From Gentoo Wiki
Jump to: navigation, search
Description The Community Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.
Project email
No lead election date set
(and inherited member(s))
Parent Project Gentoo Community Relations
Project listing

The Developer Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.

Steps to retire a developer

  1. Check CVS and bugzilla activity:
    • You can use the history subcommand of cvs , which will display you the activity of the developer in question across all CVS repositories. Use it like this: cvs history -c -u dev | sed 's/^.\{2\}//g' | sort | less
    • Additionally we have the CVS slacker report mails from flycatcher (aka to the 1st of every month
    • Check to see the last few bugzilla activities. Activity is defined very broadly in this case so commenting, changing resolution, CC'ing etc. all count as activity. You need to look at each of those bugs to decide if the activity is related to development.
    • Alternatively, you can use this script(deprecated) to view the and bugzilla activity for a specific developer.

  1. Try talking to the project lead(s), if the developer looks inactive. He might be active in ways we can't determine easily. Put in some effort to contact the developer (either IRC or via email) before starting the actual retirement process. When sending an email to the developer in question, make sure you tell him, that he might get retired due to being inactive. Also, whenever sending emails in undertakers business, CC .
  2. If the developer is inactive for more than two months, send him the First Mail asking him to consider removing himself from packages that he is not interested to maintain anymore. Those packages should be announced as unmaintained to the gentoo-dev mailing list and re-assigned to until another developer or proxy-maintainer steps up and take care of them. After two weeks of no response consider reassignment of the packages.
  3. Then search for the New Developer bug, if the developer predates recruitment bugs (there was no recruitment bug), open a new bug. Change Summary to Packages reassignment: Full Name (nickname) . Reassign the bug to (Retirement Admin) and change Status Whiteboard to first-mail-sent: yy-mm-dd . Make sure the developer is CC'ed on the bug. Once situation is clarified, close the bug as FIXED.
  4. After four months from the first e-mail, if you still believe the developer is inactive, reopen the Packages reassignment bug. Change Summary to Retire: Full Name (nickname) and change Status Whiteboard to second-mail-sent: yy-mm-dd .
  5. Send him the Second Mail and wait a minimum of one month, to give the developer adequate time to respond on the bug or to the mail. If you get no response during that period, send the Third Mail . Don't forget to change Status Whiteboard to third-mail-sent and to update the date there. Remember that must be CC'ed ALL mails and ALL responses must be forwarded there. Wait another month.
  6. Consider any responses carefully. We're supposed to help Gentoo (in this case by keeping the developer base "clean"), not to retire as many developers as possible.
  7. Close the bug if the developer is still considered active
  8. If the developer doesn't respond within six months since the first mail or is otherwise still considered inactive, state that on the bug and ask Infra to start retirement process ). Bug changes add CC,, and make sure you change the Status Whiteboard to infra-retire yyyy-mm-dd.
  9. Retirement procedure looks like this:
    • Clean up the tree and herds from the yet-retired developer. Use the script (which is available in gentoo/xml/htdocs/proj/en/devrel/undertakers/scripts/ ) for that purpose, but make sure to review its output before committing!
    • Clean up any metadata.xml the developer in question might be mentioned in. This is accomplished by running --metadata-dev devname /path/to/gentoo-x86 . Review the output, and apply it to current CVS, but make sure you cvs up before applying it.
    • Clean up herds.xml in proj/en/metastructure/herds/ . Remove the developer in question from any herds he might be listed in. To find those, you might want to run this: --herds /path/to/userinfo.xml /path/to/herds.xml . That will show you the developers listed as retired in userinfo.xml which are still listed in herds.xml .
    • Clean up any project pages the developer may be listed in. Just make sure you don't erase them completely (for example userrel/archives/soc/ is fine). Use --project /path/to/userinfo.xml /path/to/xml/proj/en/ to find any stale entries.
    • Search for all NEW and REOPEN bugs assigned to the retired developer on Gentoo Bugzilla and reassign them to herds or projects the package belongs to. Information to whom reassign can be obtained from metadata.xml file of that package.
    • Wait for Infrastructure, Planet and Forums admins to retire developer in question before proceeding further.
    • If he has an account on, add a comment (if there is not one already) with his nickname and CC .
    • Check group membership on to ensure retired devs are dropped from all groups by running the script.
    • Remove access to #gentoo-dev (access is either removed completely or changed to voice depending on whether they ask for it or they're still considered active and helpful in the channel). Ask a freenode staffer to reset the cloak to a non-gentoo one.
  1. Close the bug once all of the above steps are finished!

Pending retirements

Click here to see all the pending retirements.

What will happen with your mail address after retiring?

Your mail will be forwarded to the non-gentoo email address on file in LDAP, for a period of one month per year as developer, rounded up, min 1 month, max 6 months.

If no non-gentoo email address is on file, or the address on file bounces, your mail may be stored or discarded for up to the same time, at the discretion of infra.

This page is based on a document formerly found on our main website
The following people contributed to the original document: Bryan Østergaard, rane, hwoarang, pacho
They are listed here because wiki history does not allow for any external attribution. If you edit the wiki article, please do not add yourself here; your contributions are recorded on each article's associated history page.