1 |
On Thu, Aug 1, 2013 at 2:17 PM, Nicolas Sebrecht <nsebrecht@×××××.fr> wrote: |
2 |
> The 01/08/13, Hans de Graaff wrote: |
3 |
> |
4 |
>> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2 |
5 |
>> documents this from the new developer perspective. Note how it says to |
6 |
>> contact the recruiters if you don't already have found a mentor yourself. |
7 |
>> |
8 |
>> There is also http://www.gentoo.org/proj/en/devrel/recruiters/ which |
9 |
>> documents this from the inside, but when I wanted to become a developer I |
10 |
>> found that more useful documentation :-) |
11 |
>> |
12 |
>> So it is explicitly documented. Perhaps not well enough? In that case, |
13 |
>> let us know what you miss. |
14 |
> |
15 |
> I've proposed myself some years ago. Things might have changed since |
16 |
> then but at that time the mail I sent to the dev list got no response. |
17 |
> |
18 |
> Process recruitement is incredibely busy and over-complicated compared |
19 |
> to all other projects I've been involved into. I think this stands like |
20 |
> that because most developers are afraid to give wirte acces to the whole |
21 |
> portage CVS tree to others. |
22 |
> |
23 |
> In all other projects, it's almost a question of subscribing to a |
24 |
> mailing list and send git patches. |
25 |
|
26 |
I don't see the major difference between that and opening a bug and |
27 |
attaching the patch. Only that bugzilla allow to manage the process, |
28 |
not have leftovers, and future people can resume past discussions. |
29 |
|
30 |
> With time, you get direct write |
31 |
> access. |
32 |
|
33 |
In time you can be become either proxy maintainer or gentoo developer |
34 |
(direct access to source repository). |
35 |
|
36 |
> With Gentoo, you have to find a mentor, officially call for |
37 |
> being a member, success the online tests, keep mentored some time. Not |
38 |
> very light and efficient... |
39 |
|
40 |
Can you please suggest a different method to ensure quality? |
41 |
|
42 |
> Now, I'm away from Gentoo and it's fine. :-) |
43 |
> |
44 |
> -- |
45 |
> Nicolas Sebrecht |
46 |
> |