public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Doty <kingtaco@gentoo.org>
To: Donnie Berkholz <dberkholz@gentoo.org>
Cc: Markus Ullmann <jokey@gentoo.org>,  gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Retirement of slacking peeps
Date: Wed, 16 Jan 2008 03:06:52 -0800	[thread overview]
Message-ID: <478DE54C.1080506@gentoo.org> (raw)
In-Reply-To: <478DE307.1010906@gentoo.org>

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

Mike Doty wrote:
> Donnie Berkholz wrote:
>> On 12:15 Tue 15 Jan     , Markus Ullmann wrote:
>>> Hi guys,
>>>
>>> our retirement folks brought up a discussion about retiring people that
>>> do a small amount of commits (1-2 mostly) right before the 60 day period 
>>> ends so they stay active yet are effectively slacking.
>>>
>>> I gave a starting idea to change the minimum amount to something like 
>>> $count of fixed bugs per month for ebuild developers. As we have enough 
>>> bugs that are trivial to fix this shouldn't be a real problem at the moment 
>>> (considering we have ~6.5k bugs open excluding maintainer-wanted).
>> I don't see a good reason to turn away any amount of help, and I don't 
>> think we should ever forcibly retire developers because of inactivity. 
>> If we let them stay developers, they might continue contributing a few 
>> fixes we wouldn't otherwise get, or they may become more active again in 
>> the future. Developers are valuable people, and a lot of time has gone 
>> into their training and experience.
> 
>> Do I think we should reassign their packages after a while, if they need 
>> love? Sure.
> 
>> Do I think we should remove them from roles besides "ebuild developer"? 
>> Sure.
> 
>> Thanks,
>> Donnie
> How about calling them inactive.  infra will remove cvs/svn/git access
> and when they have time to contribute to a manner that we expect that
> access can be restored.
> 
> Know that infra is/has been planning to automatically disable
> cvs/svn/git access for those who haven't committed in some time period
> (2 months is the current idea)
> 
> 
s/we expect/some standard/ and the re-enabling can be made very easy, it
really depends on what standards you set for someone to be an "active"
developer.

- --
=======================================================
Mike Doty                      kingtaco -at- gentoo.org
Gentoo Infrastructure
Gentoo/AMD64 Strategic Lead
GPG: E1A5 1C9C 93FE F430 C1D6  F2AF 806B A2E4 19F4 AE05
=======================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iQCVAwUBR43lS4BrouQZ9K4FAQJrdgP+MBxGEkyOVeFNF9HnfWCIx97HCGwxKkYq
4gPBsTYa278J6i0byrtVuaWhdQwKv4tKX481ydwXmyXGGJmWbhaREjnfdomkS3Bf
/NQVc9Q6jsq5syLwqaveQDcC02L2rQxCC8SxK2Tvb4c4P47YE+RbqkisJIHyXgxb
ZnZV6EEadiA=
=xy/t
-----END PGP SIGNATURE-----
-- 
gentoo-council@lists.gentoo.org mailing list



  reply	other threads:[~2008-01-16 11:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 11:15 [gentoo-council] Retirement of slacking peeps Markus Ullmann
2008-01-15 11:36 ` Mike Frysinger
2008-01-15 11:41   ` Mike Frysinger
2008-01-16  8:15 ` Donnie Berkholz
2008-01-16 10:57   ` Mike Doty
2008-01-16 11:06     ` Mike Doty [this message]
2008-01-16 11:43     ` Mike Frysinger
2008-01-16 20:40       ` Ned Ludd

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=478DE54C.1080506@gentoo.org \
    --to=kingtaco@gentoo.org \
    --cc=dberkholz@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=jokey@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