I requested changes in both pull requests. This approach does not seem to be correct for any plugin having at least one non-CloudBees contributor. I doubt such contributors would expect an arbitrary CloudBees employee to be able to cut the releases. Pretty much the same applies to other plugins. Even if all maintainers are employed by CloudBees, it does not mean that it is maintained during the working time.
I suggest closing these bulk PRs and opening new ones only for those plugins where a consensus with all maintainers is reached On Wednesday, December 22, 2021 at 4:36:28 AM UTC+1 Carroll Chiou wrote: > Hello all, > > In an effort to better manage plugins that are being maintained by > CloudBees employees, we would like to add the “cloudbees-developers” team > to the appropriate repository permission files and update the corresponding > GitHub repos. You can review the proposed plugins here: > > https://github.com/jenkins-infra/repository-permissions-updater/pull/2265 > https://github.com/jenkins-infra/repository-permissions-updater/pull/2266 > > Thanks, > Carroll Chiou -- 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/1d0e5f63-8607-4cc6-b312-afc9d3a4a747n%40googlegroups.com.
