oVirt comminuty voting

Itamar Heim iheim at redhat.com
Tue Sep 13 14:01:50 UTC 2011



> -----Original Message-----
> From: project-planning-bounces at ovirt.org
[mailto:project-planning-bounces at ovirt.org] On Behalf Of Jim
> Jagielski
> Sent: Tuesday, September 13, 2011 16:54 PM
> To: Anthony Liguori
> Cc: project-planning at ovirt.org
> Subject: Re: oVirt comminuty voting
> 
> A project lead implies that somehow his/her vote is more important
> than anyone else's, which is not how the ASF works.
> 
> The idea is to build a community that strives for consensus so that
> the need for tie-breaking votes isn't required. If half the community
> thinks A and the other B, then there is for sure no consensus.

How often are these and how do they get resolved?
How is a nack by someone resolved if majority are in agreement (ack it)?

> 
> >
> > Having 3 maintainers does not mean there isn't an overall project
leader.  We have around 30 maintainers
> in QEMU but only one project leader.  The project leader casts the tie
breaking vote.
> >
> > It's the same model as the kernel and many other communities.
> >
> > Regards,
> >
> > Anthony Liguori
> 
> --
> Jim Jagielski | jimjag at redhat.com | 443-324-8390 (cell)
> 
> _______________________________________________
> Project-planning mailing list
> Project-planning at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/project-planning



More information about the Project-planning mailing list