public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-project] [RFC] Undertakers: toggling commit access for inactive devs, and prolonging retirement timeframe
@ 2019-09-25 13:27 Michał Górny
  0 siblings, 0 replies; only message in thread
From: Michał Górny @ 2019-09-25 13:27 UTC (permalink / raw
  To: gentoo-project; +Cc: undertakers

[-- Attachment #1: Type: text/plain, Size: 2365 bytes --]

Hi,

TL;DR: if developers don't reply in 2 weeks from first mail, their
commit access is temporarily disabled.  It is reenabled immediately
on request from the (returning) developer.  All other points in
retirement timeframe are shifted forward to provide twice as much time
as currently.


Currently, the retirement timeframe roughly includes:

1. Sending first mail after 2+ months of inactivity (usually 4+),

2. For developers with commit access, if developer *does not reply*:

2a. Reassigning packages in 2+ weeks.

3. For everyone, while the developer *is still inactive*:

3a. Sending second mail 4 months after the first mail.

3b. Sending third mail 1 month later.

3c. Retiring 1 month later.

Those times are just minimal requirements, we wait longer
if the developer is away, has problems, etc.  However, they kinda suck
for people truly MIA, since it implies that it takes 8-10 months before
unused commit access is disabled.  They also suck for people who need
more away time and don't want to lose developer status.


Following earlier discussion and comments, I'd like to propose to change
the timeline to:

1. Sending first mail after 2+ months of inactivity (usually 4+),

2. For developers with commit access, if developer *does not reply*:

2a. Disabling commit access in 2 weeks.

2b. Reassigning packages in 4+ weeks.

3. For everyone, while the developer *is still inactive*:

3a. Sending second mail 6 months after the first mail.

3b. Sending third mail 3 months later.

3c. Sending fourth mail 2 months later.

3d. Retiring 1 month later.


The main changes are:

a. Commit access is disabled 2 weeks after first mail if developer does
not reply (and does not commit).  It can be quickly reenabled on
developer's return.

b. The retirement process takes 12 months instead of 6 months since
first-mail.

c. Additional mail is added to the process to reduce the risk that
developer misses some, and times are increased from 4,1,1 to 6,3,2,1. 
This gives developer more time, and improves pinging process.


Note that in the original discussion, making the commit access switch
automated was discussed.  However, no progress has been made on this,
so I'm sending the original proposal that requires no technical changes.

WDYT?

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-09-25 13:27 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-09-25 13:27 [gentoo-project] [RFC] Undertakers: toggling commit access for inactive devs, and prolonging retirement timeframe Michał Górny

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox