Open Stack

This is wonderful, Jim. Thank you. It is just what I was looking for to
help structure some of my own focus to allow for meaningful upstream
contributions to all the tools you pointed to. I'll cross fingers for
additional notes and documentation to come out of the bootcamp that will
help those of us not able to send developers right now still make a
meaningful impact to your 6 month "grow the review team" goal.

Have a great day, all.

Rainya Mosher
Software Dev Manager ­ Compute Deploy Infrastructure
210.316.5065 (mobile)
Communication € Strategic € Maximizer € Individualization € Activator
Not all of us can save the world. Some of us need to make it worth saving.
- RFM





On 6/10/13 12:45 PM, "James E. Blair" <corvus at inaugust.com> wrote:

>Rainya Mosher <rainya.mosher at RACKSPACE.COM> writes:
>
>> hihi all and particularly Monty & Jim,
>>
>> Is this bootcamp planned to be a pure hackday-format for high-code
>> contributors or is it more about process and setting up "how tos" for
>> newbies to the organization? Or a combination? I am very curious about
>> what outputs we expect to see for those that can make it to NYC and
>>those
>> that will not be able to attend. If it is "just" for hacking on code,
>>that
>> is great, but anything that can be done can do in terms of documenting
>> processes and best practices and how to enter the Infra team would be
>> beneficial (in my opinion.)
>
>Hi!
>
>The goal is to get new core contributors to the infra team, long term.
>So it's not a typical sprint where we measure the success in code output
>-- we might write some code, but that's incidental.  This is more of a
>"boot camp".  Real success will be measured by whether, in 6 months,
>we've managed to grow the team of infrastructure core reviewers.
>
>We're an extremely active project but our ratio of core reviewers to
>changes is much smaller than other OpenStack projects.  Some of the
>stuff we do is rather complicated, and it's hard for new people to pick
>it all up, or even know where to start sometimes.  So we're going to
>invest some time in helping people who can commit serious time to the
>infrastructure team get up to speed so that they can start making
>significant contributions soon, both as contributors and reviewers, and
>hopefully become core team members in the future, or at least regular
>and substantial contributors.
>
>You know we're trying to run the most open project infrastructure we
>can, and any contribution is always welcome.  However, at this
>particular event, we don't want to focus on enabling casual
>contributions.  We really want people who can at least work half-time on
>pure upstream OpenStack project needs.  That means working on things
>that affect the whole project, not just an employer's area of interest.
>People who can help maintain Gerrit, Zuul, Jenkins, Etherpad, IRC bots,
>Mailman, Logstash, Devstack-gate, etc.  I believe that kind of broad
>focus is needed to become a core member of the infrastructure team.
>
>I hope that helps you understand what we want to accomplish at this
>event.
>
>As another part of this effort, I have recently restructured the
>infrastructure documentation:
>
>  http://ci.openstack.org/
>
>Its focus is now to help new contributors (both casual and long-term) to
>any of the infrastructure sub-projects.  It describes the operation of
>the project and team, how to make and test changes, and gives an
>overview with resources for each of the major systems we manage.  It's
>_far_ from complete, but I hope the course is now set and we can
>continue on that heading.
>
>-Jim