Tag: community


Openstack at barcamp XII, Bangalore, India.

August 31st, 2012 — 12:35am

Barcamp, Bangalore was organized on 25th  august and we had registered for a talk on Openstack. Our talk got scheduled for later in the day. Barcamp is a unconf style event so after meeting few other Openstack contributors from HP and others, we decided lets keep the session more of a QA and whiteboard centric than slide centric. So me  Sajid and Yogesh joined for the session.  :)

The session was attended by over 30 people and after 25 minutes basic intro about whole Openstack project, we ended up spending rest of our time in QA session. There were wide range of questions related to data center deployment with Openstack to start-up venturing to project. There were also some questions like how freshers can build there career while contributing to Openstack.

Overall i would say it was great to have a session at barcamp, thanks to the organizers put putting up such awesome event. Some of the folks we met were looking forward to attend our Openstack monthly meetup in Banglore. We will be announcing the date and venue soon. :)

 

Comment » | Communication, community

Meeting To Discuss Next OpenStack Conference And Summit

June 14th, 2012 — 1:50pm

It’s never too late to get started, especially with a complex series of event like the OpenStack Summit and Conference. We’ve received the results of the survey after the past event in April in San Francisco and we want to keep the conversation open with the community.

All people interested in the next OpenStack Summit and Conference, especially former sponsors and coordinators of tracks in past events, are invited to register for the meeting OpenStack Summit & Conference Fall 2012 Planning,  next Tuesday, June 19 at 10:00 AM CDT. It will be the right time and place to discuss the challenges faced as the events have grown, and potential changes to the format to address them going forward.

Update: read the results of this meeting on OpenStack Summit coming October 15th-19th to San Diego, CA

Comment » | Communication, community, Event, Webinar

Announcing OpenStack Asia/Pacific Conference 2012

June 13th, 2012 — 7:02pm

We talked about during the community sessions at past OpenStack Design Summit, we’re now ready to announce it officially: the Asia/Pacific community is hosting a large OpenStack conference. Mark your calendar: August 10th and 11th, with a main venue in Bejing and a remote participation in Shanghai, hosted by the Chinese OpenStack User Group (COSUG) and CSDN, supervised by CSIP.

OpenStack developers and companies building products based on OpenStack from Asia Pacific Economic Cooperation will meet to present their solutions and to plan ways of working together on promoting OpenStack in local enterprises and industries.

There is still space available to sponsor the event: thousands of users from the region are expected. Interested companies can browse the sponsorship prospectus and pick the best options for their budget.

Speakers are welcome to submit their speaking proposal, also in English.

If you want to help with the organization of the event you can still join the OpenStack APEC community group. You can also follow: @CSDN and @CSDN Cloud Computing for updates in Chinese.

Comment » | Communication, community, Event

OpenStack Community Weekly Newsletter (June 1-8)

June 8th, 2012 — 2:01pm

OpenStack Community Newsletter — June 8

Highlights of the week

The results of Bug Triage Day are in

Nova has more bugs than all the other core projects combined, and the most slack to clean up. We went from 237 “New” bugs at the beginning of the day and down to 42, a completion rate of 82%. In the mean time we managed to close permanently 86 open bugs over a total of 627 [more, with charts]

Zuul: a Pipelining Trunk Gating System

The OpenStack Infra team has released a new tool to improve the trunk gating system. Zuul is a program that performs speculative execution of tests.  By constructing a virtual queue of changes based on the order of their approval, it runs jobs in parallel assuming they will all be successful.  If any of them fail, then any jobs that were run based on the assumption they succeeded are re-run without the problematic changes included.  This means that in the best case, as many changes can be tested and merged in parallel as computing resources will allow for testing.  And of course, with cloud computing, that isn’t much of a hurdle.

OpenStack Blog Authors Code Of Conduct

With the current number of authors on the community blog there is a need to have a clear understanding of what it means to have an account on such visible community asset. There is always time to send your comments.

A good list of opportunites for Industry Conferences & Sponsorship

And the next OpenStack Conference and Summit on October 16-20 (destination TBD).

Recent changes to wiki

  • Quantum V2 APIIntro quick intro to v.2.0 API for Quantum developers already familiar with the v1.0 and v1.1 API
  • StartingPage now showing a new video every month
  • Quantum Starter Bugs These are bugs that folks new to Quantum might want to pick off as an introduction

New version of gerrit – with new features!

Based on the new upstream version 2.4, but in addition we’ve landed two additional features on top of that – so there’s tons of new toys to play with.

Forking an OpenStack project to remotely save changes

Find on this thread the answer to the question: If you have a relatively long-lived topic branch, what’s the best way to remotely save changes?

Reports from past OpenStack events

Upcoming Events

 Other news

Welcome new contributors

Celebrating the first patches submitted this week by:

  • Zhiteng Huang, Intel
  • Vincent Untz, Suse

 

  The 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 leave a comment.

Comment » | Communication, community, Newsletter

OpenStack Blog Authors Code Of Conduct

June 7th, 2012 — 12:09pm

With the current number of authors on the community blog I think it’s a good idea to make sure we all have a clear understanding of what it means to have an account on such visible community asset. I think it would be good for the whole community to have a brief, clear, understandable code of conduct for all existing authors and for the future ones. We discussed on our community team and we came up with the OpenStack Blog Authors Code Of Conduct below.  We’ll publish this together with other community policies (like the OpenStack Event policy) in the next days: add your comments below or send them to the community team.

OpenStack.org Blog is the asset owned by the community and a platform where to share thoughts, ideas, reports and news about OpenStack. All the authors of blog posts have the responsibility to respect this common space while being grateful for the opportunity it represents. As a writer you should write articles respecting other’s opinions, even if you disagree. The OpenStack Community will benefit from sharing, debating and reflecting rather than discounting and disparaging others’ thoughts. Remember that as an author of OpenStack.org blog, the community trusts you to give voice to the community as a whole.

Writers accept these simple principles:

  • Prefer facts to opinions: be always aware that what you publish will be read by thousands of people and that your opinion is not necessarily that of the whole community. Try to stick to facts, like reporting the result of a meeting, announcing upcoming community events, describing technical achievements.
  • Disclose, don’t promote: it’s good to let people know that a company is contributing to OpenStack, sponsoring an event and such but the OpenStack.org Blog is not the place to publish a company’s press release or other type of commercial offering message.
  • Contribute to the commons: our blog is licensed under the terms of Creative Commons Attribution Share-alike version 3 unported. Pay attention to the license of any material you add to the blog, make sure it’s released under compatible terms.

Comment » | Communication, community, Governance

Starter docs and articles

May 21st, 2012 — 1:44pm

I wanted to send a note out to discuss the growth of all the starter docs and “articles” on a particular topic. Thanks all who are sending these as links to the mailing list or tweeting ‘em. We are listening.

The doc team has been discussing ways to ensure we help people find what they seek while still getting high-quality content into the “official” documentation. Here are some ideas. I’d like to get input from our wider community as well.

What we’re doing:

  • Add a “Where do I start?” section to the docs landing page. Let us know what you think of this approach by taking a look at the pending review. We discussed quite a bit a more friendly approach to the docs site but I haven’t identified a web dev and designer to do the re-do, contact me if you’re interested.
  • Reach out to writers and where licensing allows and something “official” is not already documented, bring the content into the official docs. We’ve done this a few times now, an example is how to custom brand the OpenStack Dashboard.
  • Add link to helpful blog entries to a “BloggersTips” wiki page.
  • Expand the install/deploy guide to include more distros so the “single distro” guides can standalone. This effort is still a work in progress.
  • Hastexo has offered to write a separate high availability (HA) guide, so we won’t bring in their 12.04 “all in one” install guide after all, since the CSS OSS Starter Guide covers a similar scenario.
  • Remove “articles” from RST docs. (Currently nova only, in further discussion with the Project Technical Leads, QA and CI team leads.)
  • Add blog URLs to the Google Custom Search Engine at http://docs.openstack.org. I took this as an action item from our last doc team meeting.

What we’ve discussed:

  • Removing redundant docs. At the Design Summit, members of the nova core team asked for removal of “article” style RST documents from the nova source repo, creating a more doc-string based nova.openstack.org. Members of the swift core team, when asked, did not want to go to this architecture. I haven’t specifically asked all the PTLs on this particular item. So there’s still a potential problem here of consistency, where to write what, and having all the project.openstack.org sites that aren’t really tied together. I don’t have a good solution to suggest just yet but know we’re thinking about this particular problem. One idea was to have devs who want to write compose WordPress “articles” and that would aggregate together, but we haven’t found an ideal implementation (design is fine, working code, not so much).
  • Setting up a separate WordPress blog for documentation only. Apparently the aggregation tools just don’t give us all the requirements for version labels, bringing in one blog entry at a time (RSS feeds are needed), and so on.
  • Setting up a “support knowledge base” article site such as http://support.mozilla.org. We discussed this at the last doc team meeting. It seems to solve a lot of problems we have, but my current thinking (which of course can change) is that a support KB is for troubleshooting articles, while the “official” docs should create a happy path. These are two different scenarios, and I’m pretty sure the docs team cannot take on the support scenario with our current resources. A support knowledge base with translation built-in will go a long way in supporting our growing base, so this is important to me, but not in the Folsom plans currently.

I’ll follow up with each PTL for the docstring discussion, and welcome all input. Thanks for reading this far, and thanks for the docs. Now get started!

Starting line

Comment » | community, Development, Documentation

Community Weekly Review (Apr 20-27)

April 27th, 2012 — 4:50pm

OpenStack Community Newsletter – April 27, 2012

Welcome back to our regular publishing schedule. This week we still hear the echo of the Design Summit and Conference.

HIGHLIGHTS

Upcoming Events

Other news

Community Statistics

This week’s chart shows the geographical dispersion of participants to Folsom series of events in San Francisco. The information is derived from the work address provided by participants when they registered. Participants from USA were the large majority, around 70% of the over 1,000 participants, nonetheless it’s interesting to look at the distribution once the outlier is removed.

Participants to Folsom Design Summit and Conference, per nation (excluding USA)

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 leave a comment.

1 comment » | Communication, community, Newsletter

Community Weekly Review (Mar 16-23)

March 23rd, 2012 — 5:00pm

OpenStack Community Newsletter –March 23, 2012

A great community story:

Over the course of just a week I’ve gone from despair and frustration to almost wanting to shout from the rooftops the achievements that have been made in OpenStack and my own deployments and testing

Read the rest of it on https://lists.launchpad.net/openstack/msg08950.html

HIGHLIGHTS

EVENTS

OTHER NEWS

COMMUNITY STATISTICS

  •  Activity on the main branch of OpenStack repositories, lines of code added and removed per developer during week 7 of 2012 (from Mon Mar 5 00:00:00 UTC 2012 to Mon March 12 00:00:00 UTC 2012)

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 leave a comment.

Comment » | Communication, community, Newsletter

OpenStack Governance Elections Spring 2012: Time to vote!

February 27th, 2012 — 7:41pm

UPDATE: PPB election update: we need to reboot the voting process. Please accept our apology. Read more on http://ow.ly/9lNGf

The OpenStack community is called to elect the Project Technical Leads and two seats of the Project Policy Board. The nominations process is now officially closed and voting can start: all entitled to vote will receive a personal message via email on February 28 and have time until March 3 11:59 PST to vote. The email message will go to the email address included in the Authors file and the one provided during the registration for PPB votes.

The official list of nominees (in random order) is the following:

NOVA Project Technical Lead (1 position)

KEYSTONE Project Technical Lead (1 position)

HORIZON Project Technical Lead (1 position)

SWIFT Project Technical Lead (1 position)

GLANCE Project Technical Lead (1 position)

PROJECT POLICY BOARD (2 positions)

Voting process

Like previous OpenStack Governance Elections, we will use the Condorcet Internet Voting Service from Cornell University, 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.

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. Voter anonymity is guaranteed.  The result’s ranking will be evaluated using Schulze (also known as Beatpath or CSSD) completion rule. 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 in  the most recent election.  Thanks for participating in this essential process.

The election committee is made of Stefano Maffulli, Lloyd Dewolf and Dave Nielsen.

Comment » | community, Governance

OpenStack Governance Elections Spring 2012: Action Item For All Candidates

February 22nd, 2012 — 11:52pm

The OpenStack community is electing its Project Technical Leads and two members of the Project Policy Board. Details are at http://www.openstack.org/blog/2012/02/openstack-governance-elections-spring-2012/. On February 26 the nominations will close and the voting process will start on February 28 and finish on March 3rd.

The list of nominees is at http://etherpad.openstack.org/Spring2012-Nominees. It’s still open. You must register to vote for PPB on http://ppbelectionsregistration.openstack.org/

Before the voting process starts the election committee asks all nominees to create a page on OpenStack wiki and answer three simple questions:

1a. [for PPB] Since the last elections, what areas have you focused on and what contributions have you made in order to improve OpenStack as a whole?

1b. [for PTL] Since the last elections, what areas have you focused on and what contributions have you made in order to improve your project?

2a. [for PPB] What are the most pressing/important issues facing OpenStack as a whole?

2b. [for PTL] What are the most pressing/important issues facing your project?

3. What is your relationship to OpenStack & why is its success important to you and/or your company?

If you’re a candidate, create a wiki page using the template http://wiki.openstack.org/Governance/ElectionsSpring2012/[Firstname_Lastname] and answer those questions there. Feel free to add more content, too. Those pages will be included in the link sent to all voters.

The election committee is made of Stefano Maffulli, Lloyd Dewolf and Dave Nielsen.

Comment » | Communication, community, Governance

Back to top