From: Theo Chatzimichos <tampakrap@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Feedback on recruitment process
Date: Sat, 17 Nov 2012 16:57:38 +0100 [thread overview]
Message-ID: <4590342.EuHlatdsbp@virtuoso> (raw)
In-Reply-To: <50A76C95.1040904@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]
On Saturday 17 of November 2012 10:53:09 Markos Chandras wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Good morning,
>
> Most of you have probably noticed that the recruitment.gentoo.org
> webapp is gone[1]. We(recruiters) are in the process of reworking and
> re-evaluating the recruitment process. Right now, I am asking you to
> comment on the quizzes. Tell us if you think that some of the
> questions are obsolete, or too , or outdated etc. Moreover, if you
> have a new question in mind that you would like to see in the quizzes
> please let me know. Your feedback is valuable for us in order to come
> up with a more up2date process that would satisfy the upcoming
> developers, you as mentors and us as recruiters. I would like to ask
> you to refrain from the usual "oh git will solve everything"
> discussions that will drive this thread out of topic. At this point
> I'd like only developers to comment on this as some of them have been
> mentors and certainly all of them have done the quizzes. Users, former
> developers etc are welcome to join but at this point we need to gather
> feedback from people who have actually gone through this process.
> For your convenience, I've merged both quizzes on a Google doc[2].
>
> [1]http://thread.gmane.org/gmane.linux.gentoo.devel.announce/1783
> [2]https://docs.google.com/document/d/1pqq0ROBc7yggLRsYUKhReYQL68k1XYFZlvfqI
> 4yAt6k/edit
Hello,
the non-technical questions should be formed better, and probably to have
subquestions. For example, for the council question, I have been given answers
from "council is 7 people that take all decisions" to really lengthy ones that
lose the point. So I believe that it should be reformed in 4-5 questions: what
it is, how it performs, what kind of decisions it takes, how it stays alive,
how does it do the elections, who is legible to nominate/participate.
Regarding the technical ones, there is too much duplication as Tomas pointed
out already, especially regarding KEYWORDS so please do something because the
answers are pretty much the same in some of them (or even identical in 2-3 of
them)
And thanks for the google doc.
Theo
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-11-17 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 10:53 [gentoo-project] Feedback on recruitment process Markos Chandras
2012-11-17 11:55 ` Tomáš Chvátal
2012-11-17 12:01 ` Agostino Sarubbo
2012-11-17 15:18 ` Markos Chandras
2012-11-17 15:45 ` Agostino Sarubbo
2012-11-17 18:55 ` Markos Chandras
2012-11-17 15:19 ` Ciaran McCreesh
2012-11-17 15:57 ` Theo Chatzimichos [this message]
2012-11-18 11:25 ` Markos Chandras
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=4590342.EuHlatdsbp@virtuoso \
--to=tampakrap@gentoo.org \
--cc=gentoo-project@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