I'm supportive of this new policy and I think we should have a similar
approach for the PMC.

Just to add some colors to the discussion, as of today we have 30
committers that are not part of the PMC. If we were to apply this
policy with the specified threshold and qualifying activities, I
_think_ this would concern:

- Andy I.C.
- Ádám Markovics
- Dániel Bakai
- Ben Qiu
- Bryan Rosander
- Denes Arvay
- Ed Berezitsky
- Kotaro Terada
- Mike Hogue
- Margot Tien
- Ricky Saltzer
- Toivo Adams
- Sivaprasanna Sethuraman

Thanks,
Pierre

Le mar. 5 août 2025 à 03:34, David Handermann
<exceptionfact...@apache.org> a écrit :
>
> Team,
>
> After some positive feedback among the Project Management Committee, I
> propose the following policy for additional discussion on the subject
> of inactive committer status.
>
> This policy would apply to committers, not to PMC members. Discussing
> inactive PMC membership is also worthwhile, but should be considered
> separately.
>
> ---
>
> 1. Committers become inactive after a period of 1 year without any
> qualifying activity
>
> 2. Qualifying activities consist of the following publicly observable
> contributions:
>   A. Submitting a pull request to any project repository
>   B. Reviewing a pull request in any project repository
>   C. Submitting an issue to a project issue tracking system
>   D. Commenting on an issue in a project issue tracking system
>   E. Sending a message to any public project mailing list
>
> 3. An authorized PMC member revokes access for an inactive committer
> and sends a message to the developer mailing list announcing inactive
> status with links indicating lack of activity
>
> 4. Within 1 year of becoming inactive, committers may email the PMC,
> requesting return to active status, and an authorized PMC member will
> restore access as requested
>
> 5. Committers become emeritus after a period of 1 year following
> inactive status, which is 2 years without any qualifying activity
>
> 6. Committers with emeritus status require renomination and PMC vote to
> return to active status
>
> ---
>
> The purpose of this policy is to provide clear boundaries of time and
> qualifying activities required to retain committer access to project
> repositories. The move from inactive to emeritus status is a means to
> recognize both the value of contributions and the reality of changes
> in availability.
>
> Based on feedback and subject to adjustments, I would like to move to
> a vote on this policy soon.
>
> Regards,
> David Handermann

Reply via email to