Re: [gentoo-dev] About some developers in devaway status that maybe are no longer active at all

[Jorge Manuel B. S. Vicetto]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09-07-2011 14:40, Pacho Ramos wrote:
> El sáb, 09-07-2011 a las 12:20 +0000, Jorge Manuel B. S. Vicetto
> escribió:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> On 08-07-2011 17:00, Pacho Ramos wrote:
>>> El vie, 08-07-2011 a las 19:45 +0300, Markos Chandras escribió:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA512
>>
>> <snip>
>>
>>>> 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.
>>
>> The retirement process evolves with time and with our experience. Markos
>> linked to the last documented process, but after that we've been trying
>> to take care of metadata.xml asap. So as soon as a bug is assigned to
>> infra, we're free to drop people from metadata.xml and reassign bugs.
>> - From that point onwards, if a retirement is stopped, it's the
>> developer's responsibility to add himself back to any packages and to
>> get back to bugs.
>> The processing of herds and teams should still be left to the final step.
>>
>>
>> - --
>> Regards,
>>
>> Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
>> Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
>
> OK, thanks for the explanation.
>
> I have searched in bugzilla for bugs with "infra-retire" in whiteboard
> and have found, for example:
> https://bugs.gentoo.org/show_bug.cgi?id=28480
>
> I have seen he still have some bugs assigned to him and he is still
> present on metadata.xml. From your last comment, looks like we could
> start to reassign them and drop him from metadata.xml just now. Could I
> do that or should I be a member of retirement team?

Anyone can help with that, so if you feel like doing it, please go ahead.

- -- 
Regards,

Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJOGaeXAAoJEC8ZTXQF1qEP1x8P/1X2edKcJsXaWQx9f2TmkO8F
7FegJr6QpjipMJg6KQoKYO4rRPNuPCToGYJFQCvy/P5MYhX2LQUT4O/exUmk4j4j
Rkpkj5NdoUVxj71Zq7foX3d6PE37XR6NACao1gkkNZSxoRHKhfDoCj8pyKpdNemK
xOEoXhLTmZJnRJCkRu2/ZgEBp0dOp4TKMlSo8QnZSokUjoFb1/PF25JupYGNs+Wi
71tTW0ykiOFMPav2eMUZY4p7R9X/flHY1/7h8C4barkx4p/CV/aAg9sgksFGc+kT
MHkgt7z3vjScKayLAbitwDNHsj7jeD0JVSkyki9cp0/9B0fjryD3goXrewk79e6e
3guhq1wTMrUpY8BmuHqQ0UUUKLKXp9bMdGcRKlTr8CQqlaPFtWqrpGpy1dlJ5cZw
HbraScaQpQTQdklFYlql8WSBga+uGv6TrsruqeSEBETPm/CMNbTl94KljcJyH2rg
aVAmlJhy0zTvweBI8iy8sshgmwhZxO8mJ1Jjo81Uomq5NoQNIvZXLpg18ubTGK9C
QX3FpslfKCxsnhy7WVsw83g9L9aAj6ygkVd0kDZzd5bahBs3fqwvnQshcwHUOY4W
/1mnwZfxfMb7LTTSTBpz9R4Ch4guMEb//9pLo6HtDGxJqElDvhDv5ypFlH6C/uZB
YpVRPOxRX5n8FsP8Mf5P
=nV04
-----END PGP SIGNATURE-----