> On 31. Aug 2018, at 17:16, Daniel Beck <[email protected]> wrote:
>
> … as previous maintainers could just add the new maintainer as an 'external
> contributor' to the GitHub repo, if they have repo admin access -- which is
> the default.
>
> So the only thing they cannot accomplish on their own _somehow_, without a
> project infra contributor getting involved, is updating upload permissions.
So to clarify, most of my concerns are how the revised 'Adopt a plugin' process
would interact with the established maintainership definition and transfer
process.
In the proposal as it is today, the latter isn't being considered at all, and
that's what the majority of my concerns are about.
For example, maintainership transfers can happen without marking a plugin for
adoption, or creating Jira issues, etc. -- so Jira can never be a complete
reference. We have one reference that will be up to date unless we stopped a
transfer halfway through, and that is the upload permissions.
--
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/74132BB7-FE85-4B01-A4A4-3D417D69BD39%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
