Examine individual changes
From Gentoo Wiki
This page allows you to examine the variables generated by the Abuse Filter for an individual change, and test it against filters.
Variables generated for this change
| Variable | Value |
|---|---|
Whether or not the edit is marked as minor (no longer in use) (minor_edit) | false |
Edit count of the user (user_editcount) | 146 |
Name of the user account (user_name) | 'Amynka' |
Age of the user account (user_age) | 163846457 |
Page ID (page_id) | 116572 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'Undertakers' |
Full page title (page_prefixedtitle) | 'Project:Undertakers' |
Action (action) | 'edit' |
Edit summary/reason (summary) | '' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=Undertakers
|Description=The Community Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.
|Email=undertakers@gentoo.org
|ParentProject=Project:ComRel
|PropagatesMembers=No
|LeadElectionDate=2019/06/15
|Members={{Project Member
|Developer=User:Pacho
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Amynka
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:MGorny
|Role=Lead
|IsLead=Yes
}}
}}
The Developer Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.
== Sending mail ==
{{Tip|You can automate sending mail using send-email script from [https://github.com/mgorny/undertaker-scripts undertaker-scripts].}}
Whenever sending mail on behalf of Undertakers, please remember to:
* CC the alternative e-mail addresses of the developer (found in LDAP)
* CC <code>retirement@gentoo.org</code>
* set Reply-To to <code>retirement@gentoo.org</code>
If you forget to do that or the user skips the alias in his reply, please forward the mail to the alias for archiving purposes.
== Checking activity ==
{{Important|This section does '''not''' specify a policy. It is merely a handy list of sources which Undertakers can consult while looking for specific signs of activity. Activity in any of the listed areas by itself does not preclude retirement, and lack of activity in any of them does not imply retirement. Every case is considered individually.}}
* gentoo.git commits (for devs with gentoo.git commit access):
** git log: https://gitweb.gentoo.org/repo/gentoo.git/log/
** graphical commit timeline: https://qa-reports.gentoo.org/output/active-devs.html (updated daily)
** check-commit-activity script: https://github.com/mgorny/undertaker-scripts/blob/master/check-commit-activity.py
** monthly "slacker" report mails from Infra team to <code>retirement@gentoo.org</code>
* Bugzilla activity:
** Check [https://bugs.gentoo.org/custom_userhistory.cgi?matchstr=DEVELOPER@gentoo.org https://bugs.gentoo.org/custom_userhistory.cgi?matchstr=DEVELOPER@gentoo.org] 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.
* Forums:
** Find the developer on [https://forums.gentoo.org/memberlist.php member list], then use 'Find all posts by ...'
** See also [https://bugs.gentoo.org/650120 #650120] as request for better activity indication
* Activity in other areas:
** For activity in projects, contact the project to establish some way of determining activity
** Contact the developer and ask for a way of determining activity
* Check for [https://www.gentoo.org/inside-gentoo/developers/unavailable-developers.html devaway]
== Steps to retire a developer ==
=== Prior to inactivity retirement ===
# If the developer is inactive for more than two months:
#* Send the [[Project:Undertakers/FirstMail|First Mail]] asking the developer to consider removing themself from packages they are uninterested in maintaining and/or update their project roles. Packages no longer in the developer's care should be announced as unmaintained to the {{Mail|gentoo-dev@lists.gentoo.org}} mailing list and re-assigned to {{Mail|maintainer-needed@gentoo.org}} until another developer or proxy-maintainer steps up and take care of them.
#* Find the developer's bug:
#** If the developer predates recruitment bugs (there was no recruitment bug), open a new bug.
#** Change <code>Summary</code> to:
#*** Developers with gentoo.git commit access: ''Packages reassignment: Full Name (nickname)''.
#*** Developers without gentoo.git commit access: ''Status update: Full Name (nickname)''.
#** Reassign the bug to <code>retirement@gentoo.org</code> (Retirement Admin).
#** Change <code>Status Whiteboard</code> to ''first-mail-sent: yy-mm-dd''.
#** Make sure the developer and relevant teams are '''CC'ed''' on the bug.
#** Set Alias bug field to nickname.
#** Once situation is clarified, close the bug as FIXED/WONTFIX.
#* After two weeks of no response consider reassignment of the packages.
#** '''Remember to reassign bugs to new maintainer''' after changing metadata.xml maintainer field.
# After four months from the first e-mail, if you still believe the developer is inactive:
#* Reopen the Packages reassignment bug:
#** Change <code>Summary</code> to ''Retire: Full Name (nickname)''.
#** Change <code>Status Whiteboard</code> to ''second-mail-sent: yy-mm-dd''.
#* Send the [[Project:Undertakers/SecondMail|Second Mail]].
#* Wait a minimum of one month, to give the developer adequate time to respond on the bug or to the mail.
# After one month from the second e-mail, if you still believe the developer is inactive:
#* Send the [[Project:Undertakers/ThirdMail|Third Mail]].
#* Don't forget to change Status Whiteboard to ''third-mail-sent'' and to update the date there.
#* Wait another month.
# Close the bug if the developer is still considered active
# 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 [[Project:Infrastructure/Retire_Process|retirement process]].
=== Retirement procedure ===
Retirement procedure looks like this:
* Change the <code>Status Whiteboard</code> to <code>infra-retire: yyyy-mm-dd</code>.
* CC <code>infra-bugs@gentoo.org</code>, <code>planet@gentoo.org</code> (when you find DEV in Contributors list, left column at https://planet.gentoo.org/), <code>forum-mods@gentoo.org</code>.
* Clean up any <code>metadata.xml</code> the developer in question might be mentioned in. Using simple python [https://github.com/mgorny/herdfix/blob/master/kill-developer.py script].
* Remove the developer from all the teams of which they are still a member of on the [[Project:Gentoo]] page, and set developer status to <code>Is active: No</code> on the developer's wiki user page.
* Search for all NEW and REOPEN bugs assigned to the retired developer on Gentoo Bugzilla and reassign them to the remaining package maintainers (or maintainer-needed). Information to whom reassign can be obtained from {{Path|metadata.xml}} file of that package.
* Wait for Infrastructure, Planet and Forums admins to retire developer in question before proceeding further.
* Remove access to <code>#gentoo-dev</code> (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 (#gentoo-groupcontacts channel) to reset the cloak to a non-gentoo one.
Close the bug once all of the above steps are finished!
=== Status tracking for retirement bugs ===
Pending:
- Packages reassignment
- Bugs
- IRC cloak
- Infra
- Wiki
- Forum
- Planet
== Pending retirements ==
Click [https://bugs.gentoo.org/buglist.cgi?component=Retirement&product=Gentoo%20Developers%2FStaff&resolution=--- here] to see all the pending retirements.
== Undertaker scripts ==
The following scripts are currently available in [https://github.com/mgorny/undertaker-scripts undertaker-scripts] repository to help automating the work of Undertakers:
* {{c|check-commit-activity.py}} to find developers who haven't committed in N days (and don't have retirement bug open); 4 months, by default;
* {{c|scan-open-bugs.py}} to scan open retirement bugs and report those for which action is overdue,
* {{c|send-email.py}} along with mail templates to help sending e-mails on behalf of Undertakers.
== 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, the mail may be stored or discarded for up to the same time,
at the discretion of infra.
{{Migrated|originalauthors=Bryan Østergaard, rane, {{Dev|Hwoarang}}, {{Dev|Pacho}}}}' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=Undertakers
|Description=The Community Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.
|Email=undertakers@gentoo.org
|ParentProject=Project:ComRel
|PropagatesMembers=No
|LeadElectionDate=2019/06/15
|Members={{Project Member
|Developer=User:Pacho
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:MGorny
|Role=Lead
|IsLead=Yes
}}
}}
The Developer Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.
== Sending mail ==
{{Tip|You can automate sending mail using send-email script from [https://github.com/mgorny/undertaker-scripts undertaker-scripts].}}
Whenever sending mail on behalf of Undertakers, please remember to:
* CC the alternative e-mail addresses of the developer (found in LDAP)
* CC <code>retirement@gentoo.org</code>
* set Reply-To to <code>retirement@gentoo.org</code>
If you forget to do that or the user skips the alias in his reply, please forward the mail to the alias for archiving purposes.
== Checking activity ==
{{Important|This section does '''not''' specify a policy. It is merely a handy list of sources which Undertakers can consult while looking for specific signs of activity. Activity in any of the listed areas by itself does not preclude retirement, and lack of activity in any of them does not imply retirement. Every case is considered individually.}}
* gentoo.git commits (for devs with gentoo.git commit access):
** git log: https://gitweb.gentoo.org/repo/gentoo.git/log/
** graphical commit timeline: https://qa-reports.gentoo.org/output/active-devs.html (updated daily)
** check-commit-activity script: https://github.com/mgorny/undertaker-scripts/blob/master/check-commit-activity.py
** monthly "slacker" report mails from Infra team to <code>retirement@gentoo.org</code>
* Bugzilla activity:
** Check [https://bugs.gentoo.org/custom_userhistory.cgi?matchstr=DEVELOPER@gentoo.org https://bugs.gentoo.org/custom_userhistory.cgi?matchstr=DEVELOPER@gentoo.org] 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.
* Forums:
** Find the developer on [https://forums.gentoo.org/memberlist.php member list], then use 'Find all posts by ...'
** See also [https://bugs.gentoo.org/650120 #650120] as request for better activity indication
* Activity in other areas:
** For activity in projects, contact the project to establish some way of determining activity
** Contact the developer and ask for a way of determining activity
* Check for [https://www.gentoo.org/inside-gentoo/developers/unavailable-developers.html devaway]
== Steps to retire a developer ==
=== Prior to inactivity retirement ===
# If the developer is inactive for more than two months:
#* Send the [[Project:Undertakers/FirstMail|First Mail]] asking the developer to consider removing themself from packages they are uninterested in maintaining and/or update their project roles. Packages no longer in the developer's care should be announced as unmaintained to the {{Mail|gentoo-dev@lists.gentoo.org}} mailing list and re-assigned to {{Mail|maintainer-needed@gentoo.org}} until another developer or proxy-maintainer steps up and take care of them.
#* Find the developer's bug:
#** If the developer predates recruitment bugs (there was no recruitment bug), open a new bug.
#** Change <code>Summary</code> to:
#*** Developers with gentoo.git commit access: ''Packages reassignment: Full Name (nickname)''.
#*** Developers without gentoo.git commit access: ''Status update: Full Name (nickname)''.
#** Reassign the bug to <code>retirement@gentoo.org</code> (Retirement Admin).
#** Change <code>Status Whiteboard</code> to ''first-mail-sent: yy-mm-dd''.
#** Make sure the developer and relevant teams are '''CC'ed''' on the bug.
#** Set Alias bug field to nickname.
#** Once situation is clarified, close the bug as FIXED/WONTFIX.
#* After two weeks of no response consider reassignment of the packages.
#** '''Remember to reassign bugs to new maintainer''' after changing metadata.xml maintainer field.
# After four months from the first e-mail, if you still believe the developer is inactive:
#* Reopen the Packages reassignment bug:
#** Change <code>Summary</code> to ''Retire: Full Name (nickname)''.
#** Change <code>Status Whiteboard</code> to ''second-mail-sent: yy-mm-dd''.
#* Send the [[Project:Undertakers/SecondMail|Second Mail]].
#* Wait a minimum of one month, to give the developer adequate time to respond on the bug or to the mail.
# After one month from the second e-mail, if you still believe the developer is inactive:
#* Send the [[Project:Undertakers/ThirdMail|Third Mail]].
#* Don't forget to change Status Whiteboard to ''third-mail-sent'' and to update the date there.
#* Wait another month.
# Close the bug if the developer is still considered active
# 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 [[Project:Infrastructure/Retire_Process|retirement process]].
=== Retirement procedure ===
Retirement procedure looks like this:
* Change the <code>Status Whiteboard</code> to <code>infra-retire: yyyy-mm-dd</code>.
* CC <code>infra-bugs@gentoo.org</code>, <code>planet@gentoo.org</code> (when you find DEV in Contributors list, left column at https://planet.gentoo.org/), <code>forum-mods@gentoo.org</code>.
* Clean up any <code>metadata.xml</code> the developer in question might be mentioned in. Using simple python [https://github.com/mgorny/herdfix/blob/master/kill-developer.py script].
* Remove the developer from all the teams of which they are still a member of on the [[Project:Gentoo]] page, and set developer status to <code>Is active: No</code> on the developer's wiki user page.
* Search for all NEW and REOPEN bugs assigned to the retired developer on Gentoo Bugzilla and reassign them to the remaining package maintainers (or maintainer-needed). Information to whom reassign can be obtained from {{Path|metadata.xml}} file of that package.
* Wait for Infrastructure, Planet and Forums admins to retire developer in question before proceeding further.
* Remove access to <code>#gentoo-dev</code> (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 (#gentoo-groupcontacts channel) to reset the cloak to a non-gentoo one.
Close the bug once all of the above steps are finished!
=== Status tracking for retirement bugs ===
Pending:
- Packages reassignment
- Bugs
- IRC cloak
- Infra
- Wiki
- Forum
- Planet
== Pending retirements ==
Click [https://bugs.gentoo.org/buglist.cgi?component=Retirement&product=Gentoo%20Developers%2FStaff&resolution=--- here] to see all the pending retirements.
== Undertaker scripts ==
The following scripts are currently available in [https://github.com/mgorny/undertaker-scripts undertaker-scripts] repository to help automating the work of Undertakers:
* {{c|check-commit-activity.py}} to find developers who haven't committed in N days (and don't have retirement bug open); 4 months, by default;
* {{c|scan-open-bugs.py}} to scan open retirement bugs and report those for which action is overdue,
* {{c|send-email.py}} along with mail templates to help sending e-mails on behalf of Undertakers.
== 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, the mail may be stored or discarded for up to the same time,
at the discretion of infra.
{{Migrated|originalauthors=Bryan Østergaard, rane, {{Dev|Hwoarang}}, {{Dev|Pacho}}}}' |
Unified diff of changes made by edit (edit_diff) | '@@ -8,8 +8,4 @@
|Members={{Project Member
|Developer=User:Pacho
-|Role=Member
-|IsLead=No
-}}{{Project Member
-|Developer=User:Amynka
|Role=Member
|IsLead=No
' |
Old page size (old_size) | 8197 |
Lines added in edit (added_lines) | [] |
Lines removed in edit (removed_lines) | [
0 => '|Role=Member',
1 => '|IsLead=No',
2 => '}}{{Project Member',
3 => '|Developer=User:Amynka'
] |
New page text, stripped of any markup (new_text) | '
Undertakers
Description
The Community Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.
Project email
undertakers@gentoo.org
Lead(s)
Michał Górny
(mgorny)Lead Last elected: 2019/06/15
Member(s)
Amy Liffey
(amynka)MemberPacho Ramos
(Pacho)Member
Subproject(s)(and inherited member(s))
(none)
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.
Contents
1 Sending mail
2 Checking activity
3 Steps to retire a developer
3.1 Prior to inactivity retirement
3.2 Retirement procedure
3.3 Status tracking for retirement bugs
4 Pending retirements
5 Undertaker scripts
6 What will happen with your mail address after retiring?
Sending mail[edit]
TipYou can automate sending mail using send-email script from undertaker-scripts.
Whenever sending mail on behalf of Undertakers, please remember to:
CC the alternative e-mail addresses of the developer (found in LDAP)
CC retirement@gentoo.org
set Reply-To to retirement@gentoo.org
If you forget to do that or the user skips the alias in his reply, please forward the mail to the alias for archiving purposes.
Checking activity[edit]
ImportantThis section does not specify a policy. It is merely a handy list of sources which Undertakers can consult while looking for specific signs of activity. Activity in any of the listed areas by itself does not preclude retirement, and lack of activity in any of them does not imply retirement. Every case is considered individually.
gentoo.git commits (for devs with gentoo.git commit access):
git log: https://gitweb.gentoo.org/repo/gentoo.git/log/
graphical commit timeline: https://qa-reports.gentoo.org/output/active-devs.html (updated daily)
check-commit-activity script: https://github.com/mgorny/undertaker-scripts/blob/master/check-commit-activity.py
monthly "slacker" report mails from Infra team to retirement@gentoo.org
Bugzilla activity:
Check https://bugs.gentoo.org/custom_userhistory.cgi?matchstr=DEVELOPER@gentoo.org 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.
Forums:
Find the developer on member list, then use 'Find all posts by ...'
See also #650120 as request for better activity indication
Activity in other areas:
For activity in projects, contact the project to establish some way of determining activity
Contact the developer and ask for a way of determining activity
Check for devaway
Steps to retire a developer[edit]
Prior to inactivity retirement[edit]
If the developer is inactive for more than two months:
Send the First Mail asking the developer to consider removing themself from packages they are uninterested in maintaining and/or update their project roles. Packages no longer in the developer's care should be announced as unmaintained to the gentoo-dev@lists.gentoo.org mailing list and re-assigned to maintainer-needed@gentoo.org until another developer or proxy-maintainer steps up and take care of them.
Find the developer's bug:
If the developer predates recruitment bugs (there was no recruitment bug), open a new bug.
Change Summary to:
Developers with gentoo.git commit access: Packages reassignment: Full Name (nickname).
Developers without gentoo.git commit access: Status update: Full Name (nickname).
Reassign the bug to retirement@gentoo.org (Retirement Admin).
Change Status Whiteboard to first-mail-sent: yy-mm-dd.
Make sure the developer and relevant teams are CC'ed on the bug.
Set Alias bug field to nickname.
Once situation is clarified, close the bug as FIXED/WONTFIX.
After two weeks of no response consider reassignment of the packages.
Remember to reassign bugs to new maintainer after changing metadata.xml maintainer field.
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).
Change Status Whiteboard to second-mail-sent: yy-mm-dd.
Send the Second Mail.
Wait a minimum of one month, to give the developer adequate time to respond on the bug or to the mail.
After one month from the second e-mail, if you still believe the developer is inactive:
Send the Third Mail.
Don't forget to change Status Whiteboard to third-mail-sent and to update the date there.
Wait another month.
Close the bug if the developer is still considered active
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.
Retirement procedure[edit]
Retirement procedure looks like this:
Change the Status Whiteboard to infra-retire: yyyy-mm-dd.
CC infra-bugs@gentoo.org, planet@gentoo.org (when you find DEV in Contributors list, left column at https://planet.gentoo.org/), forum-mods@gentoo.org.
Clean up any metadata.xml the developer in question might be mentioned in. Using simple python script.
Remove the developer from all the teams of which they are still a member of on the Project:Gentoo page, and set developer status to Is active: No on the developer's wiki user page.
Search for all NEW and REOPEN bugs assigned to the retired developer on Gentoo Bugzilla and reassign them to the remaining package maintainers (or maintainer-needed). 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.
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 (#gentoo-groupcontacts channel) to reset the cloak to a non-gentoo one.
Close the bug once all of the above steps are finished!
Status tracking for retirement bugs[edit]
Pending:
- Packages reassignment
- Bugs
- IRC cloak
- Infra
- Wiki
- Forum
- Planet
Pending retirements[edit]
Click here to see all the pending retirements.
Undertaker scripts[edit]
The following scripts are currently available in undertaker-scripts repository to help automating the work of Undertakers:
check-commit-activity.py to find developers who haven't committed in N days (and don't have retirement bug open); 4 months, by default;
scan-open-bugs.py to scan open retirement bugs and report those for which action is overdue,
send-email.py along with mail templates to help sending e-mails on behalf of Undertakers.
What will happen with your mail address after retiring?[edit]
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, the 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 gentoo.org. The following people contributed to the original document: Bryan Østergaard, rane, Markos Chandras (Hwoarang), Pacho Ramos (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.
' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>Undertakers</big>
</th></tr>
<tr valign="top">
<th> Description
</th>
<td style="text-align: justify;"> The Community Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.
</td></tr>
<tr>
<th> <span title="Mails to member(s) listed below.">Project email</span>
</th>
<td> <a rel="nofollow" class="external text" href="mailto:undertakers@gentoo.org">undertakers@gentoo.org</a>
</td></tr>
<tr valign="top">
<th> Lead(s)
</th>
<td> <ul><li><a href="/wiki/User:MGorny" title="User:MGorny">Michał Górny</a>
(mgorny)<br /><i>Lead</i></li></ul> <br />Last elected: 2019/06/15
</td></tr>
<tr valign="top">
<th> Member(s)
</th>
<td> <ul><li><a href="/wiki/User:Amynka" title="User:Amynka">Amy Liffey</a>
(amynka)<br /><i>Member</i></li><li><a href="/wiki/User:Pacho" title="User:Pacho">Pacho Ramos</a>
(Pacho)<br /><i>Member</i></li></ul>
</td></tr>
<tr valign="top">
<th> Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td> (none)
</td></tr>
<tr>
<th> Parent Project
</th>
<td> <a href="/wiki/Project:ComRel" title="Project:ComRel">Gentoo Community Relations</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></table>
<p>The Developer Relations Undertakers project handles developer retirement, both when developers announce their retirement as well as due to developer inactivity.
</p>
<div id="toc" class="toc"><div class="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Sending_mail"><span class="tocnumber">1</span> <span class="toctext">Sending mail</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Checking_activity"><span class="tocnumber">2</span> <span class="toctext">Checking activity</span></a></li>
<li class="toclevel-1 tocsection-3"><a href="#Steps_to_retire_a_developer"><span class="tocnumber">3</span> <span class="toctext">Steps to retire a developer</span></a>
<ul>
<li class="toclevel-2 tocsection-4"><a href="#Prior_to_inactivity_retirement"><span class="tocnumber">3.1</span> <span class="toctext">Prior to inactivity retirement</span></a></li>
<li class="toclevel-2 tocsection-5"><a href="#Retirement_procedure"><span class="tocnumber">3.2</span> <span class="toctext">Retirement procedure</span></a></li>
<li class="toclevel-2 tocsection-6"><a href="#Status_tracking_for_retirement_bugs"><span class="tocnumber">3.3</span> <span class="toctext">Status tracking for retirement bugs</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-7"><a href="#Pending_retirements"><span class="tocnumber">4</span> <span class="toctext">Pending retirements</span></a></li>
<li class="toclevel-1 tocsection-8"><a href="#Undertaker_scripts"><span class="tocnumber">5</span> <span class="toctext">Undertaker scripts</span></a></li>
<li class="toclevel-1 tocsection-9"><a href="#What_will_happen_with_your_mail_address_after_retiring.3F"><span class="tocnumber">6</span> <span class="toctext">What will happen with your mail address after retiring?</span></a></li>
</ul>
</div>
<h2><span class="mw-headline" id="Sending_mail">Sending mail</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=1" title="Edit section: Sending mail">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<div class="alert alert-success gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-check-circle"></i> Tip</strong><br />You can automate sending mail using send-email script from <a rel="nofollow" class="external text" href="https://github.com/mgorny/undertaker-scripts">undertaker-scripts</a>.</div>
<p>Whenever sending mail on behalf of Undertakers, please remember to:
</p>
<ul><li> CC the alternative e-mail addresses of the developer (found in LDAP)</li>
<li> CC <code>retirement@gentoo.org</code></li>
<li> set Reply-To to <code>retirement@gentoo.org</code></li></ul>
<p>If you forget to do that or the user skips the alias in his reply, please forward the mail to the alias for archiving purposes.
</p>
<h2><span class="mw-headline" id="Checking_activity">Checking activity</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=2" title="Edit section: Checking activity">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<div class="alert alert-warning gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-exclamation-circle"></i> Important</strong><br />This section does <b>not</b> specify a policy. It is merely a handy list of sources which Undertakers can consult while looking for specific signs of activity. Activity in any of the listed areas by itself does not preclude retirement, and lack of activity in any of them does not imply retirement. Every case is considered individually.</div>
<ul><li> gentoo.git commits (for devs with gentoo.git commit access):
<ul><li> git log: <a rel="nofollow" class="external free" href="https://gitweb.gentoo.org/repo/gentoo.git/log/">https://gitweb.gentoo.org/repo/gentoo.git/log/</a></li>
<li> graphical commit timeline: <a rel="nofollow" class="external free" href="https://qa-reports.gentoo.org/output/active-devs.html">https://qa-reports.gentoo.org/output/active-devs.html</a> (updated daily)</li>
<li> check-commit-activity script: <a rel="nofollow" class="external free" href="https://github.com/mgorny/undertaker-scripts/blob/master/check-commit-activity.py">https://github.com/mgorny/undertaker-scripts/blob/master/check-commit-activity.py</a></li>
<li> monthly "slacker" report mails from Infra team to <code>retirement@gentoo.org</code></li></ul></li>
<li> Bugzilla activity:
<ul><li> Check <a rel="nofollow" class="external free" href="https://bugs.gentoo.org/custom_userhistory.cgi?matchstr=DEVELOPER@gentoo.org">https://bugs.gentoo.org/custom_userhistory.cgi?matchstr=DEVELOPER@gentoo.org</a> 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.</li></ul></li>
<li> Forums:
<ul><li> Find the developer on <a rel="nofollow" class="external text" href="https://forums.gentoo.org/memberlist.php">member list</a>, then use 'Find all posts by ...'</li>
<li> See also <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/650120">#650120</a> as request for better activity indication</li></ul></li>
<li> Activity in other areas:
<ul><li> For activity in projects, contact the project to establish some way of determining activity</li>
<li> Contact the developer and ask for a way of determining activity</li></ul></li>
<li> Check for <a rel="nofollow" class="external text" href="https://www.gentoo.org/inside-gentoo/developers/unavailable-developers.html">devaway</a></li></ul>
<h2><span class="mw-headline" id="Steps_to_retire_a_developer">Steps to retire a developer</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=3" title="Edit section: Steps to retire a developer">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<h3><span class="mw-headline" id="Prior_to_inactivity_retirement">Prior to inactivity retirement</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=4" title="Edit section: Prior to inactivity retirement">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<ol><li> If the developer is inactive for more than two months:
<ul><li> Send the <a href="/wiki/Project:Undertakers/FirstMail" title="Project:Undertakers/FirstMail">First Mail</a> asking the developer to consider removing themself from packages they are uninterested in maintaining and/or update their project roles. Packages no longer in the developer's care should be announced as unmaintained to the <a rel="nofollow" class="external text" href="mailto:gentoo-dev@lists.gentoo.org">gentoo-dev@lists.gentoo.org</a> mailing list and re-assigned to <a rel="nofollow" class="external text" href="mailto:maintainer-needed@gentoo.org">maintainer-needed@gentoo.org</a> until another developer or proxy-maintainer steps up and take care of them.</li>
<li> Find the developer's bug:
<ul><li> If the developer predates recruitment bugs (there was no recruitment bug), open a new bug.</li>
<li> Change <code>Summary</code> to:
<ul><li> Developers with gentoo.git commit access: <i>Packages reassignment: Full Name (nickname)</i>.</li>
<li> Developers without gentoo.git commit access: <i>Status update: Full Name (nickname)</i>.</li></ul></li>
<li> Reassign the bug to <code>retirement@gentoo.org</code> (Retirement Admin).</li>
<li> Change <code>Status Whiteboard</code> to <i>first-mail-sent: yy-mm-dd</i>.</li>
<li> Make sure the developer and relevant teams are <b>CC'ed</b> on the bug.</li>
<li> Set Alias bug field to nickname.</li>
<li> Once situation is clarified, close the bug as FIXED/WONTFIX.</li></ul></li>
<li> After two weeks of no response consider reassignment of the packages.
<ul><li> <b>Remember to reassign bugs to new maintainer</b> after changing metadata.xml maintainer field.</li></ul></li></ul></li>
<li> After four months from the first e-mail, if you still believe the developer is inactive:
<ul><li> Reopen the Packages reassignment bug:
<ul><li> Change <code>Summary</code> to <i>Retire: Full Name (nickname)</i>.</li>
<li> Change <code>Status Whiteboard</code> to <i>second-mail-sent: yy-mm-dd</i>.</li></ul></li>
<li> Send the <a href="/wiki/Project:Undertakers/SecondMail" title="Project:Undertakers/SecondMail">Second Mail</a>.</li>
<li> Wait a minimum of one month, to give the developer adequate time to respond on the bug or to the mail.</li></ul></li>
<li> After one month from the second e-mail, if you still believe the developer is inactive:
<ul><li> Send the <a href="/wiki/Project:Undertakers/ThirdMail" title="Project:Undertakers/ThirdMail">Third Mail</a>.</li>
<li> Don't forget to change Status Whiteboard to <i>third-mail-sent</i> and to update the date there.</li>
<li> Wait another month.</li></ul></li>
<li> Close the bug if the developer is still considered active</li>
<li> If the developer doesn't respond within six months since the first mail or is otherwise still considered inactive:
<ul><li> State that on the bug and ask Infra to start <a href="/wiki/Project:Infrastructure/Retire_Process" title="Project:Infrastructure/Retire Process">retirement process</a>.</li></ul></li></ol>
<h3><span class="mw-headline" id="Retirement_procedure">Retirement procedure</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=5" title="Edit section: Retirement procedure">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Retirement procedure looks like this:
</p>
<ul><li> Change the <code>Status Whiteboard</code> to <code>infra-retire: yyyy-mm-dd</code>.</li>
<li> CC <code>infra-bugs@gentoo.org</code>, <code>planet@gentoo.org</code> (when you find DEV in Contributors list, left column at <a rel="nofollow" class="external free" href="https://planet.gentoo.org/">https://planet.gentoo.org/</a>), <code>forum-mods@gentoo.org</code>.</li>
<li> Clean up any <code>metadata.xml</code> the developer in question might be mentioned in. Using simple python <a rel="nofollow" class="external text" href="https://github.com/mgorny/herdfix/blob/master/kill-developer.py">script</a>.</li>
<li> Remove the developer from all the teams of which they are still a member of on the <a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project:Gentoo</a> page, and set developer status to <code>Is active: No</code> on the developer's wiki user page.</li>
<li> Search for all NEW and REOPEN bugs assigned to the retired developer on Gentoo Bugzilla and reassign them to the remaining package maintainers (or maintainer-needed). Information to whom reassign can be obtained from <span style="font-family: monospace; font-size: 95%">metadata.xml</span> file of that package.</li>
<li> Wait for Infrastructure, Planet and Forums admins to retire developer in question before proceeding further.</li>
<li> Remove access to <code>#gentoo-dev</code> (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 (#gentoo-groupcontacts channel) to reset the cloak to a non-gentoo one.</li></ul>
<p>Close the bug once all of the above steps are finished!
</p>
<h3><span class="mw-headline" id="Status_tracking_for_retirement_bugs">Status tracking for retirement bugs</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=6" title="Edit section: Status tracking for retirement bugs">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<pre>Pending:
- Packages reassignment
- Bugs
- IRC cloak
- Infra
- Wiki
- Forum
- Planet
</pre>
<h2><span class="mw-headline" id="Pending_retirements">Pending retirements</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=7" title="Edit section: Pending retirements">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Click <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?component=Retirement&product=Gentoo%20Developers%2FStaff&resolution=---">here</a> to see all the pending retirements.
</p>
<h2><span class="mw-headline" id="Undertaker_scripts">Undertaker scripts</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=8" title="Edit section: Undertaker scripts">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>The following scripts are currently available in <a rel="nofollow" class="external text" href="https://github.com/mgorny/undertaker-scripts">undertaker-scripts</a> repository to help automating the work of Undertakers:
</p>
<ul><li> <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">check-commit-activity.py</span> to find developers who haven't committed in N days (and don't have retirement bug open); 4 months, by default;</li>
<li> <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">scan-open-bugs.py</span> to scan open retirement bugs and report those for which action is overdue,</li>
<li> <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">send-email.py</span> along with mail templates to help sending e-mails on behalf of Undertakers.</li></ul>
<h2><span class="mw-headline" id="What_will_happen_with_your_mail_address_after_retiring.3F">What will happen with your mail address after retiring?</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Undertakers&action=edit&section=9" title="Edit section: What will happen with your mail address after retiring?">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>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.
</p><p>If no non-gentoo email address is on file, or the address on file bounces, the mail may be stored or discarded for up to the same time,
at the discretion of infra.
</p>
<hr /><small>This page is based on a document formerly found on our main website <a rel="nofollow" class="external text" href="https://www.gentoo.org/">gentoo.org</a>. <br />The following people contributed to the original document: <b>Bryan Østergaard, rane, <a href="/wiki/User:Hwoarang" title="User:Hwoarang">Markos Chandras (Hwoarang)</a>, <a href="/wiki/User:Pacho" title="User:Pacho">Pacho Ramos (Pacho)</a></b><br /><span style="color: #555;">They are listed here because wiki history does not allow for any external attribution. If you edit the wiki article, please do <b>not</b> add yourself here; your contributions are recorded on each article's associated history page.</span></small>
<!--
NewPP limit report
Cached time: 20190714173921
Cache expiry: 86400
Dynamic content: false
[SMW] In‐text annotation parser time: 0.005 seconds
CPU time usage: 0.104 seconds
Real time usage: 0.135 seconds
Preprocessor visited node count: 428/1000000
Preprocessor generated node count: 1778/1000000
Post‐expand include size: 5950/2097152 bytes
Template argument size: 2038/2097152 bytes
Highest expansion depth: 7/40
Expensive parser function count: 0/100
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
100.00% 111.413 1 -total
63.35% 70.580 1 Template:Project
23.10% 25.739 3 Template:ProjectMemberLine
20.91% 23.292 1 Template:Migrated
19.90% 22.168 2 Template:Dev
9.99% 11.127 3 Template:ProjectMemberLineNickname
9.97% 11.106 2 Template:Mail
8.55% 9.521 2 Template:DevName
5.81% 6.473 2 Template:Project_Member
1.55% 1.728 1 Template:Tip
-->
</div>' |
Unix timestamp of change (timestamp) | 1563125960 |