Gentoo Archives: gentoo-dev

From: Denis Dupeyron <calchan@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [Gentoo Phoenix] recruitment process
Date: Mon, 05 Apr 2010 18:28:57
In Reply to: Re: [gentoo-dev] [Gentoo Phoenix] recruitment process by Jon Portnoy
1 On Mon, Apr 5, 2010 at 11:57 AM, Jon Portnoy <avenj@××××××××××××××.us> wrote:
2 > Which is all well and good -- the "you wrote some ebuilds so here's
3 > your commit privs and" approach to recruitment worked great
4 > when Gentoo had a few dozen developers.
5 >
6 > Today QA is a bit more important, and development is often rather more
7 > complex than "new version, bump the ebuild" -- it's important that new
8 > developers have a firm understanding of ebuild complexities.
10 That's a very important point. On one side there are developers and
11 would-be developers who want an easier way to recruit people. Most
12 ideas revolve around lowering the technical/social barriers. On the
13 other side there's QA and a bunch of other developers who want fewer
14 people screwing up the tree. Those are proponents of being stricter
15 during the recruiting process (i.e. in the end recruiting fewer
16 people) and firing more devs.
18 None of them though help the poor guys in the middle. Those are the
19 recruiters who could swing completely one way or the other for
20 simplicity, or be more subtle and try and make the best out of the
21 situation and resources.
23 When you're all done barking, and in case you really consider helping
24 here are two things you can do:
25 - join the recruiters
26 - actually *mentor* people to become developers. And by that I don't
27 mean passing them your quiz answers, but really training them and
28 preparing them to become good and well behaved developers. When people
29 ask me how to go about that my usual answer is do as you were teaching
30 your son/little brother how to fly fish (or replace fly fishing with
31 what you do best). Start from the start, progress from there, don't
32 overlook any aspect of the art (there's more to being a dev than
33 writing ebuilds), and be ready to spend hours explaining and
34 re-explaining. If your recruit doesn't get it then it can only be your
35 fault, so try harder.
37 Before you replace/change a system you should first try and make it work.
39 > II don't even like resurfacing to post to -dev.
40 > Just here to offer some insight on why we originally kept the quiz system.
42 Hi Jon, long time no see. Thanks for doing that.
44 Denis.