Date: Tue, 03 Sep 2019 14:06:28 -0000 From: Joseph Mingrone <jrm@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: "Rodney W. Grimes" <rgrimes@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-svnadmin@freebsd.org Subject: Re: svn commit: r345786 - svnadmin/conf Message-ID: <86imvvoqlz.fsf@phe.ftfl.ca> In-Reply-To: <CANCZdfryBpuYQHPoK2vBKOr1AFLk_ZJAsa9DX2EUoFJWvLu9hA@mail.gmail.com> (Warner Losh's message of "Mon, 1 Apr 2019 22:38:37 -0600") References: <CANCZdfpLs-7%2BDwhopKPp-14rC6owPwBq8_smDxUzRnup7R%2BaRw@mail.gmail.com> <201904020345.x323jKM2018935@gndrsh.dnsmgr.net> <CANCZdfryBpuYQHPoK2vBKOr1AFLk_ZJAsa9DX2EUoFJWvLu9hA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Here is an updated checklist based on the feedback.
- 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, follow these steps.
1. Check whether the bit is associated with a vendor committer. Is so,
consider further investigation to determine the cause of the inactivity.
Has something changed with this vendor?
2. Check the mentors file to determine whether this developer is either a
mentor or a mentee. If the developer is a mentee, remove the developer
from the mentors file. If the developer is a mentor, create a core@ item
to find the mentee a new mentor, inform the mentee that this item has
been created, and ask the mentee for input on who might be a suitable
replacement as a new mentor. Assign core@ as the temporary mentor.
3. Check whether the developer is a member of any groups. If so, inform
those groups that the developer's commit be is being taken in, and ask
that the developer be removed from the group.
4. If the developer wishes to continue receiving developer@ mail,
ask postmaster@ to add the developer to alumni group.
5. Remove the developer from the access file.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEEVbCTpybDiFVxIrrVNqQMg7DW754FAlykBEhfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1
QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUACgkQNqQMg7DW
756QDQ/+MNdLNbNpFs2hW7sWUg/iF9wR5HfxoR/teWew7dzufKVAzeKdXyEnT3yC
dmxfCjoT8AHZpWOD+K0BMhCCVmlGEDu2zTFZojWy6xJwExec2KcFxE9fWDJc+/jK
Gv5055syJfBHAgkdrsf6hFxXTzxp/mD7uPW0rfNwahaT1cyBK65EyRTPdOlCfYkq
BHEcirnBhFVuMKaDSYJcRjIIDLZbuFy0zAkI6JxuJ3BXD4B6IZjmijEhMJAUx/Uf
MnORtHV2ubqaTdRMDvC26TSkdxYMtXODoRlrkaxTuNV97GmoUnOaTBbq32xUtyE4
NsnrpwBZB9tvX9utt7tNFoO2bZnIfvQNeXc8CGRAfFZQEQjlWUEE8norS+MFOD6U
XzbU4BxW/LashKoTP+lJkatUJd8X1d3i8ce2liUj5NBKnYE0mxvpv8A4X/UNsQpm
+eZ8hydQgiat953qcksW4I7KlUAcE6Q0fnxTHw0Whw+J7doTC+y2iFnwhQWycgSt
krD6hx7tGTieTQPKBclXdEa424x+b0BDI4AOGxz0jBRKP3K6vePJWkXGy5mtxX5I
AAiQRoEC15ogq9iv1BUcMe+CAvXaiRw3bUyIJa3dT9mqjsyIWM78mwYwnuJTnV7g
tXLsj3zJ5c4747b+lQ03gV2z581OlOPwnyjnOdKutsDPlQTUzVo=
=GEl/
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86imvvoqlz.fsf>