I think the idea is not to *remove* members. My understanding (at least, what I agree with) is to flag members as active or not. This would help having a better understanding of the community dynamics, as indicated in the original email. If we don't remove members, any inactive member can just be active again by simply... becoming active.
Guillaume Le mar. 22 oct. 2024 à 21:36, Elliotte Rusty Harold <elh...@ibiblio.org> a écrit : > -1 > > At least once I have personally brought a long dormant Maven PMC > member out of hibernation to approve PRs and releases, and it was very > helpful for moving the train along when active PMC members weren't > interested enough in what my team was doing to review code and vote > for releases. And now that I think about it, I also had to do that > (reach out to a former maintainer to reclaim ownership of a repo and > project) for a non-Apache project where the current maintainer had > gone incommunicado and could not be reached. > > Perhaps even more importantly I have seen other Apache projects get > captured by a single active PMC member with idiosyncratic ideas about > software development and go seriously off the rails to the detriment > of users. > > A larger pool of PMC members and committers, even long dormant ones, > provides at least some buffer against this dysfunction. > > On Tue, Oct 22, 2024 at 4:17 PM Tamás Cservenák <ta...@cservenak.net> > wrote: > > > > Howdy, > > > > I would like to propose a project policy change (followed by > > implementation) regarding "emeritus" status of PMCs and members. > > > > Proposal: > > 1) IF a PMC member is inactive for 24 months (did NOT participate in > > any VOTE [by casting binding vote] OR did not create any commit that > > ended up in the project), he should be automatically moved to > > "emeritus PMC" status. > > 2) IF a committer is inactive for 24 months (did NOT participate in > > any VOTE [by casting vote] OR did not create and/or review any commit > > that ended up in the project), he should be automatically moved to > > "emeritus committer" status. > > > > Reasoning: > > Currently if interested party checks ASF report about Maven project on > > https://projects.apache.org/committee.html?maven , the presented data > > is skewed, if not even false, about "who" (and more importantly "how > > many") user is working on a project. This can lead to some unpleasant > > misunderstandings as well (from "why is my PR not reviewed yet" to > > many others). Moreover, this same (wrong) number may in fact lessen > > potential contributors, make them turn away and choose another, less > > supported project to join. Finally, I think we should shrink the > > circle of "admin" powered users to those we are almost certain are > > around us and involved. Project already has "emeritus" roles for both, > > PMCs and committers AFAIK (correct me if I am wrong). > > > > WDYT? > > > > Thanks > > T > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- ------------------------ Guillaume Nodet
