On Mon, Jan 30, 2023 at 12:27 PM Daniel Beck <db...@cloudbees.com> wrote:
> I also see this less as a step to remove maintainers who are not doing any > maintenance (which goes beyond what the officers' mission is) and more > limiting risk (which is in scope). IMO if one of the affected folks were to > show up tomorrow and resume activity in core reviews etc., I would be happy > with a quick restoration of access, different from how it'd work for a > newcomer. > We could even use a separate team to represent this, like jenkinsci/inactive-core-maintainers, which would include folks whose permissions were removed due to inactivity, but who are welcome back if they want (while we don't have a real process to remove maintainer status). (While the jenkinsci/alumni team exists, its description indicates willingness to review things, which is probably not a given here.) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2B64pJVghW33XhzE2tnjHmOxZLsbyC-gjSJ2f6ETkLT_Q%40mail.gmail.com.
