{"id":4746,"date":"2013-07-16T13:39:27","date_gmt":"2013-07-16T18:39:27","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=4746"},"modified":"2013-07-16T14:55:45","modified_gmt":"2013-07-16T19:55:45","slug":"infrastructure-bootcamp","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/infrastructure-bootcamp\/","title":{"rendered":"Infrastructure Bootcamp"},"content":{"rendered":"

Recently the Project Infrastructure team hosted a two-day “bootcamp”
\nfor people who are interested in contributing to the Project
\nInfrastructure. \u00a0The OpenStack project is so large, and continuing to
\ngrow, that creating and operating the developer infrastructure for the
\nproject itself is a unique challenge. \u00a0Because OpenStack receives code
\ncontributions from more than 600 developers in a release cycle, and
\nmerges as many as 200 changes per day, we are at the cutting edge of
\ndistributed development and testing.<\/p>\n

The project infrastructure covers a wide range of tools and services
\nused by the project, including code review, testing, and
\ncollaboration. \u00a0The design and operation of these systems is managed
\nunder the Infrastructure Program which is overseen by the TC just like
\nthe rest of the OpenStack project. \u00a0And like any other OpenStack
\nprogram, our team is open and we welcome contributions from anyone.<\/p>\n

Managing the infrastructure for a project of this scale is a lot of
\nwork, but it is uniquely rewarding because it affects every OpenStack
\nproject and affords interactions with all of the developers. \u00a0We heard
\na lot of interest from persons and companies who wanted to contribute,
\nso we held the bootcamp to get anyone who was interested in
\ncontributing together in a room with the current core team of
\ninfrastructure developers.<\/p>\n

\"OpenStack<\/a>

OpenStack Infrastructure Bootcamp kicks off
Photo: Elizabeth Krumbach, CC-BY 2.0<\/p><\/div>\n

Day one saw us all together and discussing how contributions are
\naccepted, how the team operates, and how new members can expect to
\nbecome core members in the future. \u00a0We discussed each major system at
\na high level, and worked out how all of the systems interact with each
\nother.<\/p>\n

In the evening, we all got together for dinner and spent several
\nenjoyable hours talking about how we could improve the system, and
\ngenerally getting to know each other.<\/p>\n

On day two, we dove deeper into some topics of particular interest to
\nattendees, and generally had a less structured approach where people
\nwho shared interest in an area got together and discussed it in depth.<\/p>\n

I think everyone who attended got a lot out of the event, and we’re
\nalready seeing significant new contributions as a result. \u00a0I hope that
\nin several months more time we will have new core members on our
\nteam. \u00a0I also think this is a good model for other programs in
\nOpenStack who want to quickly bring new contributors up to speed.<\/p>\n

I’d like to thank Monty Taylor for organizing the event, the rest of
\nthe core contributors (or “coremudgeons”) for talking about what we do
\nfor two days straight, and Hewlett-Packard and the OpenStack
\nFoundation for sponsoring the event.<\/p>\n

Some reactions from others who attended:
\nhttp:\/\/dague.net\/2013\/06\/29\/openstack-infrastructure-bootcamp\/<\/a>
\nhttp:\/\/princessleia.com\/journal\/?p=8229<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Recently the Project Infrastructure team hosted a two-day “bootcamp” for people who are interested in contributing to the Project Infrastructure. \u00a0The OpenStack project is so large, and continuing to grow, that creating and operating the developer infrastructure for the project itself is a unique challenge. \u00a0Because OpenStack receives code contributions from more than 600 developers… Read more »<\/a><\/p>\n","protected":false},"author":56,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[21,9,4,1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/4746"}],"collection":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/users\/56"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=4746"}],"version-history":[{"count":7,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/4746\/revisions"}],"predecessor-version":[{"id":4750,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/4746\/revisions\/4750"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=4746"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=4746"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=4746"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}