1 |
(Targeting one specific comment here) |
2 |
|
3 |
On 10/03/2016 11:04 AM, Rich Freeman wrote: |
4 |
> [snip] |
5 |
> Ultimately if you want to rejoin Gentoo you're going to have to |
6 |
> convince either Comrel or the Council that you're not going to create |
7 |
> trouble. |
8 |
> [snip] |
9 |
|
10 |
Are you speaking for William's specific situation, or in general? I |
11 |
never (knowingly) spoke with any member of Comrel in order to qualify |
12 |
for developer status (my mentors were pchrist and heroxbd, my recruiters |
13 |
were jlec and zlogene). Granted, I came up mostly through proxy-maint |
14 |
and haven't gone out of my way to stir the pot, but it seems to me that |
15 |
William may have a point and it might be worth investigating Comrel's |
16 |
role in Gentoo and whether or not it's a net positive for the project. |
17 |
Do we have a transparent mission for Comrel? Is there a way to measure |
18 |
their impact and progress? The wiki [1] has a few pages, but they appear |
19 |
to be "ported over" from the old website. There are still mentions of |
20 |
CVS, even, so it's clear they haven't been touched too much. It appears |
21 |
ComRel is not related to the acceptance of a developer at all; instead |
22 |
it's left up to Recruiters whether a new developer is satisfactory[2]: |
23 |
|
24 |
(paragraph "Jumping the gap", fetched 2016-10-06) |
25 |
> After your mentor and the Gentoo Recruiters have reviewed your quiz |
26 |
> and deemed it to be of a suitable standard, you should send it along |
27 |
> with a public SSH2 DSA key (e.g. id_dsa.pub) to the Gentoo |
28 |
> Recruiters. If the Recruiters consider your quiz to be of a |
29 |
> satisfactory standard, they will set you up with the services that |
30 |
> you require. |
31 |
> |
32 |
> After this time, you enter a "probationary period" of 30 days during |
33 |
> which your mentor is responsible for your actions, providing |
34 |
> accountability - also, Gentoo Recruiters may reject new developers |
35 |
> during this time if they feel it is appropriate. |
36 |
|
37 |
Additionally, it appears that rejoining devs are merely treated like new |
38 |
devs. Or at least, *should* be[3]: |
39 |
|
40 |
> If the developer later returns, the same initial recruitment bug is |
41 |
> used to track it. Returning developers are subject to the same |
42 |
> criteria as a first-time developer and must go through the same steps |
43 |
> to rejoin Gentoo. |
44 |
|
45 |
Given the above, I have to question the validity of Comrel's involvement |
46 |
and ask why things that (allegedly?) happened eight years ago are still |
47 |
relevant. As a case study, who else has had to appeal Comrel or the |
48 |
Council to rejoin Gentoo? |
49 |
|
50 |
I think organizationally that each project deserves equal scrutiny into |
51 |
its workings and whether or not they are improving Gentoo as a whole. |
52 |
That includes Comrel and arguably *any* project within Gentoo, imo. |
53 |
|
54 |
I'm only writing this because, for better or worse, the community side |
55 |
of Gentoo's been put in the spotlight lately and if there are any |
56 |
problems I hope that we can deal with them in constructive, adult ways. |
57 |
If that means improving and clarifying the language in our policies -- |
58 |
hopefully simplifying and making them more concrete -- then I'm in favor |
59 |
of looking more into this. |
60 |
|
61 |
As usual, this is just my two cents, offered only because I hope I would |
62 |
not be treated this way if I were to come back to Gentoo after leaving. |
63 |
(That said, I have no current plans of leaving Gentoo. It's just |
64 |
something to think about.) Thanks for reading. |
65 |
|
66 |
~zlg |
67 |
|
68 |
[1]: |
69 |
https://wiki.gentoo.org/wiki/Project:ComRel/Developer_Handbook/Etiquette_policy |
70 |
[2]: |
71 |
https://wiki.gentoo.org/wiki/Project:ComRel/Developer_Handbook/Becoming_a_developer |
72 |
[3]: |
73 |
https://wiki.gentoo.org/wiki/Project:Recruiters#What_does_the_recruitment_process_involve.3F |
74 |
-- |
75 |
Daniel Campbell - Gentoo Developer |
76 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
77 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |