Plugin Maintainer alumni metadata

[Oleg Nenashev]

Hi all,

Just to follow-up on https://groups.google.com/g/jenkinsci-dev/c/e3T6QG24YVg , I propose adding a new "Alumni" category to https://github.com/jenkins-infra/repository-permissions-updater to reference ex maintainers of the plugins.

Such a category could serve two purposes:

• Giving credit on plugins.jenkins.io while not keeping permissions for older maintainers
• Simplifying the return process if an old maintainer re-applies for plugin ownership

What do you think?

Best regards,

Oleg

[Daniel Beck]

Seems like unnecessary clutter.

The former can be accomplished much more nicely by integrating with GitHub's contributor information.

The latter is just noise, if you've been a maintainer before and actually did something, it'll be easy enough to show that.

This only makes sense if the idea is that there are two classes of former maintainers, those that are eligible to be credited and return, and those that are not?

[Oleg Nenashev]

GitHub contributor metadata does not list former maintainers specifically, unless you want to query audit log

Listing all contributors is possible through that and it would be cool indeed, but it is not a specific use-case for maintainer alumni

[Tim Jacomb]

I don't see the need for this, if someone wants to come back to active they can just ask, the git history is there in RPU, commit history etc

--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/775d379a-bc88-4cbc-997c-e5bfd5ab526fn%40googlegroups.com.

[tzach....@gmail.com]

I'm with Oleg on this one. 

Just for the sake that someone contributed from his/her time and knowledge and it would be nice to still give credit.

[Daniel Beck]

> On 17. Oct 2021, at 10:52, Oleg Nenashev <o.v.ne...@gmail.com> wrote:
>
> GitHub contributor metadata does not list former maintainers specifically, unless you want to query audit log
> Listing all contributors is possible through that and it would be cool indeed, but it is not a specific use-case for maintainer alumni

Agree, but what specifically motivates your chosen solution that excludes non-maintainer contributors? I'd rather feature consistent, long-term contributors than some dude who merged a PR (possibly by someone else) and pushed one release, once.

If former maintainers don't make it onto the contributor graph, then maybe they didn't do enough maintaining. (Obviously there are non-code contributions, but that isn't properly acknowledged either way.)