Monty Taylor wrote: > Different but related question (might be hard to calculate though): > > If we remove people who have only ever landed one patch from the > electorate, what do the turnout numbers look like? 2? 5? > > Do we have the ability to dig in slightly and find a natural definition > or characterization amongst our currently voting electorate that might > help us understand who the people are who do vote and what it is about > those people who might be or feel different or more enfranchised? I've > personally been thinking that the one-patch rule is, while tractable, > potentially strange for turnout - especially when one-patch also gets > you a free summit pass... but I have no data to say what actually > defined "active" in active technical contributor.
As a sidenote, we are a bit limited by the Foundation bylaws in tweaking what rules gives you the right to vote in the TC election. "The members of the Technical Committee shall be elected by a vote of the Active Technical Contributors (“ATC”) using a fair voting method determined by the Technical Committee" "An Individual Member is an ATC who has had a software contribution approved for inclusion in any of the modules of the Core OpenStack Project during one of the two prior release cycles of the Core OpenStack Project (“Approved Contribution’). Such Individual Member shall remain an ATC for three hundred and sixty five days after the date of acceptance of such Approved Contribution." (from http://www.openstack.org/legal/technical-committee-member-policy/) We further define the ATC in the TC charter, so I guess we could redefine that "a software contribution" means at least 2 patches. It's harder to play with the 2-cycle timeframe without requiring a bylaws change, though. -- Thierry Carrez (ttx) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
