[Framework-Team] Re: Plone 2009: Going from here

Encolpe Degoute encolpe.degoute at free.fr
Wed May 13 02:22:49 UTC 2009

Ricardo Newbery a écrit :
> On May 12, 2009, at 4:23 PM, Steve McMahon wrote:
>> Ideally, a framework team should have an odd number of members in
>> order to avoid tie votes. However, in watching the last couple of
>> voting sessions for Plone 3, I noticed that there were not that many
>> PLIPS on which every person voted. So, I think the 'odd number' rule
>> of thumb isn't really that important.
> <parliamentary pedantry mode on>
> Of course an 'odd number' usually only becomes important if something
> contentious is on the table which can easily result in all members
> casting votes.
> Since most groups define majority approval as "greater than half", a
> split vote means it fails.  The problem arises when a proposal can be
> legitimately worded in either the affirmative or the negative.  So in
> the case of a split vote, the same proposed action can either pass or
> fall just by stating it in a different form.
> In the case of PLIPs, there seems to be an unofficial rule that they are
> always worded in the affirmative as a proposal to change the status
> quo.  As long as that rule is enforced and these are the only votes ever
> solicited then an 'odd number' rule is probably superfluous.
> <parliamentary pedantry mode off>

The most important in a PLIP vote is that no FTM put a veto on the
proposition and later on the implementation done. If one think that the
PLIP need to take in account an important usecase or that the code needs
more polish or a refactoring the PLIP shoud be delayed.
It was done in the past and ensure the global quality of a release.

Generally when a consensus is reached the vote always have a strong
majority. The FT is working to find the consensus that every Plone
developer will accept not to impose by a vote of few an unwanted
solution to all. Until now precedent teams succeeded in this way.

Logiciels libres, hockey sur glace et autres activités cérébrales

More information about the Framework-Team mailing list