Warner Losh <i...@bsdimp.com> writes:

> On Mon, Apr 1, 2019 at 7:15 PM Rodney W. Grimes <free...@gndrsh.dnsmgr.net>
> wrote:

>> > Author: jrm (ports committer)
>> > Date: Mon Apr  1 21:34:58 2019
>> > New Revision: 345786
>> > URL: https://svnweb.freebsd.org/changeset/base/345786

>> > Log:
>> >   Set jhb@ as new mentor to anish@

>> >   Approved by:        core (brooks, seanc)
>> >   Differential Revision:      https://reviews.freebsd.org/D19782

>> Can we please have a check list that when someones
>> commit bit is reaped, or steps away from the project
>> for more than N days, N being something rather small
>> given the context here, that includes the item:

>>         x)  Is this person a mentor of anyone?


> Great idea...  Joseph will put one together based on this round of
> retirement...

<snip>

This is the current checklist:

- Check for idle developers using: idle-commit-bits.pl base 18

- Source bits are taken in for safekeeping after three consecutive emails about
  reaping go unanswered, or if the developer in question confirms that the bit
  can be taken in.  The email-to-idlers.pl script can be used to send warning
  emails, but René is currently taking care of this job.
  
- Once it has been established that a bit is to be taken in, first check the
  mentors file to see if this developer is a mentor.  If so, a new mentor must
  be found before the bit is taken in.
  
- If the developer whose bit to be removed is a mentee, remove the developer
  from the mentors file.
  
- Remove the developer from the access file.

--
Joseph

Attachment: signature.asc
Description: PGP signature

Reply via email to