Joe, Thanks for the feedback and confirmation. I will send out a vote thread, keeping it focused to committer status, but plan to raise a follow-on discussion regarding PMC status soon.
Regards, David Handermann On Mon, Aug 25, 2025 at 10:22 AM Joe Witt <joe.w...@gmail.com> wrote: > > David, > > This seems very reasonable and I'd support it. > > It seems even framed well to apply to the PMC but I understand this is > committer scoped at this time. > > Thanks > > On Mon, Aug 18, 2025 at 6:54 AM David Handermann < > exceptionfact...@apache.org> wrote: > > > Based on the positive discussion thus far, I would like to put this > > policy up for a vote later this week. > > > > Regards, > > David Handermann > > > > On Tue, Aug 5, 2025 at 9:13 AM Bob Paulin <b...@bobpaulin.com> wrote: > > > > > > Thank you for the background David. I was able to locate the thread, it > > > was a multi-topic thread so I did not see it initially. I agree with > > > your interpretation of the Bylaws and appreciate the way this topic has > > > been brought to the community for additional discussion. > > > > > > Sincerely, > > > Bob Paulin > > > > > > On 8/5/2025 8:42 AM, David Handermann wrote: > > > > Thanks for listing the committers to whom this would potentially apply > > > > Pierre, that is helpful context. > > > > > > > > Thanks for asking about the background discussion, Bob, the initial > > > > discussion took place among on the private Project Management > > > > Committee list. The purpose of this thread is to continue the > > > > discussion with the broader community, with some basic structure to > > > > keep it from being too open-ended. > > > > > > > > By way of additional background, Apache provides some guidelines for > > > > Project Management Committees but leaves the details to the discretion > > > > of each project. > > > > > > > > https://www.apache.org/dev/pmc.html > > > > > > > > The Fineract project approved a duration of 60 months before > > > > considering a committer to be inactive: > > > > > > > > https://lists.apache.org/thread/dhjo4ty5ymgsbobg8hy7n746kbw3z8ol > > > > > > > > The Hadoop project Bylaws state that PMC members become emeritus after > > > > six months of no contributions: > > > > > > > > https://hadoop.apache.org/bylaws.html > > > > > > > > This proposal attempts to find a middle ground, and match the goals of > > > > the Apache NiFi project. Previous NiFi PMC discussion on the topic did > > > > not make progress, which is the reason for some of the private > > > > discussion, which preceded opening this topic for more public > > > > discussion. > > > > > > > > Regards, > > > > David Handermann > > > > > > > > > > > > > > > > On Tue, Aug 5, 2025 at 7:51 AM Bob Paulin <b...@bobpaulin.com> wrote: > > > >> Hi, > > > >> > > > >> As a member I had some difficulty locating this discussion of policy. > > > >> Can you please link to it? There are a number of items detailed in > > this > > > >> policy that I believe will enhance the security of the Apache NiFi > > > >> community. Some of these are very similar to policies that have been > > > >> discussed by other projects in the foundation. Points 1-4 I believe > > are > > > >> positive steps to ensure infrequently used credentials are prevented > > > >> from write accessing the repository. I have not seen policies that > > auto > > > >> move committers to emeritus and require re-nomination so I'd be > > looking > > > >> for some prior art there to review or at least some more on list > > > >> discussion around this. I expect more PMC will be adopting these > > kinds > > > >> of policy and I think it's important that projects that adopt these > > > >> policy are transparent with the rationale with the community. > > > >> > > > >> Sincerely, > > > >> > > > >> Bob Paulin > > > >> On 8/5/2025 5:32 AM, Pierre Villard wrote: > > > >>> 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 > > > >> > > > > >
