1 |
Okay, let me explain in detail. |
2 |
|
3 |
Undertakers contact devs who didn't touch CVS for at least two months, |
4 |
are considered inactive in the bugzilla and have no current .away set. |
5 |
|
6 |
After the initial contact, something like 3/4 of e-mailed people |
7 |
respond very quickly and explain why they are gone (usually family and |
8 |
work trouble, weddings, army service, health issues, moving out/in and |
9 |
so on, so called real life) and in such cases we do not retire them |
10 |
but let them resolve whatever trouble they are in and return to the |
11 |
project afterwards. |
12 |
|
13 |
There are dozens of devs in the project who had such a conversation |
14 |
with me or other undertakers and all can confirm retirement was |
15 |
abandoned right away after they gave valid reasons for their absence |
16 |
and the only consequence was poking about missing .away and asking |
17 |
when they are planning to get back to work. |
18 |
|
19 |
Those people wouldn't even be contacted if their .aways stated why |
20 |
they are gone and for how long. Therefore a REMINDER: Please do set |
21 |
your .away. Thanks. |
22 |
|
23 |
The rest are usually people who already gave up on the project, just |
24 |
for various reasons didn't say bye yet. They often have no commits for |
25 |
many months despite undertakers poking them a bunch of times. Half a |
26 |
year period without even touching CVS and bugs isn't that uncommon for |
27 |
them. I can give you specific examples if you really want some. I'd |
28 |
prefer to avoid pointing fingers at people though. |
29 |
|
30 |
Those folks either say goodbye to everyone after being contacted by us |
31 |
or do not respond at all, in which case, if we get no response to our |
32 |
two e-mails and an open retirement bug from them after more than a |
33 |
month, we consider them missing in action and go on with their |
34 |
retirement. If they appear suddenly at any point of this procedure and |
35 |
say they want to stay, we either abandon retirement completely or only |
36 |
send them to recruiters to redo their quizzes if their absence was |
37 |
extremely long. |
38 |
|
39 |
I don't think how we can proceed differently in above kinds of |
40 |
situations. Do you suggest we stopped e-mailing people who seem gone |
41 |
from the project (how would we find out those who are really gone |
42 |
then?), stopped retiring people who mail -dev/-core and say goodbye or |
43 |
stopped retiring people who aren't responding to their mail and bugs |
44 |
named "Retire: Person's Name" for months? |
45 |
|
46 |
There's only one controversial group of inactive devs: |
47 |
|
48 |
There are some people who would prefer to stay in the project although |
49 |
they can't really give a good reason what for. Usually they claim they |
50 |
belong to a number of projects although they don't put any regular |
51 |
work into any of them and leads of this projects often haven't even |
52 |
heard there's such a person on board. They sometimes were members of |
53 |
this projects years ago, sometimes wanted to be members and sometimes |
54 |
only imagine they are members of them. I can give specific examples if |
55 |
you insist. |
56 |
|
57 |
Those we try to encourage to find a new job within Gentoo and often |
58 |
they do. I can name one who yesterday did start his new Gentoo work |
59 |
after years of slacking. :-) |
60 |
|
61 |
They are the smallest group of those we contact and process, I could |
62 |
maybe name 5 or 6 of those currently in Gentoo and that's it. There's |
63 |
no pending retirement of such a person currently. |
64 |
|
65 |
Really. Situation you name, when someone wanted to stay in Gentoo |
66 |
despite not doing any actual work and got retired happened once or |
67 |
maybe twice during the last year out of about a hundred retirements we |
68 |
have processed. And all were extreme cases of close to zero activity |
69 |
over many years with no promise of it ever increasing. We consider |
70 |
those very carefully, they are always consulted with devrel lead. This |
71 |
kind of decision isn't made lightly I can assure you. |
72 |
|
73 |
Finally, if someone really wants to be a dev but got retired, he can |
74 |
return to Gentoo within couple of weeks by reopening his retirement |
75 |
bug, submitting quizzes to recruiters and waiting to get useradded. |
76 |
Recruiters process returning devs extremely fast so returning to |
77 |
Gentoo if someone really wants to isn't a problem at all. And there's |
78 |
absolutely no way anyone from undertakers could stop someone from |
79 |
being recruited again. |
80 |
|
81 |
So summarising, the situation you're complaining about is extremely |
82 |
marginal. You are invited to subscribe to retirement@ alias and read |
83 |
its logs on bugzilla and see for yourself how rare occurrence it is. |
84 |
|
85 |
I hope I explained everything completely. I'm happy to take questions |
86 |
if you have any, and of course am open to suggestions. |
87 |
|
88 |
Kind regards, |
89 |
|
90 |
Lukasz Damentko |