Similarly, I would not hold AOO as a typical podling - both the size,
complexity, and very, ahem, rich past history and personalities had a
large influence on their growth.
The real issue is: how do we clearly express these two possibilities for
podlings and potential donors/contributors to better understand them?
I.e. the concept of either c == (P)PMC or c != (P)PMC (or even P=NP).
Even better: is there a general consensus on either the IPMC recommended
best practice, or, failing that, on a discussion page that lays out what
kinds of things a podling community would want to evaluate and think
about when they are trying to make their decision on their policies?
This is another place where we don't need a rule - but we do need to
better explain in docs what the best practices (in this case, either
one) for Apache projects are.
- Shane, personally for c != PMC, because it makes it easier to invite
people earlier
On 12/19/2012 7:43 AM, Benson Margulies wrote:
A recent vote thread on the private list led Christian Grobmeier to
wonder why a podling was simultaneously proposing someone for PPMC and
committer status.
A few bits of background:
1. TLP's vary in their behavior in this regard. Some maintain a
committer!=PMC distinction, and some do not.
2. Historically, podlings have *not* maintained this distinction, but
have waited for graduation to sort out the initial PMC members.
3. Legally/organizationally, since PPMC members don't have binding
votes, there's not much practical effect of making a distinction. At
the end of the day, only Incubator PMC members have binding votes.
4. Christian pointed out that the Open Office podling found the
process of sorting out the PMC/committer distinction to be painful.
With all respect, I don't see the OO podling as typical. It's sheer
size put it in a different category, and I for one do not feel
inclined to tell podlings to start keeping PPMC and committer distinct
on the basis of that history.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
