Gentoo Archives: gentoo-dev

From: "Petteri R├Ąty" <betelgeuse@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [Gentoo Phoenix] recruitment process
Date: Sun, 04 Apr 2010 09:43:40
Message-Id: 4BB85F40.1010802@gentoo.org
In Reply to: Re: [gentoo-dev] [Gentoo Phoenix] recruitment process by Sebastian Pipping
1 On 04/04/2010 12:48 AM, Sebastian Pipping wrote:
2 > On 04/03/10 21:00, Jesus Rivero (Neurogeek) wrote:
3 >> Maybe if we could find the way to make the knowledge found in
4 >> quizzes be more "exciting" to new devs, then we could still have a
5 >> strong recruitment process without the burden of completing the
6 >> quizzes. So, what I propose is to transform the "quizzes" part of the
7 >> process into a list of tasks the prospect should complete in order to
8 >> gain the necessary ability to "pass". This ability could be measured
9 >> in points or just by task completed.
10 >
11 > Nice idea!
12 >
13 >
14 >> This doesn't address them either. But I really don't think this is
15 >> the main issue that causes the problem :) So I guess these questions
16 >> could remain in one "easy" quiz.
17 >
18 > While you mention the non-technical part: I imagine a gain out of moving
19 > that part to the very end of recruiting: to when people know they almost
20 > made it. Especially putting up these questions first, turns some people
21 > away too: The problem is they get the wrong impression that being will
22 > be about these boring things later on, but it isn't.
23 >
24 > Betelgeuse, what do you think?
25 >
26
27 Mentors can already suggest their students to do them in reverse order.
28 As always patches to separate technical and organizational stuff to
29 their own quizzes are accepted. My time on recruiting is quite maxed out
30 already. Doing this means just not fixing the quizzes but bringing all
31 the recruiting documentation up2date.
32
33 Regards,
34 Petteri

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] [Gentoo Phoenix] recruitment process Ben de Groot <yngwin@g.o>