public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Recruitment process is moving back to quizzes
Date: Sun, 15 Jul 2012 09:27:31 -0400	[thread overview]
Message-ID: <CAGfcS_nom=yY+3za7paSpCV1FOejoNzAarAKJ5uJa1+FLCvizA@mail.gmail.com> (raw)
In-Reply-To: <20120715125620.37abf782@googlemail.com>

On Sun, Jul 15, 2012 at 7:56 AM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Sun, 15 Jul 2012 13:15:26 +0800
> Ben de Groot <yngwin@gentoo.org> wrote:
>> The first time I did the quizzes, it took me 9 months. After having
>> been away for a couple of years, I recently returned as Gentoo
>> dev, and the second time I did the quizzes it took me 3 months.
>> I've seen others take a long time doing them as well. Davide (pesa),
>> one of our most valued contributors in the Qt team, took close
>> to two years I think.
>
> If it's taking you that long, you're doing something wrong... The
> quizzes are pretty easy, and only test the bare minimum of what you
> should know. They shouldn't take you more than a couple of hours.

I'd be interested in why it was taking so long as well.  I took the
quizzes first when becoming an AT, and later when becoming a dev.  The
level of rigor was much higher of course when becoming a dev - which
was appropriate.  I did struggle because policies were not always
spelled out, so many of the questions took interaction with my mentor
to resolve.  Sometimes the indirectness of some of the questions was
frustrating, but it didn't take more than maybe 8 hours in total with
revisions/etc.  I'd give it my best shot, my mentor would review and
offer hints/suggestions, and we'd iterate.  I learned quite a bit in
the process.

Random thought here - it probably wouldn't hurt to have some kind of
ebuild tutorial that works through a few examples to explain how
ebuilds work, and demonstrate good technique.  That could be useful
not just for developer candidates, but for the community in general.
Our ebuild docs aren't bad at all actually, but they're mainly in the
form of reference now, and something that was more oriented to
teaching might be useful.  Maybe we need something that starts with
"hello world" and goes from there...

Rich



  reply	other threads:[~2012-07-15 13:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14  9:32 [gentoo-dev] Recruitment process is moving back to quizzes Markos Chandras
2012-07-14 20:46 ` Peter Stuge
2012-07-15  5:15   ` Ben de Groot
2012-07-15  9:39     ` Markos Chandras
2012-07-15 10:11       ` Peter Stuge
2012-07-15 13:21         ` Rich Freeman
2012-07-15 17:23         ` Markos Chandras
2012-07-15 11:56     ` Ciaran McCreesh
2012-07-15 13:27       ` Rich Freeman [this message]
2012-07-15 13:45         ` Ben de Groot
2012-07-15 13:50           ` Ciaran McCreesh
2012-07-15 14:32             ` Peter Stuge
2012-07-15 15:24               ` Rich Freeman
2012-07-15 15:08             ` Ben de Groot
2012-07-15 18:17               ` Denis Dupeyron
2012-07-15 10:15 ` Theo Chatzimichos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGfcS_nom=yY+3za7paSpCV1FOejoNzAarAKJ5uJa1+FLCvizA@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox