The thing to avoid is to wind up with a significant number of active contributors on a project who are not on the pmc. Separating committers from pmc members can be a symptom but it's manageable under the right conditions. Note committers aren't the only class of contributors that projects might be unintentionally excluding from pmc participation.
Sent from my iPhone On Dec 19, 2012, at 11:50 AM, Ted Dunning <ted.dunn...@gmail.com> wrote: > Well, different policies make sense at different phases of growth. A new > project is in growth mode and a major goal is to bind people into the > project. C == PMC helps do that. If you have nothing to lose and > everything to gain, then this is a pretty reasonable idea. > > A more mature project has something to lose so there is a case that C != > PMC makes some sense. > > On Wed, Dec 19, 2012 at 5:02 AM, Christian Grobmeier > <grobme...@gmail.com>wrote: > >>> 2. Historically, podlings have *not* maintained this distinction, but >>> have waited for graduation to sort out the initial PMC members. >> >> Why do they behave differently than later as TLD? >> --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
