From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [Gentoo Phoenix] recruitment process
Date: Sat, 3 Apr 2010 15:40:20 +0200 [thread overview]
Message-ID: <j2he117dbb91004030640n171d6b3u959bd6fadf2190a2@mail.gmail.com> (raw)
On 3 April 2010 13:33, Richard Freeman <rich0@gentoo.org> wrote:
> I really think that the Gentoo recruitment process needs improvement. Right
> now it seems like a LOT of effort is required both to become a Gentoo dev
> and to help somebody become a Gentoo dev. That means we have great people,
> but not many of them.
I agree. So what can we do to improve this process?
I myself am not fond of the quizzes, and from what I've seen most
recruits find them tedious as well. It can be quite demotivating,
maybe because it reminds one too much of highschool or something.
I took a long time myself to finish them, and that wouldn't have
been necessary, as my mentors ensured me I was ready to become a
dev. And I see the same thing happening with some of my own recruits.
They can be ready, but just find the quizzes a chore.
So I think we need to rethink how to do this. What I have found very
helpful is to have my recruits working on actual ebuilds. The
sunrise project is ideally qualified to mold ebuild editors into
shape. Working on official overlays such as qting-edge and/or doing
proxy maintenance is also very helpful.
Recruiters (with some additional manpower) could make a list of
technical issues that recruits need to be aware of, and then gather
a number of ebuilds that display these problems and let recruits
correct some of these, under guidance of their mentors. This may
possibly be more fun and closer to the actual work that is required
of developers.
Of course this doesn't address the organizational side of things, so
we need to come up with something else for that.
Another problem I see is that our documentation seems to be scattered
all over the place. I propose that we make at least one portal page
for (prospective) developers that will link them to all the resources
they might need. It also means our existing documentation needs to
be brought and kept up to date.
Are there any other ideas on how to improve our recruitment process?
--
Ben de Groot
Gentoo Linux Qt project lead developer
next reply other threads:[~2010-04-03 13:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 13:40 Ben de Groot [this message]
2010-04-03 13:53 ` [gentoo-dev] [Gentoo Phoenix] recruitment process "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
2010-04-11 7:52 ` [gentoo-dev] [Gentoo Phoenix] Team : Recruitment Process Markos Chandras
-- strict thread matches above, loose matches on Subject: below --
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-05 18:51 ` 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
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=j2he117dbb91004030640n171d6b3u959bd6fadf2190a2@mail.gmail.com \
--to=yngwin@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