1 |
Hi, |
2 |
|
3 |
On Sun, 01 Oct 2017 18:13:32 -0500 Christopher Díaz wrote: |
4 |
> Hello everyone, |
5 |
> |
6 |
> I would like to propose to the community a new policy in the process of |
7 |
> "becoming a developer". Here is the initial draft, do not hesitate to |
8 |
> point out anything that needs to be discussed. |
9 |
|
10 |
This will result in having less developers and at the end of the |
11 |
day less arch testing and stabilization. |
12 |
|
13 |
Our recruitment bar is already quite high. While ensuring basic |
14 |
mandatory skills is OK and understandable, we should not offload |
15 |
dirty work on newbies. The same way we may demand work in many |
16 |
other understaffed areas and will have less and less new developers. |
17 |
|
18 |
Besides, it is not mandatory for developers to use stable |
19 |
themselves and some of us are using stable only on occasion or not |
20 |
at all, because of $reasons. For some people stable is a perfect |
21 |
fit, for others it is not practical. |
22 |
|
23 |
> Prepare the next generation of developers to be able to test and |
24 |
> stabilize their own packages, and help other devs in stabilization, |
25 |
> would benefit the whole community and give all mentors, recruiters and |
26 |
> users wanting to become a official gentoo developer a starting point |
27 |
> with endless work to do, and at the same time mentors and recruiters |
28 |
> would have a place to look for prospectives developers. |
29 |
|
30 |
Problem is not in current developers being unable to stabilize |
31 |
their packages due to insufficient skills. Problem is in: |
32 |
|
33 |
a) lack of hardware with ready setup access, especially for rare |
34 |
arches; |
35 |
|
36 |
b) our rules forbidding developers to stabilize packages |
37 |
themselves if they are not on the arch team; the only exception is |
38 |
amd64 with an unwritten policy allowing developers to stabilize |
39 |
stuff themselves. |
40 |
|
41 |
Best regards, |
42 |
Andrew Savchenko |