1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 30-06-2010 00:12, Sebastian Pipping wrote: |
5 |
> Jorge, |
6 |
> |
7 |
> |
8 |
> On 06/17/10 03:10, Jorge Manuel B. S. Vicetto wrote: |
9 |
>> So everyone can have an idea, I'd suggest looking at the list of |
10 |
>> the open retirement bugs[1]. As there seems to be some confusion |
11 |
>> about the policies to retire developers, please read the |
12 |
>> undertakers page[2]. |
13 |
> |
14 |
> Interesting links, thanks. |
15 |
> |
16 |
> |
17 |
> Two things come to my mind: Step 2 of the undertakers page reads: |
18 |
> |
19 |
> "When sending an email to the developer in question, make sure you |
20 |
> tell him, that he might get retired due to being inactive." |
21 |
> |
22 |
> If I'm not mistaken this is telling the developer about potential |
23 |
> retirement on first direct contact. If that's true I don't |
24 |
> consider it very sensitive. After all our goal is to keep that |
25 |
> developer in, not out. So my proposal is: please add another two |
26 |
> weeks and a second mail so the first one does not mention |
27 |
> retirement. How about that? |
28 |
> |
29 |
|
30 |
One aspect of the undertakers work that is not mentioned in the |
31 |
project page is that we generally start our work from the mails people |
32 |
send announcing their retirement and from the automatic activity mails |
33 |
that are sent to our alias. |
34 |
So as stated in step 2 and after doing a filtering of active people |
35 |
from the above mails, we start by approaching developers, their |
36 |
project(s) lead(s) and the developers themselves trying to investigate |
37 |
whether a developer is MIA, really stopped contributing or if he / she |
38 |
is active in other ways. We only move on to step 3 where we reopen the |
39 |
bug and start sending the official e-mails about possible retirement, |
40 |
if we are convinced the developer is really inactive. |
41 |
You have a very good point and one that the undertakers team really |
42 |
embraces - the goal of the undertakers work is not to "kick" |
43 |
developers out, but to get them to resume contribution to the project. |
44 |
There are however certain minimal levels of commitment that we expect |
45 |
and ask from developers. |
46 |
|
47 |
> |
48 |
> The other thing is: what are the reasons to retire inactive |
49 |
> developers? Are these reasons documented somewhere? |
50 |
|
51 |
There are some considerations about retirement in section 3[1] of the |
52 |
"Developer Relations Policy Guide"[2] and the undertakers project |
53 |
page[3] states that undertakers "handle{s} developer retirement, both |
54 |
when developers announce their retirement as well as due to developer |
55 |
inactivity." |
56 |
|
57 |
The following is a list with a few reasons to retire inactive developers: |
58 |
|
59 |
* security considerations regarding access to Gentoo infra, including |
60 |
tampering of the tree |
61 |
* need to ensure that maintainers are accessible, take care of |
62 |
packages and bugs and that they reply on due time to community |
63 |
contacts and requests |
64 |
* desire to have project and team membership, as well as package |
65 |
maintenance reflect reality |
66 |
* make it clear what areas of the project are understaffed and what |
67 |
packages require new maintainers |
68 |
* need to ensure that developers keep up to date regarding policies |
69 |
and use of the tree by using it |
70 |
|
71 |
[1] - http://www.gentoo.org/proj/en/devrel/policy.xml#doc_chap3 |
72 |
[2] - http://www.gentoo.org/proj/en/devrel/policy.xml |
73 |
[3] - |
74 |
http://www.gentoo.org/proj/en/devrel/undertakers/index.xml#doc_chap1 |
75 |
|
76 |
> Thanks! |
77 |
> |
78 |
> |
79 |
> |
80 |
> Sebastian |
81 |
> |
82 |
|
83 |
- -- |
84 |
Regards, |
85 |
|
86 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
87 |
Gentoo- forums / Userrel / Devrel / KDE / Elections |
88 |
-----BEGIN PGP SIGNATURE----- |
89 |
Version: GnuPG v2.0.15 (GNU/Linux) |
90 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
91 |
|
92 |
iQIcBAEBAgAGBQJMKrR3AAoJEC8ZTXQF1qEPvDUQAKyvWFyJikHGk/oieYeGUQjH |
93 |
C6+t9NRGft1r2vjswRqtkFkyxIVfOBLQSXeFAP+fZa++q9o6E/F5ovqudg3V0t7s |
94 |
u1sXU3tHr2hTF9F78hNlkaUT0P1UIIV1Cj5/FYTrWcgPzYCL9aPkeFOKppP+9PPN |
95 |
Lpn1jLWrGvXnf6wICE41hmYSuBs43om1GxyNZz1G0nXE2YKUYqk9MUYGPA/PIaOp |
96 |
wotxPo6BZ2QBY5y+a+WxjHScaFQXJASPVlh+TwkEOZFUxnapVE4pGo5E1zRW3+iV |
97 |
D7F3efgUXCHTVMoV/iy3GM1Usx3XY3UdGySdKTqwgnISboVKLLJbTkjaENt8Cny0 |
98 |
Pqkc5KySObavmSlKj0b43/kfWegVwiwrdJt2a00LT/2YQOK/kxAv6w/lpJOaffin |
99 |
AT0KyGH10tObTIUcFcHjo4EZE6UdX5otYMKfokOzBuDiz2BCOQa95shDkIuJ2tcw |
100 |
pVSVYjVTyV1Ax2S/BNomVezmY24RCIjRkmxnxwyOfZhZhwprDoS2V9HQeFqwslfh |
101 |
7EC9e+rTaqy+2WEHkLQ6Lte2B+tF1g56YA2fv+wKcbcP9Syltin1VnQvke6hS2eR |
102 |
jYYK3cUa0okB2G5FE5PmWsCKjfwoVyBQ8707ahGyf/QQbyiSvnTb8yjO9WP+CH7/ |
103 |
QvFZ7O+XzRzn5JUTy8pp |
104 |
=nZ75 |
105 |
-----END PGP SIGNATURE----- |