Re: cvs commit: avalon-sandbox/avalon5 - New directory

[Sam Ruby]

Stefano Mazzocchi wrote:
>
> I also propose that every committer that will propose an internal
> fork will have to go thru the community vote to be allowed to do
> that.

+1

From an e-mail I sent to community@ (Subject: Convergence, vetoes, forks, and projects):

> Forks should be clearly identified with separate names per the rules
> for revolutionaries e-mail. For external forks, i.e., ones that
> reside outside of ASF servers, this is all that is necessary. For
> internal forks, it is important to realize that the PMC is still
> accountable for that code and the rules for voting and commit
> privileges still apply.
>
> In other words, the creation of such internal forks is to be done
> based on consensus on the scope, visibility, and design direction of
> such an effort. This does not mean that there needs to be consensus
> of opinion on the viability of the design approach; merely that the
> idea merits exploration - even if the ultimate result is only to
> prove that it is indeed a dead end.
>
> As long this code resides under the purview of an existing PMC, no
> separate voting or commit rights should be sanctioned for this code.
> Nor should vetoes be used after the fact to change the agreed upon
> scope of such an effort.

- Sam Ruby




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