Hi PJ, Fair point, and thanks for raising it. The "one committer" line is already out of date. Thank you for your own contributions. We now have four or five people active on the project, with six stars, two issues, and a few PRs. I expect the committer base to grow naturally once there is a clear place to plug in.
Larry, thank you, I would be glad to have you as a mentor and on the PPMC. Knox is the closest analogue to what I am building for MCP governance, and I would much rather learn from it than reinvent it. Your two points hit my roadmap directly. The RFC 8693 token exchange with an actor chain is exactly the delegation model I want instead of my current per-caller pass-through, and that is my 0.2 credential work. Knox's shared JDBC token state is the same gap behind my single-replica limit, which is my 0.2 HA work. Your Ranger suggestion is worth talking through early. I will write up a short mapping of the Aegis chain onto Knox's provider chain so we have something concrete to look at. Looking forward to working with you and learning from your guidance Thanks all. Viquar Khan On Sat, Aug 8, 2026 at 9:25 PM Justin Mclean <[email protected]> wrote: > Hi, > , > > I wanted to say a word on project governance. Specifically, how can we > > ensure that individuals who are already PPMC members across multiple > > projects don't monopolize leadership roles here? > > > > Are there any existing quotas, guidelines, or best practices regarding > the > > number of projects someone can be involved in as a committer or PPMC > > member? > > I suggest you take a look at these documents on mentors: > https://cwiki.apache.org/confluence/x/cQqRFw > https://cwiki.apache.org/confluence/x/cwqRFw > > Re (P)PMC or committers, there are no real limits or advice that I’m aware > of. > A few reasons why: > > Committer and PPMC roles are not a fixed pool of seats. Adding one person > doesn't prevent adding another. If several experienced contributors are > eager to step up, the answer is to invite all of them, not to ration roles > among them. > > The ASF works on merit within each project. Merit is earned per project > and doesn't carry over, so someone being on five other PPMCs gives them no > standing here beyond what they've contributed. Equally, it doesn't count > against them. > > People involved in many projects are usually a benefit, not a problem. > They bring experience of how other communities handle releases, votes and > governance, which is exactly what a new project needs. > > If your concern behind your question is capacity: can someone spread > across many projects give this one enough attention? That varies widely and > on a case-by-case basis. > > Kind Regards, > Justin > > >
