I like this idea so a +1 from me.

> On Mar 2, 2020, at 3:02 AM, Stephen Connolly 
> <[email protected]> wrote:
> 
> 
> Can we add a concept of emeritus maintainer... by just commenting out their 
> username in the corresponding repository-permissions-updater yaml file?
> 
> An emeritus maintainer would be indicating that they are no longer active, 
> but if they want to re-activate they do not need to wait for existing 
> maintainers to approve... or in the case of unmaintained plugins they do not 
> need to wait for the claim-ownership period.
> 
> If all maintainers of a plugin are emeritus and someone wants to claim 
> ownership then the emeritus maintainers can short-circuit the transfer of 
> ownership rather than having to wait out the full period.
> 
> My use case is that I currently wish to be marked emeritus for all plugins 
> that I am a maintainer of *except*:
> 
> - gitea (until I get the gitea token auth implemented, then I'll be looking 
> for someone to adopt it)
> - impersonation (until I decide whether to release it or kill it)
> - mock-load-builder (needed for work commitments)
> - random-job-builder (needed for work commitments)
> - metrics (needed for work commitments)
> 
> I may need to step back on the other plugins at shorter notice, so it would 
> be annoying to have to go though recovering maintainer status... which is why 
> I have not dropped those permissions.
> 
> I do think we need to be able to reflect better the case where maintainers 
> are not actively maintaining but do not want to drop permissions because it 
> could trigger the plugin as completely unmaintained and thus a lot harder to 
> reclaim... yet by not dropping permissions it leaves others who might be 
> interested in adopting the impression that the plugin is actively maintained
> -- 
> 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/CA%2BnPnMw0XFtd1PR00yuhJJ-q8B0s6LqHK%3DResjH8P%3Di%3DJ%2B-MTw%40mail.gmail.com.

-- 
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/6E994ABD-F3E1-4FF6-9E8F-A27C7F9B04D2%40gmail.com.

Reply via email to