I'm not that much concerned that we wouldn't do exactly what Apache does
TBH. More of an inspiration.

IOW, we could just create a special team with no permission of "emeritus"
members. People in jenkins/core that we know have not been active since 1+
year anywhere.
And when in doubt, we'd double check with these persons, and if they don't
answer we'd move them to this emeritus list.


Baptiste


Le jeu. 23 sept. 2021 à 20:30, Matt Sicker <[email protected]> a écrit :

> At Apache, emeritus status is typically requested by the individual.
> That might be hard to emulate here if some otherwise emeritus members
> of Jenkins aren't here to request emeritus. Some forms of active
> versus inactive members could be useful, though, for code review
> purposes and other bookkeeping.
>
> On Thu, Sep 23, 2021 at 5:08 AM Tim Jacomb <[email protected]> wrote:
> >
> > +1 we have this in jenkins-infra
> >
> > On Thu, 23 Sep 2021 at 10:28, Baptiste Mathus <[email protected]> wrote:
> >>
> >> Hi all,
> >>
> >> Following up on Jesse's comment, and as I was reflecting on this a few
> days ago: I think we should introduce an Emeritus concept/status for
> Jenkins core team's inactive members.
> >>
> >> That would allow "cleaning up" the list for various reasons, while
> still recognizing the contributions of such individuals.
> >>
> >> I think, akin to Apache does in many projects, we should also have a
> straightforward way for such members to be reinstated inthe core list when
> they would request it.
> >>
> >> WDYT?
> >>
> >> Once we agree on this principle, we will also need to dicuss the
> "inactive member" definition, but that's a secondary concern for now IMO.
> >>
> >> Baptiste
> >>
> >> Le mer. 22 sept. 2021 à 14:10, [email protected] <
> [email protected]> a écrit :
> >>>
> >>> +1 as well, really involved in the community so it's just natural :-)
> >>>
> >>> On Wednesday, September 22, 2021 at 2:05:32 PM UTC+2 Jesse Glick wrote:
> >>>>
> >>>> If he is interested, absolutely +1!
> >>>>
> >>>> By the way there are a number of people in
> https://github.com/orgs/jenkinsci/teams/core/members who are no longer
> active in the Jenkins community and who should likely be removed.
> >>>
> >>> --
> >>> 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/2735a776-6bdf-485c-bdb0-96d45175ab67n%40googlegroups.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/CANWgJS5RcWPCSPghkpyBL3TH8iwv96ogjSbunVBbAdQ0rsTh6A%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/CAH-3Bie4XJNJ_WNDmH%3DJsuid4g5w9X%3D%2B8%3DTn3odWs0gZoZLHhQ%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/CACmp6kpV8vE-8C%3D7mAE3DgcAA3O84Fgyqg0CpXUPCq5-CrZxpw%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/CANWgJS6ReuCQTxfcw52pEYL8PK-mB8rXdREAe5uywrwT%2B6HCCA%40mail.gmail.com.

Reply via email to