Steven Noels wrote:
> Nicola Ken Barozzi wrote:
> > The Incubator should try to minimize cross-votes, as they have shown
> > in practice to be very confusing and not productive.
> >
> > I don't like this Mentor+Lenya+IncubatorPMC double vote either. The
> > alternative is to have all Lenya committers on the Incubator PMC, but I
> > don't think others are ready to accept it, nor if all the implications
> > of it are clear.
> ... and I know for a fact that some, if not many Lenya peeps are *not*
> on any [EMAIL PROTECTED] list, perhaps hinting at a lack of interest in a
> one-for-all cross-project incubation mailing list, or the centralization
> of 'power' in the Incubator PMC (that's my interpretation) - I did hear
> some complaints about 'Incubator lists being noisy and not so helpful'
> during the Con.
As you know, we are discussing some options related to this topic. One
would be that for a given subproject, we would have
[EMAIL PROTECTED], where the members of that list consist
of the Incubator PMC, the subproject's committers, and (if there is one) the
PMC for the destination TLP. So in the case of Lenya, that would mean the
Incubator PMC, the Cocoon PMC and the lenya committers.
That doesn't require all Lenya committers to be on the Incubator PMC, keeps
the Cocoon PMC involved, and provides direct oversight from the Incubator
PMC. The decisions are made in one place at one time, rather than spread
out over time and project and people.
Thoughts?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
