Berin Loritsch wrote:
Due to the past history in this project with vetos being abused, I want to make
it a matter of policy that no one user can block the rest of the team with a
veto. We are all free to express our discontent with a resolution, but if the
team chooses against your resolution, then you are out of luck. Vetos have
consistently been used to ram one developer's opinion on the rest of the team,
making cooperation unattainable.
We must learn to work together.
VOTE:
Officially disallow all vetos for technical and policy issues.
+1 from me
Berin:
While I respect you persistence in attempting to get around by objection to your change, I think this has gone far enough. The principals of veto rights are an accepted Apache policy. I refer you to the incubator pages on policy:
Vetos
A code-modification proposal may be stopped dead in its tracks by a -1 vote by a qualified voter. This constitutes a veto, and it cannot be overruled nor overridden by anyone. Vetos stand until and unless withdrawn by their casters.
To prevent vetos from being used capriciously, they must be accompanied by a technical justification showing why the change is bad (opens a security exposure, negatively affects performance, /etc./). A veto without a justification is invalid and has no weight.
As a member of the PMC - I call on you to retract this vote an the grounds that is it invalid from a Avalon procedure point of view (no prior discussion was initiated). Should you continue you will be in breach of the Avalon polices and procedures and I will have no choice but to call for your resignation as PMC Chair.
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
