Proposal: Update CloudBees maintained plugins with CloudBees team

[Carroll Chiou]

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

[Oleg Nenashev]

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

[Oleg Nenashev]

FWIW I explicitly -1 adding such undetermined group top any plugin where I am listed as co-maintainer.

Happy to discuss on a case by case basis, because I'd step down for some of the plugins