From: Jon Portnoy <avenj@eris.oppresses.us>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Gentoo Phoenix] recruitment process
Date: Mon, 5 Apr 2010 16:07:01 +0000 [thread overview]
Message-ID: <20100405160701.GA15345@eris.oppresses.us> (raw)
In-Reply-To: <4BB97A39.20500@caf.com.tr>
On Mon, Apr 05, 2010 at 08:50:49AM +0300, Eray Aslan wrote:
> Just replying randomly.
>
> On 05.04.2010 04:33, Tobias Heinlein wrote:
> > I think this is a good starting point to get rid of the "some important
> > questions are too hard to answer" dilemma that can be implemented
> > relatively fast. On top of that I like Sebastian's idea to order the
> > quizzes by difficulty -- this means just ordering by the categories I
> > just mentioned would be sufficient: 1 first, then 2, then 3.
>
> I am not against this idea but frankly, I do not understand what is so
> demotivating about the ebuild quiz. If you get demotivated because of a
> single exam, perhaps the problem is with the motivation and not with the
> exam itself. I took the published quiz just for the fun of it and to
> see where I missed. It is not that long.
>
Agreed...
I've been following this discussion with mixed feelings. When we
originally began using the quiz system the idea was simply to try
to force new developers to RTFM -- and I was not such a fan of the
entire concept (as I recall, the quizzes were a "suggestion" from Daniel).
As it turns out, the quiz system has repeatedly proven itself useful
in another way: developers who whine/bitch/moan and are hesitant to
even attempt to complete the quizzes often turn out to be bitchy,
unmotivated, or unpleasant developers. I don't want to name any names,
but I've seen this often.
IMO, those "boring" "too much like high school" quizzes serve one
extremely valuable function: finding out up front who's a team player
(or at least willing to do something mildly unpleasant for the
Greater Good)
If that's causing potential devs to drop out... perhaps the system is
working as it should? :)
next prev parent reply other threads:[~2010-04-05 16:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 1:33 [gentoo-dev] [Gentoo Phoenix] recruitment process Tobias Heinlein
2010-04-05 5:50 ` Eray Aslan
2010-04-05 16:07 ` Jon Portnoy [this message]
2010-04-05 16:50 ` George Prowse
2010-04-05 17:57 ` Jon Portnoy
2010-04-05 18:28 ` Denis Dupeyron
2010-04-05 18:26 ` Zeerak Mustafa Waseem
2010-04-05 17:35 ` Petteri Räty
2010-04-06 2:16 ` Jorge Manuel B. S. Vicetto
2010-04-06 13:28 ` [gentoo-dev] " Duncan
2010-04-06 16:16 ` Denis Dupeyron
2010-04-05 18:51 ` [gentoo-dev] " Nathan Zachary
2010-04-05 18:59 ` Denis Dupeyron
2010-04-07 17:35 ` Markos Chandras
2010-04-05 7:48 ` Ciaran McCreesh
2010-04-05 8:19 ` Brian Harring
2010-04-05 13:38 ` Richard Freeman
-- strict thread matches above, loose matches on Subject: below --
2010-04-03 13:40 Ben de Groot
2010-04-03 13:53 ` "Paweł Hajdan, Jr."
2010-04-05 2:36 ` Alistair Bush
2010-04-05 8:23 ` Petteri Räty
2010-04-03 13:53 ` George Prowse
2010-04-03 14:05 ` Petteri Räty
2010-04-03 14:22 ` George Prowse
2010-04-03 21:39 ` Sebastian Pipping
2010-04-03 14:03 ` Petteri Räty
2010-04-03 19:00 ` Jesus Rivero (Neurogeek)
2010-04-03 21:48 ` Sebastian Pipping
2010-04-04 9:43 ` Petteri Räty
2010-04-04 16:24 ` Ben de Groot
2010-04-04 15:16 ` basile
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=20100405160701.GA15345@eris.oppresses.us \
--to=avenj@eris.oppresses.us \
--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