From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NybCe-0000q1-Me for garchives@archives.gentoo.org; Mon, 05 Apr 2010 01:34:12 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 185A2E0ABE; Mon, 5 Apr 2010 01:34:08 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 20C2BE07DA for ; Mon, 5 Apr 2010 01:33:56 +0000 (UTC) Received: from [192.168.2.107] (p5B28A043.dip.t-dialin.net [91.40.160.67]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 462246427B for ; Mon, 5 Apr 2010 01:33:55 +0000 (UTC) Message-ID: <4BB93E00.3070301@gentoo.org> Date: Mon, 05 Apr 2010 03:33:52 +0200 From: Tobias Heinlein User-Agent: Mutt/1.5.16 (2007-06-09) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [Gentoo Phoenix] recruitment process OpenPGP: id=9CE3CA91 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 69514033-606c-4b8e-b8a0-2c6223340bae X-Archives-Hash: 415a15afe3649a139122cf0cdd76b304 I'd first like to extend the idea of bug #312977. It's basically about a different level of detail for each question. I think the quiz questions can be divided into different groups: 1) Questions that are fun to answer. People should either already know the answer, know where to look, or be willing to figure the answers out themselves without a hint to specific docs. 2) Questions about stuff that people NEED to know for day-to-day development, but that aren't much fun to answer. Petteri's proposed level of detail would be appropriate here. 3) Questions that aren't that important at all and would just be "nice to know". These are the ones that make people give up on the quizzes because they are boring and the answers hard to find. Most people would like to see this kind of questions dropped entirely, but recruiter's point is that people should know about them, even though they aren't fun. This is why for these I'd add a more exact pointer to the docs, similar to the way we do in the interviews when a recruit doesn't know an answer. This way they won't be demotivated because they won't have to search for too long, yet know the answer and remember it when they need it someday. Examples for these: 5. What is the Gentoo Foundation? How does one apply for membership and who are eligible? [Gentoo Foundation Bylaws, "Members"] 5. What is wrong with using $(somecommand) or `somecommand` or $ARCH inside SRC_URI, DEPEND, etc? [Devmanual, Caching] 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. As soon as we have implemented that, we can think about how to make the ebuild-related questions more interesting by using tasks and example ebuilds. I guess this part will take a longer time. basile wrote, on 04/04/2010 05:16 PM: > The learning flow should go something like this: > [..] I like that idea. However, I would combine writing the example ebuild (i.e. "doing the task") and answering questions. There's no need to show twice what you have learnt. Also, some of our questions could pretty easily be replaced by doing a task, some cannot.