From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] The mis-concept of "slacking" in Gentoo
Date: Wed, 30 Jun 2010 02:12:47 +0200 [thread overview]
Message-ID: <4C2A8BFF.5040400@gentoo.org> (raw)
In-Reply-To: <4C1975F7.5010903@gentoo.org>
Jorge,
On 06/17/10 03:10, Jorge Manuel B. S. Vicetto wrote:
> So everyone can have an idea, I'd suggest looking at the list of the
> open retirement bugs[1].
> As there seems to be some confusion about the policies to retire
> developers, please read the undertakers page[2].
Interesting links, thanks.
Two things come to my mind: Step 2 of the undertakers page reads:
"When sending an email to the developer in question, make sure you
tell him, that he might get retired due to being inactive."
If I'm not mistaken this is telling the developer about potential
retirement on first direct contact. If that's true I don't consider it
very sensitive. After all our goal is to keep that developer in, not
out. So my proposal is: please add another two weeks and a second mail
so the first one does not mention retirement. How about that?
The other thing is: what are the reasons to retire inactive developers?
Are these reasons documented somewhere?
Thanks!
Sebastian
next prev parent reply other threads:[~2010-06-30 0:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C184B06.8040806@gentoo.org>
2010-06-16 4:48 ` [gentoo-project] Re: [gentoo-dev] The mis-concept of "slacking" in Gentoo Alec Warner
2010-06-30 0:01 ` Sebastian Pipping
2010-07-01 9:50 ` Nirbheek Chauhan
2010-06-16 16:46 ` "Paweł Hajdan, Jr."
2010-06-16 17:28 ` Steve Dibb
2010-06-17 1:10 ` Jorge Manuel B. S. Vicetto
2010-06-30 0:12 ` Sebastian Pipping [this message]
2010-06-30 3:05 ` Jorge Manuel B. S. Vicetto
2010-07-02 13:51 ` Sebastian Pipping
2010-07-03 0:26 ` Jorge Manuel B. S. Vicetto
2010-07-03 12:32 ` Sebastian Pipping
2010-06-30 0:20 ` Sebastian Pipping
2010-06-30 9:38 ` Roy Bamford
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=4C2A8BFF.5040400@gentoo.org \
--to=sping@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