Gentoo Archives: gentoo-council

From: Mike Doty <kingtaco@g.o>
To: Donnie Berkholz <dberkholz@g.o>
Cc: Markus Ullmann <jokey@g.o>, gentoo-council@l.g.o
Subject: Re: [gentoo-council] Retirement of slacking peeps
Date: Wed, 16 Jan 2008 11:06:58
Message-Id: 478DE54C.1080506@gentoo.org
In Reply to: Re: [gentoo-council] Retirement of slacking peeps by Mike Doty
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Mike Doty wrote:
5 > Donnie Berkholz wrote:
6 >> On 12:15 Tue 15 Jan , Markus Ullmann wrote:
7 >>> Hi guys,
8 >>>
9 >>> our retirement folks brought up a discussion about retiring people that
10 >>> do a small amount of commits (1-2 mostly) right before the 60 day period
11 >>> ends so they stay active yet are effectively slacking.
12 >>>
13 >>> I gave a starting idea to change the minimum amount to something like
14 >>> $count of fixed bugs per month for ebuild developers. As we have enough
15 >>> bugs that are trivial to fix this shouldn't be a real problem at the moment
16 >>> (considering we have ~6.5k bugs open excluding maintainer-wanted).
17 >> I don't see a good reason to turn away any amount of help, and I don't
18 >> think we should ever forcibly retire developers because of inactivity.
19 >> If we let them stay developers, they might continue contributing a few
20 >> fixes we wouldn't otherwise get, or they may become more active again in
21 >> the future. Developers are valuable people, and a lot of time has gone
22 >> into their training and experience.
23 >
24 >> Do I think we should reassign their packages after a while, if they need
25 >> love? Sure.
26 >
27 >> Do I think we should remove them from roles besides "ebuild developer"?
28 >> Sure.
29 >
30 >> Thanks,
31 >> Donnie
32 > How about calling them inactive. infra will remove cvs/svn/git access
33 > and when they have time to contribute to a manner that we expect that
34 > access can be restored.
35 >
36 > Know that infra is/has been planning to automatically disable
37 > cvs/svn/git access for those who haven't committed in some time period
38 > (2 months is the current idea)
39 >
40 >
41 s/we expect/some standard/ and the re-enabling can be made very easy, it
42 really depends on what standards you set for someone to be an "active"
43 developer.
44
45 - --
46 =======================================================
47 Mike Doty kingtaco -at- gentoo.org
48 Gentoo Infrastructure
49 Gentoo/AMD64 Strategic Lead
50 GPG: E1A5 1C9C 93FE F430 C1D6 F2AF 806B A2E4 19F4 AE05
51 =======================================================
52 -----BEGIN PGP SIGNATURE-----
53 Version: GnuPG v2.0.7 (GNU/Linux)
54
55 iQCVAwUBR43lS4BrouQZ9K4FAQJrdgP+MBxGEkyOVeFNF9HnfWCIx97HCGwxKkYq
56 4gPBsTYa278J6i0byrtVuaWhdQwKv4tKX481ydwXmyXGGJmWbhaREjnfdomkS3Bf
57 /NQVc9Q6jsq5syLwqaveQDcC02L2rQxCC8SxK2Tvb4c4P47YE+RbqkisJIHyXgxb
58 ZnZV6EEadiA=
59 =xy/t
60 -----END PGP SIGNATURE-----
61 --
62 gentoo-council@l.g.o mailing list