From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Gentoo Phoenix] recruitment process
Date: Mon, 05 Apr 2010 09:38:07 -0400 [thread overview]
Message-ID: <4BB9E7BF.40003@gentoo.org> (raw)
In-Reply-To: <20100405084808.2fadb906@snowmobile>
On 04/05/2010 03:48 AM, Ciaran McCreesh wrote:
> On Mon, 05 Apr 2010 03:33:52 +0200
> Tobias Heinlein<keytoaster@gentoo.org> wrote:
>> 3) Questions that aren't that important at all and would just be "nice
>> to know".
>> [snip]
>> Examples for these:
>>
>> 5. What is wrong with using $(somecommand) or `somecommand` or $ARCH
>> inside SRC_URI, DEPEND, etc?
>> [Devmanual, Caching]
>
> How the heck is this not important? Anyone who doesn't immediately know
> the answer to this has absolutely no business touching any ebuild that
> might end up being given to someone else.
>
My concern with these kinds of questions is that there really isn't any
page where we have key gotchas consolidated like "don't execute external
programs in global scope." Sure, it is in the devmanual, and if you
read the whole thing then maybe you might remember that one bit in
particular.
I agree that somebody who doesn't know this particular fact shouldn't be
committing ebuilds. My concern is that we don't really have any way to
make people aware of that particular fact.
Honestly, I think it would be just as effective to simply write up a
single webpage with thou shalt not's, and not make people go hunting all
over the place to figure out the whys. By all means have a link on each
thou shalt not to the reason.
There are lots of people who would be perfectly capable of doing many
developer activities who might not come in knowing about the metadata
cache. They don't need to know the nuts and bolts of how it works, just
what they need to do to avoid problems with it.
In any case, giving hints as to the location of the answer in this kind
of a question seems fine to me. The important thing is that the
candidate dev learn about the potential problem - not that they figure
it out 100% on their own. Still, the socratic method is a good approach
to teaching, so I'm not opposed to the Q&A format of the quiz in
general. We just need to let candidates know that we're there to help
them succeed and the quiz is a tool - the goal isn't to eliminate any
potential contributor who doesn't come to the table knowing as much
about Gentoo as any seasoned dev.
Rich
next prev parent reply other threads:[~2010-04-05 13:38 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
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 [this message]
-- 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=4BB9E7BF.40003@gentoo.org \
--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