Re: [DISCUSS] Aegis MCP Governance Gateway Incubator Proposal

> And for anybody at the ASF who *has*
> implemented an MCP, or *intends* to implement an MCP, to at least give
this
> proposal a once-over.

I failed to mention that I have created a couple MCPs as well as a POC of
Knox as an MCP Gateway. :)

On Sat, Aug 8, 2026 at 10: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
>
>
>