From: Daniel Drake <dsd@gentoo.org>
To: Gentoo Kernel List <gentoo-kernel@lists.gentoo.org>
Subject: [gentoo-kernel] recruiting update
Date: Sat, 13 Dec 2008 18:10:59 +0000 [thread overview]
Message-ID: <4943FAB3.5020004@gentoo.org> (raw)
Hi,
Thanks to everyone who responded to my recent call for help with kernel
bug-squashing. I replied to a number of emails and was pleasantly
surprised to see a lot of people actually following through. Probably to
the point where some people are a little discouraged or at loose ends
because there aren't immediately enough bugs to go around... (the bug
list is currently the smallest I have seen it in a long time, but more
will come!)
I am going to start recruiting the new contributors to "official" Gentoo
Developer status, which will provide proper recognition for your work,
access to directly contribute to genpatches, and so on.
I will probably start with the most active new contributors in no
particular order. I just wanted to make sure that everyone is aware that
all contributions, even only occasional ones, are very much appreciated,
and I will (in time) recruit anyone who is prepared and able to
contribute even on an occasional basis. Anyone is welcome to remind or
ask me about this and I'll give an honest answer.
The Gentoo recruitment process is a bit long and drawn out, so this
needs to be done one or two people at a time. I have travel plans
starting next month so will become much less active until mid-April, so
my first priority is to make one or two more active people be in a
position less dependent on myself. But I will continue on the recruiting
as long as there are enthusiastic people to recruit, as time allows.
Thanks for your patience!
Daniel
reply other threads:[~2008-12-13 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4943FAB3.5020004@gentoo.org \
--to=dsd@gentoo.org \
--cc=gentoo-kernel@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