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