1 |
Hi, |
2 |
|
3 |
Here's a quick pre-GLEP for review. It's a supplement to GLEP 39 that |
4 |
defines who Gentoo Developer is (GLEP 39 mentions devs a lot but doesn't |
5 |
say who they are). Alike 39, it's purely information -- it doesn't |
6 |
state a policy, just notes the status quo. It is also minimal |
7 |
and focuses on linking the policies of relevant teams. |
8 |
|
9 |
Please review. |
10 |
|
11 |
--- |
12 |
GLEP: 76 |
13 |
Title: Gentoo Developer status |
14 |
Author: Michał Górny <mgorny@g.o> |
15 |
Type: Informational |
16 |
Status: Draft |
17 |
Version: 1 |
18 |
Created: 2018-04-11 |
19 |
Last-Modified: 2018-04-13 |
20 |
Post-History: |
21 |
Content-Type: text/x-rst |
22 |
Requires: 39 |
23 |
Replaces: |
24 |
--- |
25 |
|
26 |
Abstract |
27 |
======== |
28 |
|
29 |
This GLEP aims to supplement GLEP 39 [#GLEP39]_ with the definition |
30 |
of *Gentoo Developer*. It shortly indicates the policies relevant |
31 |
to obtaining, preserving and revoking the Developer status. |
32 |
|
33 |
|
34 |
Motivation |
35 |
========== |
36 |
|
37 |
Most of Gentoo's metastructure is explained in GLEP 39 [#GLEP39]_. |
38 |
However, while this GLEP is focused around Gentoo Developers, it does |
39 |
not define whom they precisely are. It lacks a clear statement of how |
40 |
new developers are recruited, and for how long they hold the developer |
41 |
status. |
42 |
|
43 |
The ‘status quo’ can be found across different Gentoo websites. |
44 |
The recruitment procedure (from user perspective) is described |
45 |
on the main site [#BECOME-A-DEV]_. The Recruiters [#RECRUITERS]_, |
46 |
Undertakers [#UNDERTAKERS]_ and Community Relation [#COMREL]_ teams |
47 |
provide their relevant policies. However, there seems to be no single |
48 |
document binding all of them together. This GLEP aims to be precisely |
49 |
that. |
50 |
|
51 |
|
52 |
Specification |
53 |
============= |
54 |
|
55 |
A *Gentoo Developer* is a person who has successfully passed |
56 |
the recruitment procedure (as defined at the time of his/her joining) |
57 |
and is actively contributing to Gentoo Linux in one or both |
58 |
of the following areas: |
59 |
|
60 |
1. Gentoo ebuild maintenance (either individual or through a project); |
61 |
with activity being determined through the official Gentoo repository |
62 |
commits. |
63 |
|
64 |
2. Contributing to the present Gentoo projects [#PROJECTS]_; with |
65 |
activity being determined at the discretion of project leads. |
66 |
|
67 |
The admission of new Developers is done by the *Recruiters* project |
68 |
[#RECRUITERS]_ upon asserting that the candidate has the necessary |
69 |
skills and motivation to actively contribute to Gentoo as outlined |
70 |
above, provided recent contributions to the specified areas. The exact |
71 |
policies and procedures are specified by the Recruiters project. |
72 |
|
73 |
The removal of Developers is done by the *Undertakers* project |
74 |
[#UNDERTAKERS]_. The Developer status can be revoked in one |
75 |
of the following conditions: |
76 |
|
77 |
- on an explicit request from the Developer himself/herself, |
78 |
|
79 |
- upon determining that the Developer is no longer actively contributing |
80 |
to Gentoo, |
81 |
|
82 |
- as a result of disciplinary action taken by the *Community Relations* |
83 |
project [#COMREL]_ or another explicitly authorized entity. |
84 |
|
85 |
The exact policies and procedures are specified by the Undertakers |
86 |
project. |
87 |
|
88 |
|
89 |
Rationale |
90 |
========= |
91 |
|
92 |
This GLEP does not introduce any new policies but merely attempts to |
93 |
document the current standing practices. It aims to supplement GLEP 39 |
94 |
[#GLEP39]_ with the details necessary to understand who Gentoo |
95 |
Developers are, in context of the metastructure defined there. |
96 |
It does not mean to replace or thoroughly copy the relevant policies. |
97 |
|
98 |
Only the details deemed most important and relevant are listed: |
99 |
explanation whom Gentoo Developers are, what are their responsibilities, |
100 |
what are the requirements for recruiting them and the possibilities of |
101 |
their retirement. The teams responsible for handling both of those |
102 |
processes and defining the detailed policies are explicitly indicated. |
103 |
|
104 |
The specific policy details were intentionally left out to avoid having |
105 |
to perform frequent updates to this GLEP. This includes the exact |
106 |
procedures, ``repo/gentoo`` commit access, devaway system, etc. |
107 |
|
108 |
|
109 |
References |
110 |
========== |
111 |
|
112 |
.. [#GLEP39] GLEP 39: An "old-school" metastructure proposal with "boot |
113 |
for being a slacker" |
114 |
(https://www.gentoo.org/glep/glep-0039.html) |
115 |
|
116 |
.. [#BECOME-A-DEV] Become a developer - Gentoo Linux |
117 |
(https://www.gentoo.org/get-involved/become-developer/) |
118 |
|
119 |
.. [#RECRUITERS] Project:Recruiters - Gentoo Wiki |
120 |
(https://wiki.gentoo.org/wiki/Project:Recruiters) |
121 |
|
122 |
.. [#UNDERTAKERS] Project:Undertakers - Gentoo Wiki |
123 |
(https://wiki.gentoo.org/wiki/Project:Undertakers) |
124 |
|
125 |
.. [#COMREL] Project:ComRel - Gentoo Wiki |
126 |
(https://wiki.gentoo.org/wiki/Project:ComRel) |
127 |
|
128 |
.. [#PROJECTS] Project:Gentoo - Gentoo Wiki |
129 |
(https://wiki.gentoo.org/wiki/Project:Gentoo) |
130 |
|
131 |
|
132 |
Copyright |
133 |
========= |
134 |
This work is licensed under the Creative Commons Attribution-ShareAlike |
135 |
3.0 Unported License. To view a copy of this license, visit |
136 |
http://creativecommons.org/licenses/by-sa/3.0/. |
137 |
|
138 |
-- |
139 |
Best regards, |
140 |
Michał Górny |