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