I agree the cleanup is always useful, though it would be definitely nice to document explicit criteria in https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#roles . Not sure I even count as an active maintainer on my own these days, though my "sabbatical" was publicly announced
For transparency reasons, the following maintainers were removed according to the audit log: - Michael Neale - Ryan Campbell - Andrew Bayer - Stephen Connolly - Matt Sicker - Steven Christou - Keith Zantow - Sam van Oort - Evaristo Gutiérrez - Ramon Leon All the mentioned contributors are ex CloudBees employees who have already moved on, company wise or project wise. Some of them are still active in the Jenkins community, but I do not see any activities around Jenkins core in the recent 2 years. I would not be too concerned about the removal, especially since the permissions can be easily restored upon return to Jenkins core contributions. Best regards, Oleg On Sunday, January 29, 2023 at 2:23:21 PM UTC+1 timja...@gmail.com wrote: > While I’m very much +1 for the change I think it should’ve been discussed > on the mailing list publicly > > On Sun, 29 Jan 2023 at 13:52, 'wfoll...@cloudbees.com' via Jenkins > Developers <jenkin...@googlegroups.com> wrote: > >> Thanks for the positive feedback! >> >> > we decided >> Decision was made between Damien and me. >> It was discussed with a few other people and as we got mainly just ultra >> positive response, widen the discussion before the act did not seem >> necessary. Especially when such a change can be reversed without problems. >> >> Concerning the activities, the remaining people did at least a PR review >> during the last year. This is not strictly requiring the write permission, >> but I don't want to do something that could be seen as a witch hunt. >> This kind of risk reduction was rarely done in the past, I don't want to >> be too aggressive on that. Starting small and increasing the scope over >> time. CERT membership and VPN/infra access will follow soon. >> >> Wadeck >> >> On Saturday, January 28, 2023 at 9:59:24 AM UTC+1 mc.ca...@gmail.com >> wrote: >> >>> Thanks for your ongoing efforts to make our repositories secure! >>> >>> > Was this decision made in concert with other core maintainers >>> >>> I was not aware of such a change, but I heavily endorse the cleanup :) >>> >>> Alex >>> >>> On Friday, 27 January 2023 at 16:59:41 UTC+1 m...@basilcrow.com wrote: >>> >>>> On Fri, Jan 27, 2023 at 1:06 AM 'wfoll...@cloudbees.com' via Jenkins >>>> Developers <jenkin...@googlegroups.com> wrote: >>>> > >>>> > For that reason we have decided to remove inactive contributors from >>>> the ‘core’ team. >>>> >>>> Thanks! Strongly agree that this is a great move. >>>> >>>> > we decided >>>> >>>> Was this decision made in concert with other core maintainers or >>>> unilaterally? >>>> >>>> > one year without any activity in the affected repositories qualifies >>>> as inactive >>>> >>>> Is this one year without any _general_ activity (e.g., opening a PR) >>>> or one year without any _maintainer_ activity (e.g., merging or >>>> closing a PR)? Write permissions are needed for the latter but not the >>>> former. Given the stated goal to reduce the number of people with >>>> unnecessary write access, the latter definition makes more sense to >>>> me. >>>> >>>> Basil >>>> >>> -- >> 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-de...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/007096da-aac2-4444-93ec-44466cb3527an%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/007096da-aac2-4444-93ec-44466cb3527an%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/f2790b42-5cf6-4902-86d3-c8a21c9612fbn%40googlegroups.com.
