| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 08-07-2011 17:00, Pacho Ramos wrote: |
| 5 |
> El vie, 08-07-2011 a las 19:45 +0300, Markos Chandras escribió: |
| 6 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
| 7 |
>> Hash: SHA512 |
| 8 |
|
| 9 |
<snip> |
| 10 |
|
| 11 |
>> Good point but there is a problem. If we process the metadata.xml, |
| 12 |
>> project pages and bugs before the infrastructure people process his |
| 13 |
>> account, and the said developer decides to return, then we need to |
| 14 |
>> process all the previous files again and restore them to the previous |
| 15 |
>> state. This is why we do not touch them until the developer is fully |
| 16 |
>> retired by the infrastructure. This is the only way to ensure that he is |
| 17 |
>> really gone. The only thing you ( as an individual developer ) can do, |
| 18 |
>> is to report bugs, wait for some time, and if the slacking developer |
| 19 |
>> does not touch them, go ahead and fix them. We cannot force people to |
| 20 |
>> use the devaway system or to provide accurate information about their |
| 21 |
>> status :-/ |
| 22 |
>> |
| 23 |
>> - -- |
| 24 |
>> Regards, |
| 25 |
>> Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 |
| 26 |
> |
| 27 |
> At what step is the retirement process irreversible then? For example, |
| 28 |
> looking at https://bugs.gentoo.org/show_bug.cgi?id=266794#c13 I would |
| 29 |
> start dropping him from metadata.xml as it's already clear the |
| 30 |
> retirement has started :-/ Maybe we could add a step that makes the |
| 31 |
> retirement irreversible (with a concrete date) after retirement team |
| 32 |
> comments in bug report announcing the process has started. |
| 33 |
|
| 34 |
The retirement process evolves with time and with our experience. Markos |
| 35 |
linked to the last documented process, but after that we've been trying |
| 36 |
to take care of metadata.xml asap. So as soon as a bug is assigned to |
| 37 |
infra, we're free to drop people from metadata.xml and reassign bugs. |
| 38 |
- From that point onwards, if a retirement is stopped, it's the |
| 39 |
developer's responsibility to add himself back to any packages and to |
| 40 |
get back to bugs. |
| 41 |
The processing of herds and teams should still be left to the final step. |
| 42 |
|
| 43 |
|
| 44 |
- -- |
| 45 |
Regards, |
| 46 |
|
| 47 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
| 48 |
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng |
| 49 |
-----BEGIN PGP SIGNATURE----- |
| 50 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 51 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 52 |
|
| 53 |
iQIcBAEBCAAGBQJOGEeOAAoJEC8ZTXQF1qEP3PUP/0ts4zMqcC0nR1hhvwXv2qjF |
| 54 |
jifRUTSZzc9B2S9w1H+OgVx2Gw8wwy/gvu5HDewDUV4BPnpPS+5/hLWXE0zqhPEJ |
| 55 |
YoqT+6+uouOSLTa9kQj56Zt7eViBvfS8QIWeHi9Ajz7sfiZOZ2ykkJlZ0K/orcYI |
| 56 |
hrc62ppC3L0mrlGnfJf7dFPGAbKyuDl18MqzSm972wn7kM3vGM7RMvJURFt8ji18 |
| 57 |
+Kd1C9FOTZ/HiPFQOaL5ro5BKJHo7FWwWHz99NnorGRDFJZiwMcOlzgMJwo6qfnH |
| 58 |
5fl0qxdSVx1BcZ0r0vUZAPcvDBI6GZlXwNwYfKRAnBTKM6P2c1BC28zpTwop01cU |
| 59 |
b7h/Ao/XRUHAC0rvYoONoGEvmTWrNMBE6OTPozsQQjat48ptHs2Z1Xd4Lp4TXell |
| 60 |
c3359wTsslktBWmFCwH6TK4FCjLXqOJucEXwrfZNADY8TJp04EeU9kRrwNhNPIJi |
| 61 |
WTeHG4l+5vtI1NtInU6eKpjBkECnuOCjauAnAoGDgqgV178vOSdAJCqstKPqu2tq |
| 62 |
W0JXJCBmayzEFi5G+pyiauJcv6nXA2GXrsL0x0fxbGOcY+n1Z6lC5k8wFQ4zMVuv |
| 63 |
cKOXqH3X2dOcpAVp+uGTOVljymQwjkoVhuLv+a4jD0n56+RNc5kMhjiz3KXvZP/G |
| 64 |
IhlVGU/MGO2ITp8ntJSI |
| 65 |
=jPcP |
| 66 |
-----END PGP SIGNATURE----- |
Archives