El vie, 08-07-2011 a las 19:45 +0300, Markos Chandras escribió: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 08/07/2011 06:22 μμ, Pacho Ramos wrote: > > El vie, 08-07-2011 a las 17:02 +0300, Markos Chandras escribió: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA512 > >> > >> On 08/07/2011 04:31 μμ, Pacho Ramos wrote: > >>> Due me recently taking xsane due it being not fixed/updated for a long > >>> time, I noticed its maintainer was in devaway since 2010 September. > >>> > >>> Maybe they should be pinged and retired if no reply is received like > >>> done with other cases. What do you think? :-/ > >>> > >>> That people that seems to be inactive for a long time look to be the > >>> following: > >>> http://dev.gentoo.org/devaway/ > >>> > >>> battousai -> Already in retirement process (but looks stalled since end > >>> 2010, not sure why, probably retirement team didn't have time?) -> > >>> https://bugs.gentoo.org/show_bug.cgi?id=34864 > >>> > >>> blackace -> not sure about his current status, looks like he will move > >>> to staffer per https://bugs.gentoo.org/show_bug.cgi?id=45816 , in that > >>> case, maybe his devaway status could be removed. > >>> > >>> falco -> doesn't seem to be active for a long time > >>> > >>> fox2mike -> the same case > >>> > >>> markusle -> already handled in > >>> https://bugs.gentoo.org/show_bug.cgi?id=105599 > >>> > >>> mrpouet -> https://bugs.gentoo.org/show_bug.cgi?id=266794 > >>> > >>> phosphan -> looks to be unavailable for some months :-/ > >>> > >>> tanderson -> Looks to not have committed for a long time, but I think he > >>> had other responsibilities in Gentoo (maybe the same applies to other > >>> people listed here) > >>> > >>> titefleur -> already handled in > >>> https://bugs.gentoo.org/show_bug.cgi?id=195714 > >>> > >>> vorlon -> looks to not have committed everything to the tree since 2010 > >>> > >>> > >>> > >>> As some people are already being retired (like mrpouet), I thought that > >>> would be interesting to start dropping them from metadatas of packages > >>> they maintain, moving them to their respective herds or to > >>> maintainer-needed (after sending a mail to gentoo-dev announcing what > >>> packages are up to grabs). I can do this if you want. > >>> > >>> > >>> There are also some devaway entries that could probably be updated or > >>> removed by affected developers :-/ > >>> > >>> Best regards and thanks for taking care. > >> Hi, > >> > >> Truth is that we do not touch metadata.xml entries or project pages > >> until infra people process the accounts of the inactive developers. When > >> a developer is being processed by the infrastructure team, then we clean > >> metadata.xml entries and the project pages. Additionally, we announce > >> the orphaned packages in -dev-announce mailing list. Here[1] you can see > >> the steps we follow to retire a developer. > >> If you want to see the pending retirements, search bugzilla for bugs > >> assigned to [email protected]. > >> As a side note, undertakers team is understaffed so we are not very fast > >> in spotting and warning inactive developers. You can always help us if > >> you want. Just drop an email to us. > >> > >> [1]:http://www.gentoo.org/proj/en/devrel/undertakers/ > >> - -- > >> Regards, > >> Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 > > > > > > Thanks for the link > > > > The problem of the current steps order is that, until we "Wait for > > Infrastructure, Planet and Forums admins to retire developer in question > > before proceeding further." (first step of point 8), some months pass > > with bugs being ignored and ebuilds getting outdated and buggy. Why not > > make the cleanup at first "point 8" step? I mean, just after it's > > decided at point 7 to retire the development, try to get bugs and > > packages properly reassigned as soon as possible to prevent them from > > get unattended for a long time, and, after that, proceed with the > > remaining steps. What do you think? > > > > > Good point but there is a problem. If we process the metadata.xml, > project pages and bugs before the infrastructure people process his > account, and the said developer decides to return, then we need to > process all the previous files again and restore them to the previous > state. This is why we do not touch them until the developer is fully > retired by the infrastructure. This is the only way to ensure that he is > really gone. The only thing you ( as an individual developer ) can do, > is to report bugs, wait for some time, and if the slacking developer > does not touch them, go ahead and fix them. We cannot force people to > use the devaway system or to provide accurate information about their > status :-/ > > - -- > Regards, > Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
At what step is the retirement process irreversible then? For example, looking at https://bugs.gentoo.org/show_bug.cgi?id=266794#c13 I would start dropping him from metadata.xml as it's already clear the retirement has started :-/ Maybe we could add a step that makes the retirement irreversible (with a concrete date) after retirement team comments in bug report announcing the process has started.
signature.asc
Description: This is a digitally signed message part
