TC Process Descriptions


This page contains some informal description of the process that should be followed by TC members.

Vote

Sometimes, TC members are expected to vote on a given topic.

The vote is open for a pre-defined amount of time (usually 72 hours / 3 days) that have to be clearly written in the vote thread.

The vote options are +1, 0 or -1.

  • +1 means I'm OK with the proposal
  • 0 means I don't care
  • -1 means I'm opposed to the proposal (veto)

The veto vote must be argued: it's a showstopper. We must know what is wrong and why we should stop the vote (any -1 without proper explanations will be ignored).

The option that will obtain the majority+1 of casted votes will be choosen.
Ex: if there are 10 participants, the elected option must have at least 6 casted votes ( (10/2) + 1 ).

The results will be announced on the TC list as soon as possible.

Examples

The vote manager (usually CTO or TC Chairman) should start a new thread on TC list with an explicit subject: [VOTE] <topic>.
Some examples:
[VOTE] Maturation Lifecycle Criteria
[VOTE] Accept New Project : CONTRAIL
[VOTE] Archive Project : Funambol

Example of vote mail content:
The vote is to decide if we change the project lifecycle maturation criteria.
The proposal is here: http://www.ow2.org/view/TechnologyCouncil/Project+Maturation (rev 18.1)

[ ] +1 Use this set of criteria
[ ]  0 Don't care
[ ] -1 Veto, do not change anything (must be argued)

Graduation

Project Acceptance

Get Involved

Share technical know how with other users, and help to promote OW2

TC Live

 

 


This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 6.4.4 - Documentation
Powered by XWiki Hosted by Xsalto Free PageRank Checker Creative Commons 2.0 license Legal Notice