public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@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 00:26:52 +0000	[thread overview]
Message-ID: <4C2E83CC.3010905@gentoo.org> (raw)
In-Reply-To: <4C2DEEDB.8020100@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sebastian,

On 02-07-2010 13:51, Sebastian Pipping wrote:
> Jorge,
> 
> 
> On 06/30/10 05:05, Jorge Manuel B. S. Vicetto wrote:
>> The following is a list with a few reasons to retire inactive developers:
>>
>>  * security considerations regarding access to Gentoo infra, including
>> tampering of the tree
>>  * need to ensure that maintainers are accessible, take care of
>> packages and bugs and that they reply on due time to community
>> contacts and requests
>>  * desire to have project and team membership, as well as package
>> maintenance reflect reality
>>  * make it clear what areas of the project are understaffed and what
>> packages require new maintainers
>>  * need to ensure that developers keep up to date regarding policies
>> and use of the tree by using it
> 
> interesting, thanks for elaborating.
> 
> 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. 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.


[1] - http://www.gentoo.org/proj/en/devrel/undertakers/retirement-second.txt
[2] - https://bugs.gentoo.org/show_bug.cgi?id=317071#c1

> Best,
> 
> 
> Sebastian
> 

- -- 
Regards,

Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJMLoPKAAoJEC8ZTXQF1qEP9nMP/28b1mR+kZe1zJZb7nzeTHLg
bqfdCgiTQd0uqNWWX2scgPQRE1hsv9RtJp3y8CCvvu3aYhVi4hBDXCPm/2NTiFqf
T5dWKtH9nPi5+27CXUsEwQFlV0miTp1o8I2tSOq7IuadIjbib92Yq60Z3xnqA1fX
bf+shP3lBGpR8ReDEzE9gEIWHG91/9a95iZA21dsxNoO7ev8rFS9ixKZ1I83ZEp8
xA+H2RTaNHXbwD7P3fi6Vn+xBckNnIEHWQeQGEpdi+EzYYzFyMdCiaOnOPiZFj/N
n0hEOqqmrLEVGXNrPNB12kM/v35G+yX01qM4AFzpDwNWehxOX8ZxI1u/5frJ3J5M
RNDMBy9W7FGEd0MMqYS/ndQftxpn5OOj+Y1BUXjVJcUv0+K6JGOuO+AApcrJyBX7
MuQrEMKmGZ0ZvL+AKxyAAkS4xztcLqDzvq7xAXS7S9YQ2EVKwXnYazcaa4WAyOyd
UyFdUOHUKSXy41wwWzOrXds7tZgmcgatT8+eP+BvIAvIJZti05YVRmDd4pFhOl9u
YehAx3rzuBHnyWO32Ycmr5GbBjKD0YqA5eZl9cwoBBPGazioYZXWIxMGXlNBK94o
ZF7n5JAt49EzogXXA5769t7xU0g89WpWDc+nESjl9zq51yvQXpwrQuGDh6CDsij/
xd/jnWuAa0YMxkXu4hWQ
=E13T
-----END PGP SIGNATURE-----



  reply	other threads:[~2010-07-03  0:27 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 [this message]
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=4C2E83CC.3010905@gentoo.org \
    --to=jmbsvicetto@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