Voting in the Fluid community

Colin Clark colin.clark at utoronto.ca
Tue Apr 21 16:41:20 UTC 2009


Jess pointed out some ambiguities in my first draft, so I've revised  
the Voting document based on her feedback:

http://wiki.fluidproject.org/display/fluid/Voting

My main goal with these revisions was to clearly describe the  
difference between formal and day-to-day votes. Formal voting includes  
significant technical or design issues, and -1 votes are vetoes.  
Examples of formal votes include granting commit access or making  
large-scale architectural changes. Day-to-day ("procedural") votes  
operate by majority approval and are lazy: -1 votes are not vetoes.  
Examples of day-to-day votes include the proposal to change our  
standup meeting time, etc.

Hope this helps,

Colin


On 20-Apr-09, at 4:46 PM, Colin Clark wrote:

> Hey everyone,
>
> We've been operating for the past couple of years with an Apache- 
> inspired voting process. Realizing that we hadn't actually formally  
> articulated this process, I created a page in the wiki that explains  
> how we vote:
>
> http://wiki.fluidproject.org/display/fluid/Voting
>
> In short, we vote with +1 or -1 to express approval or disapproval.  
> For formal votes--generally technical or design governance issues--a  
> -1 vote represents a veto and comes with the responsibility to  
> explain what changes need to be made to shift the vote to a +1.  
> Informal issues operate by lazy consensus, which is why we emphasize  
> open communication so much.
>
> We also nominate new committers with this process. For more specific  
> information, see:
>
> http://wiki.fluidproject.org/display/fluid/Process+for+Granting+Commit+Access
>
> Feedback is always appreciated,
>
> Colin
>
> ---
> Colin Clark
> Technical Lead, Fluid Project
> Adaptive Technology Resource Centre, University of Toronto
> http://fluidproject.org
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work

---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org




More information about the fluid-work mailing list