Just my thoughts, One thing that makes it hard to determine who to vote for (especially for those who are or have been on the TC before) is determining during their past term what they accomplished or helped get through the TC. In a way if I vote for X candidate and they have been on the TC before what was accomplished during their last term to know if anything will be any different this time around.
It may be hard to define this set of information, but I think visibility would help (without having to scrape the TC logs [1]). Knowing how a candidate has voted, decided on and what issues they have helped resolve in the larger community helps myself be more confident in voting for those types of candidates again (this doesn't work for new candidates obviously). It also ensures/reinforces that being involved in the TC voting process will actually have *meaningful* results for OpenStack as a whole. Is there any kind of central location where we can look at what a TC candidate has done before (what their proposals we, what they voted on, or any other similar kind of information; in a way this is similar to having visibility into what a US congressman/senator does, which is *some of the* information people use to determine who they should vote for in the US)? -Josh [1] http://eavesdrop.openstack.org/meetings/tc/ -----Original Message----- From: Anita Kuno <ante...@anteaya.info> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Friday, May 23, 2014 at 7:45 AM To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org>, "openstack...@lists.openstack.org" <openstack...@lists.openstack.org> Subject: [openstack-dev] Election Stats and Review Discussion >One of the things that OpenStack does really well is review our process >for various activities. I don't believe we have had a discussion in the >past reviewing our electoral process and I think it would be good to >have this discussion. > >There are two issues that I feel need to be addressed: >Item One: the health of our voter engagement for the tc election >Item Two: messaging around campaigning >others may feel additional issues need some airtime, if you can think of >other issues affection our election process for ptl and/or tc elections, >do add your item to the list. > >Item One: > the health of our voter engagement for the tc election > >Going by voter turnout, the health of individual programs as reflected >in the ptl voter turnout statistics is sound (43.5% voter turnout or >better) however the health of the voter turnout for the tc election >process could tolerate some scrutiny. > >For the April 2014 tc election the voter turnout was 29.7%. We have had >a total of three tc elections in the history of OpenStack and our voter >turnout percentage is dropping. >First TC Election, March 2013: 33.6% voter turnout >Second TC Election, October 2013: 30.9% voter turnout >Third TC Election, April 2014: 29.7% voter turnout > >Now our actual votes cast are increasing, but the size of the electorate >is increasing faster, with proportionally fewer ATCs voting >March 2013: 208 votes cast, 619 authorized voters >October 2013: 342 votes cast, 1106 authorized voters >April 2014: 448 votes cast, 1510 authorized voters > >I would like for there to be a discussion around voter engagement in the >tc election. > >Item Two: > messaging around campaigning > >Right now we have no messaging around election campaigning and I think >we should have some. > >Specifically I feel we should state that the TC requires candidates and >their backers to campaign in the spirit of the OpenStack ideals >(Openness, Transparency, Commonality, Integration, Quality...) as >stated in the TC mission statement[footnote] while refraining from >sending unsolicited email and also refraining from holding privately >sponsored campaign events. Campaigning is expected to be done in the >open with public access to links and content available to all. > >I welcome your participation in this discussion. > >Thank you, >Anita. >anteaya > >[footnote] The Technical Committee ("TC") is tasked with providing the >technical leadership for OpenStack as a whole (all official programs, >as defined below). It enforces OpenStack ideals (Openness, >Transparency, Commonality, Integration, Quality...), decides on issues >affecting multiple programs, forms an ultimate appeals board for >technical decisions, and generally has oversight over all the OpenStack >project. > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
