For those of you wanting to learn more about the Dashboard, I give you a video by Anthony Young:
Anthony Young of Rackspace Cloud Builders demos the OpenStack Dashboard from OpenStack on Vimeo.
For those of you wanting to learn more about the Dashboard, I give you a video by Anthony Young:
Anthony Young of Rackspace Cloud Builders demos the OpenStack Dashboard from OpenStack on Vimeo.
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 !
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:
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:
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.
Another video from Santa Clara Meetup:
OpenStack Lightning Talks: Andrew Shafer, Cloudscaling from OpenStack on Vimeo.
More videos from OpenStack Santa Clara Meetup:
OpenStack Lightning Talks: Sebastian Stadil, Scalr from OpenStack on Vimeo.
More videos from the Santa Clara Meetup:
OpenStack Lightning Talks: Vish Ishaya & Devin Carlen, Anso Labs from OpenStack on Vimeo.
Many people have asked for more insight into the developer activities for OpenStack as the large number of code changes and proposals make it difficult to monitor everything happening. In hopes of exposing more of the developer activities, I plan to post a weekly or biweekly blog post on the latest development activities. If you have any ideas for this blog post, please email me at [email protected]. I am always ready to listen to the community for new ideas.
Activities
Developer Mailing List (archive: https://lists.launchpad.net/openstack/)
This is select list of topics discussed this week in the developer mailing list and is not a complete list. Please visit the archive to see all the topics.
Statistics
For the latest on development activities on OpenStack please check these sites for more details:
OpenStack Community Newsletter – March 4, 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].
Midokura booth at Cloud Days in Tokyo
HIGHLIGHTS
EVENTS
DEVELOPER COMMUNITY
GENERAL COMMUNITY
COMMUNITY STATISTICS (2/25– 3/3)
OPENSTACK IN THE NEWS
Anne Gentle at the Santa Clara, CA Meetup on February 3, 2011
OpenStack Lightning Talks: Anne Gentle, Constant Stacker from OpenStack on Vimeo.
As we take stock of the amazing interest and growth, keeping in mind the initiative’s goals and commitment to openness, the time has come to evolve the governance process to match the new reality of a larger, more diverse community. To that end, the governance process has been updated, with full details published here.
As you read through the highlights below, we encourage you to get personally involved to steer this community to an even bigger, brighter future. Whether it’s participating in a spirited debate on the mailing list, attending the bi-annual design summits, or even running for one of the elected positions, there are a lot of ways to get involved and there’s no time like the present to dive in. Nominations and elections will be held later this month for many elected positions.
Highlights:
*Upcoming Elections: As noted above, a total of 5 seats are up for election later this month, March 2011, prior to the Spring 2011 Design Summit. 3 of these will be Project Technical Leads for the respective projects, and will also sit on the Project Policy Board representing those respective communities, and 2 will be General Board Members. More details soon regarding the nomination and election process.
Again, we invite everyone to get involved and have your voice heard. If you’re interested in running for the Project Policy Board, or becoming a Project Technical Leader, now’s the time to throw your hat in the ring. Registration for the second public Design Summit will open in the next few days, in which members of the community set the roadmap and make technical decisions to drive the projects forward. You can get plugged in with our new community page at openstack.org/community.