The OpenStack Blog

Category: Governance

OpenStack Governance Discussion from Conference

The OpenStack community held an open discussion on the existing and future governance policy of the community. I taped the meeting with my FLIP camera so apologies for the so-so video; however the audio sounded fine when I ran through the tape.

OpenStack Conference: Governance Discussion from OpenStack on Vimeo.

Project Policy Board Membership – Update Post Election

Now that the Spring 2011 Governance Elections have completed, I would like to formally update the community on the OpenStack Project Policy Board:

Member Status
Jesse Andrews Appointed
Jonathan Bryce Appointed
Thierry Carrez Elected – Term ends Spring 2012
Rick Clark Elected – Term ends Fall 2011 (replacing Vish Ishaya)*
Eric Day Elected – Term ends Spring 2012
John Dickinson Swift PTL – Term ends Fall 2011
Soren Hansen Elected – Term ends Fall 2011
Vish Ishaya Nova PTL – Term ends Fall 2011
Joshua McKenty Appointed
Ewan Mellor Elected – Term ends Fall 2011
Jay Pipes Glance PTL – Term ends Fall 2011
John Purrier Appointed

* The election of Vish Ishaya as the Nova Project Team Lead vacated his previously held elected position on the PPB. Based on the governance rules , the nominee with the next highest votes in the PPB general election will serve out the remaining term of the vacated seat. Thus, Rick Clark having received the third most votes in the PPB election will take over Vish Ishaya’s previously held position on the PPB which will expire in the Fall 2011.

This appointed and elected board of community leaders provides a solid leadership team to drive the project forward and I look foward to working with this board in 2011.

OpenStack Governance Election Results

The OpenStack Community has completed the governance elections as described in several previous blog posts: here and here. The results of the voting are as follows:

Project Technical Lead SWIFT: John Dickinson

Project Technical Lead NOVA: Vishvananda Ishaya

Project Technical Lead GLANCE: Jay Pipes

Project Policy Board (2 Positions): Thierry Carrez and Eric Day

Congratulations to the winners of this election and thank you to all the nominees and voters.

Community Weekly Newsletter (March 19 – 25)

OpenStack Community Newsletter – March 25, 2011

This weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please email [email protected].

Watch live streaming video from gigaombigdata at livestream.com

Nice technology discussion; OpenStack mention at 20:00 minutes in.

HIGHLIGHTS

EVENTS

DEVELOPER COMMUNITY

GENERAL COMMUNITY

COMMUNITY STATISTICS (3/18– 3/24)

  • Data Tracking Graphs – http://wiki.openstack.org/WeeklyNewsletter
  • OpenStack Compute (NOVA) Data
    • 22 Active Reviews
    • 192 Active Branches – owned by 48 people & 10 teams
    • 2,320 commits by 63 people in last month
  • OpenStack Object Storage (SWIFT) Data
    • 4 Active Reviews
    • 47 Active Branches – owned by 19 people & 4 teams
    • 189 commits by 13 people in last month
  • Twitter Stats for Week:  #openstack 113 total tweets; OpenStack 281 total tweets  (does not include RT)
  • Bugs Stats for Week:  408 Tracked Bugs; 80 New Bugs; 21 In-process Bugs; 9 Critical Bugs; 51 High Importance Bugs; 209 Bugs (Fix Committed)
  • Blueprints Stats for Week:  169 Blueprints; 4 Essential, 11 High, 16 Medium, 22 Low, 116 Undefined
  • OpenStack Website Stats for Week:  11,129 Visits, 24,014 Pageviews, 60.51% New Visits
    • Top 5 Pages: Home 43.70%; /projects 11.86%; /projects/compute 15.96%; /projects/storage 11.40%; /Community 6.20%

OPENSTACK IN THE NEWS

OpenStack Governance Elections Underway

The OpenStack community elections are underway until April 1, 2011 at 11:59 pm CST. All authorized members of the community should have received election emails this morning with information on how to vote and for which election. If you believe that you should have received a voting email, please contact me immediately so we can validate your eligibility to vote and fix the issue.

OpenStack Governance Election Process

As I stated in my earlier OpenStack Governance post, I am following up with the details for the election process. Please send me any thoughts you have on this process so I can ensure that everyone in the community is aware of the process and tools being used. I am presenting details on the four separate elections being run as each election has different requirements based on the OpenStack governance policy .

The elections will run from March 21, 2011 thru April 1, 2011 at Midnight CST. Final results will be posted first thing in the morning on April 4, 2011 when I get into the office on the OpenStack blog (http://openstack.org/blog), within the CIVS (see below) election system tool, and via an email to the OpenStack developer mailing list.

NOVA Project Team Lead (1 Position)

Voter Eligibility – Only OpenStack community members who have successfully submitted code to the NOVA project are eligible to be nominated or vote.  I am using the list of email addresses found at http://bazaar.launchpad.net/~hudson-openstack/nova/trunk/view/head:/Authors for eligible electors and nominees. Each member of this list will receive an email with a direct link to the NOVA PTL team lead election site where they can vote for the member of their choice. Each member can only vote once in this election.

SWIFT Project Team Lead (1 Position)

Voter Eligibility – Only OpenStack community members who have successfully submitted code to the SWIFT project are eligible to be nominated or vote.  I am using the list of email addresses found at http://bazaar.launchpad.net/~hudson-openstack/swift/trunk/view/head:/AUTHORS for eligible electors and nominees. Each member of this list will receive an email with a direct link to the NOVA PTL team lead election where they can vote for the member of their choice. As this list only has author names, I will be reaching out to several members whose email I do not have; of course, if you are on the list you can simply send me your email address to save me time in searching out your contact information. Each member of this list will receive an email with a direct link to the SWIFT PTL team lead election site where they can vote for the member of their choice. Each member can only vote once in this election.

GLANCE Project Team Lead (1 Position)

Voter Eligibility – Only OpenStack community members who have successfully submitted code to the GLANCE project are eligible to be nominated or vote. At this time, the following developers are authorized to vote or be nominated for this position:

Rick Harris – Cory Wright – Chris MacGown – Vishvananda Ishaya – Monty Taylor – Jay Pipes

If you believe that you should be on the GLANCE list, please email before March 19th as I will be sending out election links on March 21st.

Each member of this list will receive an email with a direct link to the GLANCE PTL team lead election site where they can vote for the member of their choice. Each member can only vote once in this election.

Project Policy Board (2 Open Positions)

Voter Eligibility – Any registered member of the OpenStack Launchpad is eligible to run or be nominated for one of the two positions. I am getting this list of authorized voters and nominees from the Launchpad system at https://launchpad.net/~openstack. Based on current numbers, there are 632 people eligible to vote or be nominated.

PTL Member Wins 1 of 2 Slots – Based on the governance policy, if either of the two top vote getters are also winners in the PTL election, then the next highest person on the election results will be declared the winner. From the governance policy:

If an individual should happen to be elected as both a PTL and General Member of the PPB, then they will take their PTL seat only and the elected General Member seat will go to the next highest vote getter

The Condorcet Internet Voting System (see below) leverages ranked choices thereby making the possibility of a tie extremely unlikely. If a tie does occur, a runoff between the two candidates who tied will be held.

ELECTION TOOL

For all four of the elections, we will use the Condorcet Internet Voting Service from Cornell University, see http://www.cs.cornell.edu/andru/civs.html. This tool uses the Condorcet method of voting which invokes ranking the nominees instead of just selecting one choice. More information on this methodology is at http://www.cs.cornell.edu/w8/~andru/civs/rp.html.

All registered voters will receive an email with a unique link allowing them to privately vote.

For the Project Advisory Board election, in order to collect voters email addresses I will contact every potential voter using the “Contact this team’s members” feature at https://launchpad.net/~openstack and ask them to reply directly to me using their preferred voting email address if they want to participate in the vote.

Please note that the voting system is run using private polls with restricted access to ensure voter authenticity; however all results will be made public once the election ends. The only delay in posting results will be due to me not being awake when the elections end at midnight.

TRIAL RUN
I am planning to run a trial of this tool on March 17 and anyone wishing to take part in the trial can email me and I will include you in the voting trial.

As is standard, please contact me with any questions you have on the voting process, nomination process, governance policy or any other issue in the OpenStack community,

OpenStack Project Techncial Leads (PTLs)

From Thierry Carrez:

I’d like to quickly precise what will be expected, from a release management perspective, from the Project Technical Leads (PTLs) some of us will nominate and elect in the following weeks.

PTLs, like it says on the tin, will have to technically lead each project. That comes with a few rights, but also with a lot of duties that the candidates shouldn’t underestimate…

Rights include the ability to decide between conflicting opinions on a technical debate, or the authority to set the theme for the next release. Exercising those rights will only be possible if the technical opinions of the elected lead are widely respected in the project.

Duties of the PTLs, from a release management perspective, mainly include coming up with a plan for the next release(s). That means staying on top of what everyone proposes, selecting (and rejecting) blueprints for a given cycle, setting priorities, approving designs (potentially with the help of other project drivers), or making sure we don’t duplicate work. The PTLs should also be very impacted by the design summit preparation, making sure we have sessions for what we need to discuss, and encouraging people to submit corresponding blueprints.

As release manager, I can help with the process, but the decisions must come from the PTLs, who have the legitimacy of being elected. During the cycle, I will then help in making sure the defined plan is on track.

With a well-established project like Swift or a relatively-small project like Glance, the PTL work can certainly be done at the same time as regular development. For Nova however, the PTL should expect project coordination work to take a large part of his time, so he could find himself not being able to write as much code as he would want. That should be kept in mind before you accept nominations.

Hoping this helps in clarifying expectations… Happy nominating and voting !

OpenStack Governance Nominations and Election Process

As stated in Jonathan Bryce’s OpenStack Governance Update last week, the OpenStack governance process has been modified to better serve the community and include additional community-elected leaders. This blog post details the nomination and election process for the open positions detailed in Jonathan’s post.

PROCESS

Nominations – Starting Tuesday March 8th thru March 18th at Midnight CST any person interested in one of the available positions and meeting the requirements (see below) can either self-nominate or be nominated for an open position. All nomination requests should be sent via email to [email protected] and include the following information:

  • Name of person being nominated including email address
  • Position posting for (PTL NOVA, PTL SWIFT, PTL GLANCE, PPB GENERAL)
  • Company name (individual developers can just put Independent)

All nominated and qualified people will be added to a public Etherpad at http://etherpad.openstack.org/Spring2011-Elections.

Elections – Starting Monday March 21 thru April 1 at Midnight CST all nominated people will be put into an online election system for community voting. Each position open for election has unique requirements for eligibility to vote thus four separate elections will be held at the same time. Details on the election process are still in review and planning; however, information on the process will be posted before the election system is activated.

Results – On April 4, 2011 the final voting results will be published to the community on the OpenStack blog at http://openstack.org/blog.

POSITIONS

Please review the descriptions of the available positions at http://wiki.openstack.org/Governance/Model to better understand the commitments involved. These are significant leadership positions within the OpenStack community and your contributions via these positions will have a large impact on the overall project. Here are some additional points to be aware of for these positions:

  • Approve and prioritize blueprints for releases, communicate roadmap
  • Coordinate the technical sessions at the design summit that occurs after their elections
  • Resolve any deadlocked conflicts in the community
  • Work with the release manager to ensure releases stay on track and status is communicated broadly
  • Implement project-specific policies such as choosing subject matter experts, code review policies
  • Participate in the #openstack IRC channel and developer mailing lists

The following positions are available for the election process:

Project Technical Leads - PTL Nova, PTL Swift, and PTL Glance

OpenStack is currently designating the following three projects – Nova, Swift, and Glance as requiring a separate project technical lead. Other projects within OpenStack will work with the Project Policy Board to determine needs for a technical lead.

Requirements – From the OpenStack Governance Model:

Anyone who has submitted code which has been accepted into the respective project’s trunk is eligible to run for a PTL seat, and to vote for the PTL. Sitting Project Technical Leads are eligible to run for re-election each cycle, provided they continue to meet the criteria.

Project Policy Board - General Board Seat A, General Board Seat B
Requirements – From the OpenStack Governance Model:

Any registered member of an OpenStack Launchpad group is eligible to run and vote in these elections. The TWO individuals receiving the most votes will assume these seats. If an individual should happen to be elected as both a PTL and General Member of the PPB, then they will take their PTL seat only and the elected General Member seat will go to the next highest vote getter.

If you have any questions on this process, please contact [email protected] who is managing nominations and elections for these positions.

OpenStack Project Oversight Committee

The OpenStack Project Oversight Committee (POC) was formed at the end of last year. The committee is a mixture of appointed and community elected members who fill nine seats. The current members are Jesse Andrews, Jonathan Bryce, Rick Clark, Soren Hansen, Mark Interrante, Vish Ishaya, Joshua McKenty, Ewan Mellor and Chuck Thier. One of the responsibilities of the POC is to approve policies for the operation of OpenStack sub-projects.

As Rick mentioned in this week’s release meeting, one policy has just been approved–a procedure for adding developers to core teams. This was a policy that was proposed to the general OpenStack mailing list for open discussion. After a period of time, the POC then took up discussion of the issue and voted to adopt the proposal. John Purrier has followed a similar process for a number of proposals and the POC is currently considering two.

The majority of POC discussion and voting has happened on a Launchpad group mailing list. Archives are publicly available and anyone interested in reviewing the detailed discussion can view the threads here: https://lists.launchpad.net/openstack-poc/

In addition, the POC will be holding regular IRC meetings, and the logs and minutes of those meetings will be available as well. A summary of POC activity and links to relevant information will be available on the OpenStack wiki: http://wiki.openstack.org/Governance/POC

In the last six months, OpenStack has grown and matured, and we have heard a lot of great feedback on the governance model. As the year progresses, I expect that we will continue to refine and improve our governance processes and models. If you have feedback, suggestions, or questions, please share them with me ([email protected]).

OpenStack Conference/Design Summit Program Committee

I am pleased to announce the formation of the OpenStack Conference/Design Summit Program Committee who will work as a group to create the event agenda as well as overall conference theme. The following community members have volunteered their time:

  • Glen Campbell, Rackspace
  • Ram Durairaj, Cisco
  • David Holland
  • Jaesuk Ahn, Korea Telecom
  • Andrew Shafer, CloudScaling
  • Thierry Carrez, OpenStack Release Manager
  • Stephen Spector, OpenStack Community Manager

As the event is for the entire community, all community members are encouraged to participate with this group of volunteers in providing feedback and ideas for the agenda and theme. To monitor all event planning please watch this Wiki page (http://wiki.openstack.org/Summit/Spring2011) as well as the following three EtherPads:

I am also announcing that we have signed the contract with the Hyatt Santa Clara hotel for the event from April 26-29, 2011 and have obtained a discounted room rate for attendees with a room block. Please plan on staying at the hotel during the event as we will have a 24 hour lounge available for attendees to meet and work together as well as plenty of time for community members to hang out. If you are budget minded, we can also setup a room sharing program to ensure attendees can take part in this 24/7 event.

Back to top