Tag: atlanta


OpenStack Upstream Training in Atlanta A Big Success

May 11th, 2014 — 4:33pm

The first edition of OpenStack Upstream Training completed today in Atlanta: the class made of software developers from around the world, started learning technical and social convention of one of the largest open source collaboration project. During the first day, twenty people picked a real bug or feature to work on, got their development environment setup, signed the CLAs and made the first attempts at committing and reviewing patches. After getting the ‘hard’ technical skills sharpened, the second day of training was all about learning the ‘soft’, social skills necessary to collaborate with a massive amount of people across the continents.

If you saw pictures of legos on twitter tagged #openstack, you have seen images of the OpenStack City role playing game. The students were split in three groups and starts with a city partially built, with a rough master plan for expansion. One group of students acts as the rulers of the city, another group acts as new contributor and the third group acts as the Product Manager of the new contributors. The role game is a nice way to practice the suggestions of the morning. on how to communicate intentions, execute on ideas, interact with other people working on OpenStack components.

With many years of practise contributing to many free software projects, Loic Dachary kindly donated his time to the OpenStack Foundation to lead the training, adapting the content of Upstream University to the specific needs of OpenStack. The class gives strong emphasis on the soft skills necessary to speed up acceptance of contributions. We noticed that over the years, a lot of new contributors, especially occasional ones, don’t have enough exposure to the big picture of OpenStack and these are more likely to be frustrated by the complex set of tools, processes, people between a bug fixed on a local branch and code accepted upstream. Based on the feedback gathered, this first set of graduates from OpenStack Upstream Training will surely get a pleasant experience. Hopefully they’ll keep growing inside OpenStack community and help future first time contributors.

The group is the first set of graduates of OpenStack Upstream Training: David BinghamBob Bennett, Daneyon HansenJacki Bauer, Gangadhar Singh, Om KumarTim FreundRichard ColemanJerry Xinyu Zhao, Sam Su, Shuichiro MakigakiJunichi MatayoshiDerek AndersonDave Fogelson, Ryo KurahashiRajeev GroverSrinivasa AcharyaVishal Thapar, Rashmi, Rohit, Jack Mac. When you meet them this week, please thank them for the time they dedicated to the project and consider them a beautiful present. I, Loic and other mentors will keep meeting online with them in the next weeks, until their chosen contribution will be merged.Thanks to all participants, Loic and Sahid Orentino Ferdjaoui, Édouard Thuleau, Chris Ricker for assisting.

We hope to replicate the training in Paris: stay tuned for the details soon.

Comment » | Communication, community, Development, Event

Call for Proposals Open Source @ OpenStack Summit

March 31st, 2014 — 6:25am

UPDATE: Friday, April 18 is the deadline for submissions. 

At this year’s OpenStack Summit we’re going to be offering space to Open Source projects that are important to the OpenStack community. We’re calling it Open Source @ OpenStack, and it’s an opportunity for these projects to hold small design summits with their community members. We’re impressed by the number of projects that have grown in the OpenStack ecosystem, and want to continue the practice we started with StackForge of fostering these projects.

We have space and time available for half day sessions on Tuesday and Wednesday, both morning and afternoon. The purpose of the space is to get developers in the same room so they can plan their development for the Juno release cycle. Rather than being a time to market a particular company or technology, it should be an opportunity communication and goal setting. To achieve these goals, we would like participating projects to use the following guidelines:

  • The project needs to be directly related to OpenStack in some way.
  • The project must be open source, with source code available and actively developed.
  • The work needs to be non-commercial and vendor neutral, although a vendor that sponsors a project can organize the meeting.
  • Sessions must be open to anyone who wants to attend. This should be not just an opportunity for core developers to meet, but to also give a venue for people interested in your project to get more information.
  • Meeting notes from the design session should be made publicly available.
  • The group organizers and participants must adhere to the OpenStack Summit Code of Conduct.

If you have a project that you think qualifies for this space, we invite you to submit a proposal for Open Source @ OpenStack. Update: Friday, April 18 is the deadline for submissions. 

Please include:

  • The name of your project.
  • A description of the project and how it relates to OpenStack.
  • The names and contact information for the organizers commiting to hosting the session.
  • Relevant links to project sites such as repositories, bug trackers, and documentation.
  • An estimate of the number of developers you expect to attend your design meeting.
  • A plan for how you intend to use the time and space.

We want to thank everyone for the time and effort they put into supporting OpenStack.

Comment » | Communication, community, Development, Event

OpenStack Community Weekly Newsletter (Jan 31 – Feb 7)

February 7th, 2014 — 10:23am

Defining OpenStack “Core”

Quite a lot of debates online and not around the DefCore initiative, triggered by a message by Thierry Carrez with comments from Mark McLoughlin, Nick Barcet, Troy Toman, Dan Wendlandt, Mark Collier, Tim Bell, Eric Windisch, Boris Renski, Pete Chadwik, Randy Bias, and others.

StoryBoard sprint in Brussels

StoryBoard is a project Thierry Carrez started a few months ago. Quite a few people in OpenStack have been running into a number of issues with Launchpad (inability to have blueprints spanning multiple code bases, inability to have flexible project group views, inability to use non-Launchpad OpenID for login…), and were investigating replacements. Tired of explaining why existing alternatives wouldn’t work for OpenStack task management, Thierry ended up writing a proof-of-concept to show a practical example. That proof-of-concept was sufficiently compelling that the Infrastructure team decided we should write our own tool.

The road to Juno Summit – Atlanta 2014

  • Have you redeemed your invite code yet? Do it now! Check your inbox and spam folder if you contributed code before January 25 for yours.
  • Next batch of invites will be sent regularly after each milestone until feature freeze.
  • The call for speakers is open: submit your proposal by Feb 14.
  • Applications for Travel Support Program. Apply by Mar 2.

Tips ‘n Tricks

Reports from Previous Events

Upcoming Events

Popular OpenStack Videos of the Week

Got Answers?

Ask OpenStack is the go-to destination for OpenStack users. Interesting questions waiting for answers:

Other News

Welcome New Reviewers and Developers

Is your affiliation correct? Check your profile in the OpenStack Foundation Members Database!

Wei Wang haruka tanizawa
Lukas Bednar Wei Wang
Joanna Huang Facundo Farias
Bertrand Lallau Esperanza Romero
Andrew Kerr Kirill Izotov
Ryan McNair Aneesh Puliyedath Udumbath
Martin Lopes Ruslan Kiianchuk
Donald Dugger Roland Hochmuth
Don Talton Ihor Stehantsev
Ren Qiaowei Tim Landscheidt
Matthew Gilliard Malini Kamalambal
Ronak Shah Nicolas PLANEL
Jay Lee

Latest Activity In Projects

Do you want to see at a glance the bugs filed and solved this week? Latest patches submitted for review? Check out the individual project pages on OpenStack Activity Board – Insights.

OpenStack Reactions

fail-period

submitting a patch that passes Python tests, but realizing jenkins failed you because the commit message has a period at the end

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, Event, Newsletter

Back to top