1 |
On 03/31/18 19:35, Daniel Robbins wrote: |
2 |
> I disagree strongly and think this is unwise because many may contribute |
3 |
> but not have time to go through the recruitment process or any interest in |
4 |
> being part of the project. |
5 |
If someone does not have any interest in being part of the project, why |
6 |
would they take part in the project via User Representatives? |
7 |
|
8 |
As for the lack of time argument, which is a recurring meme, especially |
9 |
as it applies to those without tree access, formal recruiting can be |
10 |
done in trivial amounts of time compared to making any sort of ongoing |
11 |
contributions. If one were to have a mentor and dedicate some time to |
12 |
just getting the quiz answered, without merely spoonfeeding the answers, |
13 |
it should take perhaps a few hours, past that the requirements |
14 |
essentially boil down to making some keys (call it a minute or two), |
15 |
minor interaction via bugzilla (a few more minutes, call it half an |
16 |
hour), and a meeting with Recruiters (mine was brief, but call it an |
17 |
hour, two if you feel like wildly overestimating things). If you are |
18 |
just focusing on the recruitment process itself, the executive summary |
19 |
is: perhaps six hours at worst, more realistically closer to half that, |
20 |
and potentially notably less still. |
21 |
|
22 |
However, we (specifically the forums team) do not typically do it that |
23 |
way for a very simple reason: doing so would be pointless. We recruit |
24 |
based on abilities and interests that are not so much as touched on by |
25 |
the quiz. So we get our recruits up to speed on what they are being |
26 |
recruited for and generally just let the quiz follow. |
27 |
|
28 |
Recruitment for gentoo.git access does necessarily take longer, given |
29 |
that there are multiple quizzes and more questions, but they are also |
30 |
biases quite a bit more heavily toward specific technical information |
31 |
that those being recruited should, by and large, already know before |
32 |
they reach the point of formal recruiting. Recruits do not, yet, spring |
33 |
forth from pods with no prior life experience. Recruits come in via |
34 |
filing bugs and submitting patches with are then reviewed, and modified, |
35 |
and the reasons for the modifications are discussed which provides an |
36 |
education in what the policies in effect are and how they are |
37 |
implemented, which in turn typically covers a significant fraction of |
38 |
the material on the quiz, the balance of which their mentor should cover |
39 |
with them. As such, even for gentoo.git access, recruitment itself is |
40 |
not, has not been, and is not likely to become the major time sink, the |
41 |
actual work being done is. |
42 |
|
43 |
> Also, it is critical that there is |
44 |
> representation from outside of the project proper, as the Gentoo developer |
45 |
> world can become (many will argue that is already has become) a kind of |
46 |
> mono-culture. |
47 |
A monoculture of people who are adamantly for and against many of the |
48 |
same packages and policies, and those who scarcely care either way so |
49 |
long as things work. A monoculture of people who get along reasonably |
50 |
well with virtually anyone and those who manage to get along poorly with |
51 |
virtually everyone. A monoculture of people who deliberately try to |
52 |
throw their weight around and those who simply try to work on their |
53 |
corner of their project. A very extraordinarily diverse monoculture, |
54 |
especially given its relatively small, and dare I call it cellular, nature. |