From: "Lukasz Damentko (rane)" <rane@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/devrel/undertakers: index.xml
Date: Thu, 24 Jan 2008 17:54:56 +0000 [thread overview]
Message-ID: <E1JI6Hw-0006FY-5Q@stork.gentoo.org> (raw)
rane 08/01/24 17:54:56
Modified: index.xml
Log:
updated with new procedures
Revision Changes Path
1.14 xml/htdocs/proj/en/devrel/undertakers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/undertakers/index.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/undertakers/index.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/undertakers/index.xml?r1=1.13&r2=1.14
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/undertakers/index.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- index.xml 23 Jan 2008 22:57:16 -0000 1.13
+++ index.xml 24 Jan 2008 17:54:55 -0000 1.14
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/undertakers/index.xml,v 1.13 2008/01/23 22:57:16 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/undertakers/index.xml,v 1.14 2008/01/24 17:54:55 rane Exp $ -->
<?xml-stylesheet href="/xsl/project.xsl" type="text/xsl"?>
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE project SYSTEM "/dtd/project.dtd">
@@ -40,17 +40,22 @@
<body>
<ol>
- <li>Check CVS and bugzilla activity
+ <li>Check CVS and bugzilla activity:
<ul>
<li>
- An easy way to check CVS activity is by using the <c>history</c>
- subcommand of <c>cvs</c>, which will display you the activity of the
- developer in question across all CVS repositories. Use it like this:
- <c>cvs history -c -u dev | sort | less</c>
+ The easiest way to check developer's CVS activity is to go to the
+ <c>http://cia.vc/stats/author/developer</c> page. For example:
+ <uri>http://cia.vc/stats/author/phreak/</uri>.
</li>
<li>
- Additionally we have the CVS slacker report mails from stork to
- <c>devrel@gentoo.org</c> the 1st of every month
+ Another method involves using the <c>history</c> subcommand of <c>cvs</c>,
+ which will display you the activity of the developer in question across
+ all CVS repositories. Use it like this: <c>cvs history -c -u dev | sort |
+ less</c>
+ </li>
+ <li>
+ Additionally we have the CVS slacker report mails from stork (aka
+ cvs.gentoo.org) to <c>retirement@gentoo.org</c> the 1st of every month
</li>
<li>
Check <uri
@@ -68,53 +73,54 @@
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 the alias when doing
- so.
- </li>
- <li>
- Reopen the New Developer bug. If the developer predates recruitment bugs
- (there was no recruitment bug), open a new bug for retirement purposes.
- Retirement bugs should be in the <c>Developer Relations</c> product and
- assigned to <c>devrel@gentoo.org</c> with the developer <b>CC'ed</b>. State
- on the bug last commit and bugs activity if applicable. Also state any
- appropriate input you may have gotten from project lead(s).
+ whenever sending emails in undertakers business, CC
+ <c>retirement@gentoo.org</c>.
</li>
- <li>Make sure the developer is <b>CC'ed</b> on the bug.</li>
<li>
- Wait a minimum of two weeks, to give the developer adequate time to respond
- on the bug. Often 3 or even 4 weeks are more appropriate.
+ If you believe developer is inactive, reopen the New Developer bug. If the
+ developer predates recruitment bugs (there was no recruitment bug), open a
+ new bug for retirement purposes. Change <c>Summary</c> to <e>Retire: Full
+ Name (nickname)</e>. Reassign the bug to <c>retirement@gentoo.org</c>
+ (Retirement Admin) and change <c>Status Whiteboard</c> to
+ <e>first-mail-sent: yy-mm-dd</e>. Make sure the developer is <b>CC'ed</b> on
+ the bug.
+ </li>
+ <li>
+ Send him the first mail and wait a minimum of two weeks, 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 second mail. Don't forget to change
+ Status Whiteboard to <e>second-mail-sent</e> and to update the date there.
+ Remember that <c>retirement@gentoo.org</c> must be CC'ed on both mails and
+ all responses must be forwarded there.
</li>
<li>
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.
</li>
- <li>Close the bug if the developer is still considered active.</li>
+ <li>Close the bug if the developer is still considered active</li>
<li>
If the developer doesn't respond in the given time or is otherwise still
- considered inactive <b>CC</b> <c>infra-bugs@gentoo.org</c> on the bug and
- add a comment asking infrastructure to retire the developer (as per their
- retirement <uri
- link="http://www.gentoo.org/proj/en/infrastructure/retire-process.xml">process</uri>).
- Also make sure you change the <c>Status Whiteboard</c> to <c>infra-retire
- yyyy/mm/dd</c> (where <c>yyyy</c> is the current year, <c>mm</c> he current
- month and <c>dd</c> the current day).
+ considered inactive, state that on the bug and ask Infra to start <uri
+ link="http://www.gentoo.org/proj/en/infrastructure/retire-process.xml">retirement
+ process</uri>). Also make sure you change the <c>Status Whiteboard</c> to
+ <c>infra-retire yyyy-mm-dd</c>.
</li>
<li>
- 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).
+ Wait for Infrastructure, Planet and Forums admins to retire developer in
+ question before proceeding further.
</li>
- <li>Ask a freenode staffer to reset the cloak to a non-gentoo one.</li>
<li>
- Update userinfo.xml with new status (ldap is done automatically by
- infrastructures script).
+ Remove access to <c>#gentoo-dev</c> (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).
</li>
+ <li>Ask a freenode staffer to reset the cloak to a non-gentoo one.</li>
<li>
Clean up the tree and herds from the yet-retired developer. Use the
<c>retire.py</c> script (which is available in <uri
link="http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/undertakers/scripts/">gentoo/xml/htdocs/proj/en/devrel/undertakers/scripts/</uri>)
- for that purpose, but make sure to review it's output <b>before</b>
+ for that purpose, but make sure to review its output <b>before</b>
committing!
<ol>
<li>
--
gentoo-commits@lists.gentoo.org mailing list
next reply other threads:[~2008-01-24 17:54 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 17:54 Lukasz Damentko (rane) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-12 11:19 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/devrel/undertakers: index.xml Markos Chandras (hwoarang)
2013-10-12 10:24 Markos Chandras (hwoarang)
2013-03-30 10:15 Markos Chandras (hwoarang)
2013-03-15 20:00 Markos Chandras (hwoarang)
2013-02-24 16:37 Markos Chandras (hwoarang)
2013-02-24 11:27 Markos Chandras (hwoarang)
2013-01-17 19:56 Markos Chandras (hwoarang)
2013-01-17 19:54 Markos Chandras (hwoarang)
2012-12-24 15:59 Markos Chandras (hwoarang)
2012-12-24 15:31 Markos Chandras (hwoarang)
2012-11-18 14:59 Markos Chandras (hwoarang)
2012-11-09 20:26 Markos Chandras (hwoarang)
2012-11-06 21:09 Markos Chandras (hwoarang)
2012-10-28 14:38 Markos Chandras (hwoarang)
2012-10-26 20:22 Markos Chandras (hwoarang)
2012-10-26 20:21 Markos Chandras (hwoarang)
2012-10-26 20:17 Markos Chandras (hwoarang)
2012-10-26 20:12 Markos Chandras (hwoarang)
2012-10-13 16:54 PaweA Hajdan (phajdan.jr)
2012-10-07 10:53 Pacho Ramos (pacho)
2012-10-01 13:56 PaweA Hajdan (phajdan.jr)
2012-09-23 14:46 Pacho Ramos (pacho)
2012-09-23 14:44 Pacho Ramos (pacho)
2012-09-21 20:58 Markos Chandras (hwoarang)
2012-08-18 15:17 Markos Chandras (hwoarang)
2012-08-09 18:23 Markos Chandras (hwoarang)
2012-08-08 21:38 Markos Chandras (hwoarang)
2012-07-22 22:52 Markos Chandras (hwoarang)
2012-07-22 9:26 Pacho Ramos (pacho)
2012-07-22 9:23 Markos Chandras (hwoarang)
2012-05-05 16:59 Markos Chandras (hwoarang)
2012-05-04 18:50 Markos Chandras (hwoarang)
2012-04-17 11:02 Markos Chandras (hwoarang)
2012-04-02 20:35 Markos Chandras (hwoarang)
2012-04-01 8:27 Markos Chandras (hwoarang)
2012-03-31 14:00 Markos Chandras (hwoarang)
2012-03-18 18:05 Markos Chandras (hwoarang)
2012-03-18 10:29 Markos Chandras (hwoarang)
2012-03-18 10:28 Markos Chandras (hwoarang)
2012-03-18 10:27 Markos Chandras (hwoarang)
2012-03-18 10:27 Markos Chandras (hwoarang)
2012-03-18 10:27 Markos Chandras (hwoarang)
2012-03-18 10:22 Markos Chandras (hwoarang)
2012-03-03 18:00 Markos Chandras (hwoarang)
2012-03-03 17:33 Markos Chandras (hwoarang)
2012-03-03 16:46 Markos Chandras (hwoarang)
2012-03-03 16:45 Markos Chandras (hwoarang)
2012-03-03 13:52 Pacho Ramos (pacho)
2012-03-02 23:10 Markos Chandras (hwoarang)
2012-03-02 23:09 Markos Chandras (hwoarang)
2012-03-02 23:07 Markos Chandras (hwoarang)
2012-02-11 19:02 Markos Chandras (hwoarang)
2012-02-10 18:34 Markos Chandras (hwoarang)
2012-02-09 22:41 Markos Chandras (hwoarang)
2012-02-09 22:24 Markos Chandras (hwoarang)
2012-02-09 22:01 Markos Chandras (hwoarang)
2012-02-09 19:59 Markos Chandras (hwoarang)
2012-02-04 21:34 Markos Chandras (hwoarang)
2012-02-01 21:40 Markos Chandras (hwoarang)
2012-01-26 20:12 Markos Chandras (hwoarang)
2012-01-22 23:08 Markos Chandras (hwoarang)
2012-01-22 21:50 Markos Chandras (hwoarang)
2012-01-22 21:24 Markos Chandras (hwoarang)
2012-01-22 21:13 Markos Chandras (hwoarang)
2011-12-16 22:27 Pacho Ramos (pacho)
2011-12-10 10:20 Markos Chandras (hwoarang)
2011-12-04 16:03 Markos Chandras (hwoarang)
2011-12-04 14:33 Markos Chandras (hwoarang)
2011-08-17 23:34 Markos Chandras (hwoarang)
2011-08-17 22:52 Markos Chandras (hwoarang)
2011-07-20 15:53 Pacho Ramos (pacho)
2011-05-23 11:32 Markos Chandras (hwoarang)
2011-05-21 19:23 Markos Chandras (hwoarang)
2010-11-11 13:09 Markos Chandras (hwoarang)
2010-11-02 1:30 Markos Chandras (hwoarang)
2010-07-21 13:21 Jorge Manuel B. S. Vicetto (jmbsvicetto)
2009-01-07 17:13 Lukasz Damentko (rane)
2008-09-23 11:10 Christina Fullam (musikc)
2008-08-11 1:36 Lukasz Damentko (rane)
2008-03-30 17:12 Lukasz Damentko (rane)
2008-01-24 18:19 Lukasz Damentko (rane)
2008-01-23 22:57 Lukasz Damentko (rane)
2008-01-17 13:13 Lukasz Damentko (rane)
2007-12-31 15:32 Christian Heim (phreak)
2007-12-25 11:27 Christian Heim (phreak)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1JI6Hw-0006FY-5Q@stork.gentoo.org \
--to=rane@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox