From: "Peter" <sw98234@hotmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Delay in approval of new developers
Date: Fri, 22 Sep 2006 11:35:17 +0000 (UTC) [thread overview]
Message-ID: <ef0hpk$aqj$2@sea.gmane.org> (raw)
In-Reply-To: 4513C5C2.3030207@sejo.be
On Fri, 22 Sep 2006 13:15:14 +0200, Jochen Maes wrote:
snip...
>> glad you were an exception.
>>
>>
> glad i never knew you when i was a gentoo dev... I know one thing, you
> won't ever get a hump out of me!
You're arguing a different point. I was commenting on the time delay, and
you responded with how difficult it is to be a recruiter. If the delay is
long then there is a problem. If you run a business and you want to hire
someone, yet you wait and wait and wait, it's quite possible the recruit
may accept another position. That's a loss to you. Same with potential
gentoo developers. When someone goes through the trouble to complete
tests, work with his/her mentor, spend time on bz, etc., the least they
can expect is courteous response when they choose to become a dev.
Perusing through recruitment bugs, you can see long lapses. It IS
inexcusable.
Yes, everyone does gentoo voluntarily, but that does not mean less should
be expected. It reminds me of the time my 5 year old cousin sadly was in
the hospital, and the nurse needed to take yet another blood sample. The
nurse said "I'm sorry I have to take blood again. I don't like to hurt
little boys." To which my very sharp cousin replied, "So, why are you in
this business?"
If a gentoo dev joins a particular project to perform a particular task,
he/she IS making a commitment to it. The dev should have known in advance
what's expected and the time required. AFAIK recruiters are hardly
overworked. There is no overfull pipeline of dev recruits banging on the
doors.
Simple courtesy requires they handle recruiting bugs quickly and
efficiently with either a Welcome or a thumbs down. Dragging the
recruitment out only makes it harder to get new recruits. They are, in
effect, working against themselves and their own goal.
> glad i never knew you when i was a gentoo dev
I have been recruited 3 times to be a dev, and declined. I find the gentoo
hierarchy and organization stifling and the amount of roadblocks to
progress ridiculous.
I appreciate your POV. Yes, you can't expect too much from volunteers.
But, in a worldwide linux distribution, which is run more or less like a
business, there is a higher standard that should be adhered to. I don't
accept slackers or inefficiency in my business, and nor should gentoo.
Why are you no longer a gentoo-dev, btw?
--
Peter
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-22 11:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 17:55 [gentoo-dev] seeds, GLEPs, and projects Grant Goodyear
2006-09-21 18:28 ` Simon Stelling
2006-09-21 20:03 ` Joshua Jackson
2006-09-21 20:34 ` Ciaran McCreesh
2006-09-21 20:49 ` Simon Stelling
2006-09-21 21:01 ` Mike Pagano
2006-09-21 21:43 ` [gentoo-dev] " Peter
2006-09-22 9:25 ` [gentoo-dev] Delay in approval of new developers Andrew Ross
2006-09-22 10:47 ` [gentoo-dev] " Peter
2006-09-22 11:15 ` Jochen Maes
2006-09-22 11:35 ` Peter [this message]
2006-09-22 12:14 ` Jochen Maes
2006-09-22 12:29 ` Peter
2006-09-22 12:44 ` Simon Stelling
2006-09-22 12:55 ` Seemant Kulleen
2006-09-22 13:26 ` Peter
2006-09-22 13:42 ` Seemant Kulleen
2006-09-22 14:13 ` Chris Gianelloni
2006-09-22 14:47 ` Peter
2006-09-22 15:08 ` Andrew Gaffney
2006-09-22 18:37 ` Alec Warner
2006-09-22 18:54 ` Chris Gianelloni
2006-09-22 13:56 ` Josh Saddler
2006-09-22 13:39 ` Grant Goodyear
2006-09-22 14:06 ` [gentoo-dev] Re: seeds, GLEPs, and projects Mike Kelly
2006-09-22 14:14 ` Peter
2006-09-25 2:25 ` Christel Dahlskjaer
2006-09-21 21:24 ` [gentoo-dev] " Lance Albertson
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='ef0hpk$aqj$2@sea.gmane.org' \
--to=sw98234@hotmail.com \
--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