[proposal] development process

[Leo Sutic]

Leo Simons wrote:
> No Veto
> -------
> We will refrain from the use of vetoes on medium to long-term issues on
> all code in all avalon cvses.
>
> +1 from me

-1

The solution to our social problems is not to cripple the voting process.
Our issue as a group is that we suck when it comes to handling disagreement.
If we abolished vetoes, the same mechanisms that would previously have
resultet in a burst of vetoes would find some other way of deadlocking
the process. (COMMIT/REVERT/COMMIT/REVERT/..)

Let's learn to use vetoes right instead, and let's do it by trial and error and
trying to learn - we're all that smart, right?

> Isolate controversy
> -------------------
> We will place all code that might be controversial in the avalon-sandbox
> cvs until there is a consensus (ie it becomes non-controversial).
>
> +1 from me

Sounds like a good idea, but I thought this was standard practice. This is
the standard "experiment on isolated code, merge it back with the main trunk
when it is proven to work and we have concensus", right?

If so, +1.

> Consensus
> ---------
> we will require consensus on the issues that would normally be subject
> to majority vote.
>
> +1 from me

1) Shouldn't be difficult with no -1:s being admissible, right?

2) -1

3) As I said above, I don't think our social issues are best helped
by modifying the voting process.

/LS


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