Gentoo Archives: gentoo-dev

From: Markos Chandras <hwoarang@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] About some developers in devaway status that maybe are no longer active at all
Date: Sun, 10 Jul 2011 13:32:12
Message-Id: 4E19A9B9.2090908@gentoo.org
In Reply to: Re: [gentoo-dev] About some developers in devaway status that maybe are no longer active at all by "Jorge Manuel B. S. Vicetto"
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA512
3
4 On 10/07/2011 04:22 μμ, Jorge Manuel B. S. Vicetto wrote:
5 > On 09-07-2011 14:40, Pacho Ramos wrote:
6 >> El sáb, 09-07-2011 a las 12:20 +0000, Jorge Manuel B. S. Vicetto
7 >> escribió:
8 >>> -----BEGIN PGP SIGNED MESSAGE-----
9 >>> Hash: SHA256
10 >>>
11 >>> On 08-07-2011 17:00, Pacho Ramos wrote:
12 >>>> El vie, 08-07-2011 a las 19:45 +0300, Markos Chandras escribió:
13 >>>>> -----BEGIN PGP SIGNED MESSAGE-----
14 >>>>> Hash: SHA512
15 >>>
16 >>> <snip>
17 >>>
18 >>>>> Good point but there is a problem. If we process the metadata.xml,
19 >>>>> project pages and bugs before the infrastructure people process his
20 >>>>> account, and the said developer decides to return, then we need to
21 >>>>> process all the previous files again and restore them to the previous
22 >>>>> state. This is why we do not touch them until the developer is fully
23 >>>>> retired by the infrastructure. This is the only way to ensure that he is
24 >>>>> really gone. The only thing you ( as an individual developer ) can do,
25 >>>>> is to report bugs, wait for some time, and if the slacking developer
26 >>>>> does not touch them, go ahead and fix them. We cannot force people to
27 >>>>> use the devaway system or to provide accurate information about their
28 >>>>> status :-/
29 >>>>>
30 >>>>> - --
31 >>>>> Regards,
32 >>>>> Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
33 >>>>
34 >>>> At what step is the retirement process irreversible then? For example,
35 >>>> looking at https://bugs.gentoo.org/show_bug.cgi?id=266794#c13 I would
36 >>>> start dropping him from metadata.xml as it's already clear the
37 >>>> retirement has started :-/ Maybe we could add a step that makes the
38 >>>> retirement irreversible (with a concrete date) after retirement team
39 >>>> comments in bug report announcing the process has started.
40 >>>
41 >>> The retirement process evolves with time and with our experience. Markos
42 >>> linked to the last documented process, but after that we've been trying
43 >>> to take care of metadata.xml asap. So as soon as a bug is assigned to
44 >>> infra, we're free to drop people from metadata.xml and reassign bugs.
45 >>> - From that point onwards, if a retirement is stopped, it's the
46 >>> developer's responsibility to add himself back to any packages and to
47 >>> get back to bugs.
48 >>> The processing of herds and teams should still be left to the final step.
49 >>>
50 >>>
51 >>> - --
52 >>> Regards,
53 >>>
54 >>> Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
55 >>> Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
56 >
57 >> OK, thanks for the explanation.
58 >
59 >> I have searched in bugzilla for bugs with "infra-retire" in whiteboard
60 >> and have found, for example:
61 >> https://bugs.gentoo.org/show_bug.cgi?id=28480
62 >
63 >> I have seen he still have some bugs assigned to him and he is still
64 >> present on metadata.xml. From your last comment, looks like we could
65 >> start to reassign them and drop him from metadata.xml just now. Could I
66 >> do that or should I be a member of retirement team?
67 >
68 > Anyone can help with that, so if you feel like doing it, please go ahead.
69 >
70 Moreover, there are some scripts[1] you can use to speed up the
71 re-assigning process
72
73 [1]
74 http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/undertakers/scripts/
75 - --
76 Regards,
77 Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
78 -----BEGIN PGP SIGNATURE-----
79 Version: GnuPG v2.0.17 (GNU/Linux)
80
81 iQIcBAEBCgAGBQJOGam4AAoJEPqDWhW0r/LCYkIP/1xLpdS2fmzXqQaVSBFanYYG
82 lD9/qvhL9NQNuBysVtXPFtq/wDJgON3mPam1r3wdwsTiOhmzKar45m7lWsKf3eCW
83 7lMfJgx3OWDL+TJPigaR/6MVn7I3D7+FWYuv89pv97jHMQBu6QppT2kfEYeD3pth
84 dsv/O1zoXuEDx8M9Brj4zfaaYLAgAqUeh7Jp8rT6/SW2cC9TQ890jw3u3TdfUUE0
85 TMkhOF9iQIm/5j/Jq6vo1r8whZ3wyGs6InDKqT1ZNA1mC/JHXGQQ2ZSvakPlCUsY
86 jxV7f3ccA3BeZK7NH1lcZRDp/zsNBA+sQRWWReQ81AUIHHd/6+zJv26d5EOS2Ihu
87 ynyM7XKQZfv6ezxH1ApuwXzOVJ8U2cuu7arrfhhKwr/JjMf+Y6VFV/70X0KrEBoN
88 /cd87lP791tfIoCi/o94P0m48bYYIY4ZmMXsSuOwTd80fbAGtmqKQ0Bx6EqVku31
89 LtgdlpFSENg0oYQf/aGuvOvnIc0Zmlc9QPjsh7jjLzK7v5USP7p/Q8Q9Ml7pDv50
90 8BoWZ+wowyjKb0/DpWO3N2pXmUh3oHSUw9fI/T2rzW4v9mQQAItkSgySDbRM5RpI
91 yQVO6bqUWiKoM8DowsEfNoL5/JYKKW5idC6s2bSwN6aq9kH4/NXmn0RWI4aZ3529
92 0K+lYaADYA5WCY15SSXZ
93 =DIN6
94 -----END PGP SIGNATURE-----