On Fri, Aug 24, 2018 at 11:27 AM Oleg Nenashev <[email protected]> wrote:
> I would be especially interested to allow requesting ownership via pull 
> requests …

Embryonic thought: maybe we could consider
`repository-permissions-updater` to be the source of truth? After all,
this is what ultimately controls whether or not a given person is
physically capable of producing a release of a given plugin. For
example, I am the maintainer of `build-token-root` by dint of this
line:

https://github.com/jenkins-infra/repository-permissions-updater/blob/f412da4896b12b4f4a39063f2c991d1e5b34841b/permissions/plugin-build-token-root.yml#L7

If someone wanted to be added as a co-maintainer, or take over from
me, at some point a PR would need to be filed amending this file
section anyway and CCing @jglick. So why not treat that as the formal
request for ownership of the plugin? Interested parties could approve
or deny the PR with comments, and if and when merged the transfer
takes effect. (I still maintain that a separate heads-up to the dev
list is in order.)

An org admin also needs to update the GitHub permissions via e.g.

https://github.com/orgs/jenkinsci/teams/build-token-root-plugin-developers/members

but that could just be a (manual or scripted) consequence of the
`plugin-*.yml` patch.

We would also want to deprecate the `<developers>` POM field, which is
very inconsistently maintained anyway, and is bound to a particular
(latest) release of the plugin which is not helpful when you are in
between releases and negotiating handover. Means the `update-center2`
generator would need to consider RPU rather than this.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0%3Dmjsx%3DBRj1VxoDAQT2fM4bEjuvqYRMGUJVgS6gDUo4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to