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 <timjaco...@gmail.com> wrote:
>
> +1 we have this in jenkins-infra
>
> On Thu, 23 Sep 2021 at 10:28, Baptiste Mathus <m...@batmat.net> 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, wfoll...@cloudbees.com 
>> <wfollon...@cloudbees.com> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACmp6kpV8vE-8C%3D7mAE3DgcAA3O84Fgyqg0CpXUPCq5-CrZxpw%40mail.gmail.com.

Reply via email to