1 |
Hello everyone, |
2 |
|
3 |
I would like to propose to the community a new policy in the process of |
4 |
"becoming a developer". Here is the initial draft, do not hesitate to |
5 |
point out anything that needs to be discussed. |
6 |
|
7 |
Abstract |
8 |
|
9 |
Given the necessity of testing and stabilizing software in Gentoo Linux |
10 |
and the ammount of testers is not enough to test all the packages on |
11 |
the given architectures, this GLEP proposes to make the "testing" and |
12 |
"stabilization" processes a required stage to become a Gentoo Linux |
13 |
Developer. |
14 |
|
15 |
|
16 |
Motivation |
17 |
|
18 |
The necessity of manpower in Gentoo Linux is obvious and several |
19 |
projects need more people to be able to achieve their goals. One |
20 |
critical project is the Arch testers project, which needs people to be |
21 |
able to know the procedure to test and mark as stable a given package, |
22 |
this impacts on the whole community because if arch testers are not |
23 |
capable to test all the needed packages, all the other projects can't |
24 |
go further with their goals. |
25 |
|
26 |
At this point, the process to become a Gentoo Developer does not |
27 |
explicitly require testing and stabilization. As this part is crucial |
28 |
to better understand how to fix ebuilds, each future developer should |
29 |
know the procedure to test and stabilize not only their own packages, |
30 |
but to help other developers in the stabilization work. |
31 |
|
32 |
The AT Project was created on January 2005 to reduce the developer's |
33 |
load and the amount of open keywording bugs for the amd64 porting team. |
34 |
Since then many users have volunteered to become ATs and after that |
35 |
became full developers. GLEP 41 already tried to give arch testers a |
36 |
"staff" status in the community, but rather than creating a new status, |
37 |
this new "stage" in the "becoming developer" procedure should be |
38 |
considered as a test of perseverance. At the same time, this is a great |
39 |
way to teach gentoo users how portage works and how to debug their |
40 |
future ebuilds. |
41 |
|
42 |
Prepare the next generation of developers to be able to test and |
43 |
stabilize their own packages, and help other devs in stabilization, |
44 |
would benefit the whole community and give all mentors, recruiters and |
45 |
users wanting to become a official gentoo developer a starting point |
46 |
with endless work to do, and at the same time mentors and recruiters |
47 |
would have a place to look for prospectives developers. |
48 |
|
49 |
|
50 |
Specification |
51 |
|
52 |
In order to stablish this new policy, we need to complete this list of |
53 |
tasks (minimun required in my opinion): |
54 |
|
55 |
-As test and stabilization is arch-based, we need all AT teams to try |
56 |
to prepare an "official" procedure (all of them have very good |
57 |
guidelines right now). |
58 |
|
59 |
-Mentors and recruiters should encourage recruits to test as much as |
60 |
they can, on all the given arch they are interested to, or have access |
61 |
to. |
62 |
|
63 |
-The official ebuild-quiz already has an specific "arch testing" |
64 |
question, maybe as a Proof of Concept, the recruit should add bugs |
65 |
where he/she could proof that he knows the testing procedure. |
66 |
|
67 |
-As many users starting in gentoo will start by testing and |
68 |
stabilization, AT teams would need to remember that they would interact |
69 |
with maybe not so experienced users and try to make the procedure as |
70 |
clear as posible to follow. |
71 |
|
72 |
|
73 |
Rationale |
74 |
|
75 |
This solution aims to solve a more long-term problem, which is the |
76 |
necessity of having developers prepared to start a stabilization |
77 |
process if needed and not depending on an arch tester. The reality is |
78 |
that most current Gentoo Developers and Projects are overwhelmed with |
79 |
the ammount of work, but if all developers could help by testing |
80 |
another's package, maybe this could reduce the work or at least the |
81 |
time spent waiting for stabilization. |
82 |
|
83 |
|
84 |
Copyright |
85 |
|
86 |
This work is lecensed under the Creative Commons Attribution-ShareAlike |
87 |
3.0 Unported License. To view a copy of this license, visit https://cre |
88 |
ativecommons.org/licences/by-sa/3.0 |
89 |
|
90 |
|
91 |
Christopher Díaz Riveros ChrisADR |