From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JI6Hy-000773-Kf for garchives@archives.gentoo.org; Thu, 24 Jan 2008 17:54:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EC49BE0202; Thu, 24 Jan 2008 17:54:57 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id A690BE0202 for ; Thu, 24 Jan 2008 17:54:57 +0000 (UTC) Received: from stork.gentoo.org (stork.gentoo.org [64.127.104.133]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 3C05F657F5 for ; Thu, 24 Jan 2008 17:54:57 +0000 (UTC) Received: from rane by stork.gentoo.org with local (Exim 4.68) (envelope-from ) id 1JI6Hw-0006FY-5Q for gentoo-commits@lists.gentoo.org; Thu, 24 Jan 2008 17:54:56 +0000 From: "Lukasz Damentko (rane)" To: gentoo-commits@lists.gentoo.org Reply-To: gentoo-dev@lists.gentoo.org, rane@gentoo.org Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/devrel/undertakers: index.xml X-VCS-Repository: gentoo X-VCS-Files: index.xml X-VCS-Directories: xml/htdocs/proj/en/devrel/undertakers X-VCS-Committer: rane X-VCS-Committer-Name: Lukasz Damentko Content-Type: text/plain; charset=utf8 Message-Id: Sender: Lukasz Damentko Date: Thu, 24 Jan 2008 17:54:56 +0000 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 3b7e044b-4887-46f9-b119-3c1d7b008fe5 X-Archives-Hash: 7c6fdd9c9755acb886f7d8594a16077f 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/dev= rel/undertakers/index.xml?rev=3D1.14&view=3Dmarkup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/dev= rel/undertakers/index.xml?rev=3D1.14&content-type=3Dtext/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/dev= rel/undertakers/index.xml?r1=3D1.13&r2=3D1.14 Index: index.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 @@ - + @@ -40,17 +40,22 @@ =20

Check CVS and bugzilla activity +
Check CVS and bugzilla activity:
- - An easy way to check CVS activity is by using the history - subcommand of cvs, which will display you the activity of t= he - developer in question across all CVS repositories. Use it like thi= s: - cvs history -c -u dev | sort | less + The easiest way to check developer's CVS activity is to go to the + http://cia.vc/stats/author/developer page. For example: + http://cia.vc/stats/author/phreak/.
- - Additionally we have the CVS slacker report mails from stork to - devrel@gentoo.org the 1st of every month + Another method involves using the history subcommand of = cvs, + which will display you the activity of the developer in question a= cross + all CVS repositories. Use it like this: cvs history -c -u dev |= sort | + less +
- + Additionally we have the CVS slacker report mails from stork (aka + cvs.gentoo.org) to retirement@gentoo.org the 1st of every m= onth
- Check -
- - Reopen the New Developer bug. If the developer predates recruitment = bugs - (there was no recruitment bug), open a new bug for retirement purpos= es. - Retirement bugs should be in the Developer Relations product = and - assigned to devrel@gentoo.org with the developer CC'ed= . State - on the bug last commit and bugs activity if applicable. Also state a= ny - appropriate input you may have gotten from project lead(s). + whenever sending emails in undertakers business, CC + retirement@gentoo.org.
- Make sure the developer is CC'ed on the bug.
- - 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 Summary to Retire= : Full + Name (nickname). Reassign the bug to retirement@gentoo.org + (Retirement Admin) and change Status Whiteboard to + first-mail-sent: yy-mm-dd. Make sure the developer is CC'e= d on + the bug. +
- + 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 c= hange + Status Whiteboard to second-mail-sent and to update the date = there. + Remember that retirement@gentoo.org must be CC'ed on both mai= ls and + all responses must be forwarded there.
- 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.
- Close the bug if the developer is still considered active.
- Close the bug if the developer is still considered active
- If the developer doesn't respond in the given time or is otherwise s= till - considered inactive CC infra-bugs@gentoo.org on the bu= g and - add a comment asking infrastructure to retire the developer (as per = their - retirement process). - Also make sure you change the Status Whiteboard to infra-r= etire - yyyy/mm/dd (where yyyy is the current year, mm he = current - month and dd the current day). + considered inactive, state that on the bug and ask Infra to start retirement + process). Also make sure you change the Status Whiteboard to + infra-retire yyyy-mm-dd.
- - 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 consi= dered - active and helpful in the channel). + Wait for Infrastructure, Planet and Forums admins to retire develope= r in + question before proceeding further.
- Ask a freenode staffer to reset the cloak to a non-gentoo one.
- - Update userinfo.xml with new status (ldap is done automatically by - infrastructures script). + Remove access to #gentoo-dev (access is either removed comple= tely or + changed to voice depending on whether they ask for it or they're sti= ll + considered active and helpful in the channel).
- Ask a freenode staffer to reset the cloak to a non-gentoo one.
- Clean up the tree and herds from the yet-retired developer. Use the retire.py script (which is available in gentoo/xml/htdocs/proj/en/devrel/undertak= ers/scripts/) - for that purpose, but make sure to review it's output before + for that purpose, but make sure to review its output before committing!
  1. --=20 gentoo-commits@lists.gentoo.org mailing list