| 1 |
The 01/08/13, Hans de Graaff wrote: |
| 2 |
|
| 3 |
> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2 |
| 4 |
> documents this from the new developer perspective. Note how it says to |
| 5 |
> contact the recruiters if you don't already have found a mentor yourself. |
| 6 |
> |
| 7 |
> There is also http://www.gentoo.org/proj/en/devrel/recruiters/ which |
| 8 |
> documents this from the inside, but when I wanted to become a developer I |
| 9 |
> found that more useful documentation :-) |
| 10 |
> |
| 11 |
> So it is explicitly documented. Perhaps not well enough? In that case, |
| 12 |
> let us know what you miss. |
| 13 |
|
| 14 |
I've proposed myself some years ago. Things might have changed since |
| 15 |
then but at that time the mail I sent to the dev list got no response. |
| 16 |
|
| 17 |
Process recruitement is incredibely busy and over-complicated compared |
| 18 |
to all other projects I've been involved into. I think this stands like |
| 19 |
that because most developers are afraid to give wirte acces to the whole |
| 20 |
portage CVS tree to others. |
| 21 |
|
| 22 |
In all other projects, it's almost a question of subscribing to a |
| 23 |
mailing list and send git patches. With time, you get direct write |
| 24 |
access. With Gentoo, you have to find a mentor, officially call for |
| 25 |
being a member, success the online tests, keep mentored some time. Not |
| 26 |
very light and efficient... |
| 27 |
|
| 28 |
Now, I'm away from Gentoo and it's fine. :-) |
| 29 |
|
| 30 |
-- |
| 31 |
Nicolas Sebrecht |
Archives