Ted Leung wrote:
>On 9/23/2003 12:10 AM, Nicola Ken Barozzi wrote:
>> Ted Leung wrote:
>>> Meritocracy / Community
>>>   Demonstrate an active and diverse development community
>>>   No single organization supplies more than 50% of the active
>>>   committers (must be at least 3 independent committers)
>> How do you assess that? Are we sure 50% is not too much? Will it take
>> too much time?

> For demonstrate an active and diverse development community - its one of
> those that has an "I'll know it when I see it test".

> As far as the 50% figure, I have my reservations

> You can call it the "anti-big-company" rule.

Diversity is good on the grounds that (a) no one company can control the
direction of an ASF project, and (b) the fate of one company doesn't dictate
the fate of the project.

I see it as a Catch-22 in some cases, and I don't know of any ready-made
solutions, but hopefully others have good ideas.  The more widespread the
project's appeal, the better it reaches out to other communities, the more
likely it is to attract a more diverse Committer base.

I have two interim suggestions that don't fix the lack of diversity, but do
address two potential concerns.  First, the project must have at least N
independent committers, as you have already put on your list.  Second, limit
the influence of the corporate committers on the PMC.  That could be
controversial.  Lastly, an observation: if there are technical disputes, any
one committer, independent or otherwise, can veto changes that he or she
doesn't feel are in the best interests of the project.

>>> Release plans are developed and excuted in public by the community.
>> Yup, this is important. We now have Apache projects that do not follow
>> this rule sometimes and have to be reminded every time, so it's a good
>>idea.

>>> (requriment on minimum number of such releases?)
>> two?
>That's two "Not official ASF releases" ;-)

LOL Call them "Dress Rehearsals"  :-)  I agree that they should learn the
process until it becomes a habit.

I don't believe that an project in the incubator should be allowed to make
an official release because they have not cleared whatever issues are
keeping them in the incubator, and not a part of the Foundation proper.
Upon further reflection, it does occur to me that it is possible for the
podling to go to the Incubator PMC under appropriate circumstances, and
request that the Incubator PMC vote to make a Release.  I do not believe
that it should be a common practice, but processes should allow for
exceptions and human judgment.

        --- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to