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: Sat, 03 Jul 2010 14:32:47 +0200 [thread overview]
Message-ID: <4C2F2DEF.6090609@gentoo.org> (raw)
In-Reply-To: <4C2E83CC.3010905@gentoo.org>
Jorge,
On 07/03/10 02:26, Jorge Manuel B. S. Vicetto wrote:
>> I wonder if we could start making a stronger distinction between these
>> two cases of retirement. If it isn't a throw-out I would prefer to have
>> that made so very clear that no one ever feels thrown out that way.
>> Especially that there's no guarantee to be allowed to return feels a bit
>> odd to me.
>
> please read the undertakers page and the resolution of the retirement
> bugs carefully as you seem to be confused about our policy to retired
> developers.
Confused about what exactly?
> The only case where re-admittance is subject to particular
> scrutiny is when a developer is retired for disciplinary reasons. As you
> can read in the second email template[1], we specifically inform the
> developer that:
>
> "If we do retire you, it's pretty easy to come back when you are ready.
> Just do the ebuild/end-quiz again and you're back on. You also always
> have the option of contributing as your schedule allows via proxy or
> bugzilla."
>
> We also make sure to mention in the retirement bugs that a developer can
> always return as seen on an example bug[2]. My apologies to Caleb to
> link directly to his bug, but I needed one concrete reply to show
> undertakers work.
Agreed, it could be worse. I would personally not trust on "you can
come back any time" though and looking forward to another round of
ebuild quizzes doesn't sound inviting to me either (not saying that
developers don't need to be up to date with Gentoo). I'm not sure if
I'm really the most or only sensitive person in Gentoo if that's coming
to your mind now.
Let me quote an excerpt by another developer. When I stumbled upon his
inactivity-based retirement bug I was asking if he really means to
retire. He said:
"If Gentoo likes to retire me, fine. I won't stop them.
I don't think, this will will help Gentoo get back on
track, though, if there is a way back at all."
So I don't seem to be the only one having a bad impression of our
current concepts of retirement. Do you read it differently?
Before I propose anything: What ways do you see to improve our concept
and realization of retirement?
Best,
Sebastian
next prev parent reply other threads:[~2010-07-03 12:33 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
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 [this message]
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=4C2F2DEF.6090609@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