OpenStack - User contributions [en]

Akanda

2015-09-16T16:08:38Z

Dachary: fix the link to the codebase

Docs http://docs.akanda.io/en/latest/
Past IRC Meetings http://eavesdrop.openstack.org/meetings/akanda
[https://review.openstack.org/#/q/status:open+project:stackforge/akanda-appliance+OR+project:stackforge/akanda-appliance+OR+project:stackforge/akanda-appliance-builder+OR+project:stackforge/akanda-rug+OR+project:stackforge/akanda-horizon+OR+project:stackforge/akanda-neutron,n,z Patches in review]
Code series https://launchpad.net/akanda
Codebase https://github.com/stackforge/akanda
Meeting agenda https://wiki.openstack.org/wiki/Meetings/akanda

= What Is Akanda =
Akanda is the only open source network virtualization solution built by OpenStack
operators for real OpenStack clouds. Akanda eliminates the need for complex SDN
controllers, overlays and multiple plugins for cloud networking by providing a
simple integrated networking stack (routing, firewall, load balancing) for
connecting and securing multi-tenant OpenStack environments.

Akanda is layer 2 agnostic and interfaces with the OpenStack Neutron REST APIs.
Akanda includes a sophisticated lifecycle management and orchestration platform
to monitor, configure, and manage 3rd party virtualized routers, load balancers
and firewalls.

The Name - Project names are a powerful tool because they can be used to bond teams,
communicate effectively and convey the end goal. Like many projects, we
considered many names until a member of our team sought out to find a word
appropriate for an open project. This word enables us to say something more
clearly and with a bevy of excellent synonyms by using the Sanskrit word
अखण्ड (akhaNDa) which has such lovely connotations as "non-stop, "undivided,
"entire," "whole," and most importantly, "**not broken**."

= Installing Akanda =
* Using source http://docs.akanda.io/en/latest/operation.html#installation
* Using devstack http://docs.akanda.io/en/latest/developer_quickstart.html#deploying-akanda-using-devstack

= Operating Akanda =
Rug ctl commands http://docs.akanda.io/en/latest/operation.html#id1

= Akanda Development Plans =
Akanda is only open source and OpenStack. We have only have code in https://git.openstack.org. From our Liberty Summit development plans here https://etherpad.openstack.org/p/liberty-akanda-design, the Akanda project is working towards supporting more OpenStack Neutron Advanced services, more stability, better performance, and better OpenStack code integration. All the details of our plans are outlined in our blueprints and specs that can be found here https://blueprints.launchpad.net/akanda.

OpenStack Upstream Training/Info

2014-10-31T13:29:52Z

Dachary: add kilo etherpad links

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Juno_Release_Schedule Juno release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=juno&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=juno&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals (bottom of the page)
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** [https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads Kilo Summit Etherpads]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (1 hour) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/20-training-agile-for-contributors.rst slides] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (2 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp odp slides] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf pdf slides] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

=== Etherpad ===

https://etherpad.openstack.org/p/kilo-upstream-training

</translate>

OpenStack Upstream Training/Info

2014-10-31T13:23:39Z

Dachary: update to juno stackalitics

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Juno_Release_Schedule Juno release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=juno&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=juno&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals (bottom of the page)
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (1 hour) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/20-training-agile-for-contributors.rst slides] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (2 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp odp slides] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf pdf slides] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

=== Etherpad ===

https://etherpad.openstack.org/p/kilo-upstream-training

</translate>

OpenStack Upstream Training/Info

2014-10-31T13:19:38Z

Dachary: /* How OpenStack is made (3h including 1h30 exercises) */

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Juno_Release_Schedule Juno release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (1 hour) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/20-training-agile-for-contributors.rst slides] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (2 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp odp slides] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf pdf slides] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

=== Etherpad ===

https://etherpad.openstack.org/p/kilo-upstream-training

</translate>

OpenStack Upstream Training/Info

2014-10-31T11:48:27Z

Dachary: /* Contribution Simulation (1 hour) */

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (1 hour) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/20-training-agile-for-contributors.rst slides] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (2 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp odp slides] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf pdf slides] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

=== Etherpad ===

https://etherpad.openstack.org/p/kilo-upstream-training

</translate>

OpenStack Upstream Training/Info

2014-10-31T11:45:14Z

Dachary: /* The Contribution Process (3 hours) */

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (1 hour) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/20-training-agile-for-contributors.rst slides] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp odp slides] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf pdf slides] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

=== Etherpad ===

https://etherpad.openstack.org/p/kilo-upstream-training

</translate>

OpenStack Upstream Training/Info

2014-10-31T10:47:47Z

Dachary: link to the pad

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/20-training-agile-for-contributors.rst slides] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp odp slides] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf pdf slides] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

=== Etherpad ===

https://etherpad.openstack.org/p/kilo-upstream-training

</translate>

OpenStack Upstream Training/Info

2014-10-28T06:10:27Z

Dachary: add labels to contribution planning slides

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/20-training-agile-for-contributors.rst slides] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp odp slides] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf pdf slides] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class
</translate>

OpenStack Upstream Training/Info

2014-10-28T06:09:06Z

Dachary: update links to slides to point to https://github.com/openstack/training-guides/

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/20-training-agile-for-contributors.rst slides] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class
</translate>

OpenStack Upstream Training/Info

2014-10-28T06:08:24Z

Dachary: update links to slides to point to https://github.com/openstack/training-guides/

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/19-training-contribution-process.rst slides] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [http://dachary.org/loic/openstack-training/training-agile-for-contributors.odp] [http://dachary.org/loic/openstack-training/training-agile-for-contributors.pdf] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class
</translate>

OpenStack Upstream Training/Info

2014-10-28T06:07:12Z

Dachary: update links to slides to point to https://github.com/openstack/training-guides/

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/11-devstack.rst slides] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/12-howtocontribute.rst slides] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/13-launchpad.rst slides] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/14-gerrit.rst slides] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/15-branching-model.rst slides] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/16-reviewing.rst slides] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/17-commit-message.rst slides] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/18-jenkins.rst slides] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [http://dachary.org/loic/openstack-training/training-contribution-process.odp] [http://dachary.org/loic/openstack-training/training-contribution-process.pdf] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [http://dachary.org/loic/openstack-training/training-agile-for-contributors.odp] [http://dachary.org/loic/openstack-training/training-agile-for-contributors.pdf] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class
</translate>

OpenStack Upstream Training/Info

2014-10-28T06:02:47Z

Dachary: /* How OpenStack is made (3h including 1h30 exercises) */

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [http://dachary.org/loic/openstack-training/reviewing.odp slides.odp] [http://dachary.org/loic/openstack-training/reviewing.pdf slides.pdf] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [http://dachary.org/loic/openstack-training/training-contribution-process.odp] [http://dachary.org/loic/openstack-training/training-contribution-process.pdf] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [http://dachary.org/loic/openstack-training/training-agile-for-contributors.odp] [http://dachary.org/loic/openstack-training/training-agile-for-contributors.pdf] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class
</translate>

OpenStack Upstream Training/Info

2014-10-28T06:02:09Z

Dachary: /* How OpenStack is made (3h including 1h30 exercises) */

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [http://dachary.org/loic/openstack-training/reviewing.odp slides.odp] [http://dachary.org/loic/openstack-training/reviewing.pdf slides.pdf] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [http://dachary.org/loic/openstack-training/training-contribution-process.odp] [http://dachary.org/loic/openstack-training/training-contribution-process.pdf] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [http://dachary.org/loic/openstack-training/training-agile-for-contributors.odp] [http://dachary.org/loic/openstack-training/training-agile-for-contributors.pdf] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class
</translate>

OpenStack Upstream Training/Info

2014-10-28T06:01:10Z

Dachary: update links to slides to point to https://github.com/openstack/training-guides/

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/02-relevant-actors.rst slides] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/03-technical-committee.rst slides )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/04-program-ecosystem.rst slides] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/05-design-summit.rst slides )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/06-irc-meetings.rst slides] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [http://dachary.org/loic/openstack-training/reviewing.odp slides.odp] [http://dachary.org/loic/openstack-training/reviewing.pdf slides.pdf] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [http://dachary.org/loic/openstack-training/training-contribution-process.odp] [http://dachary.org/loic/openstack-training/training-contribution-process.pdf] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [http://dachary.org/loic/openstack-training/training-agile-for-contributors.odp] [http://dachary.org/loic/openstack-training/training-agile-for-contributors.pdf] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class
</translate>

OpenStack Upstream Training/Info

2014-10-28T05:57:37Z

Dachary: 01-release-cycle.rst links to slides

<translate>

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop

= Course Outline =

== First day ==

=== Introduction ===

* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/01-release-cycle.rst slides] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [http://dachary.org/loic/openstack-training/reviewing.odp slides.odp] [http://dachary.org/loic/openstack-training/reviewing.pdf slides.pdf] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [http://dachary.org/loic/openstack-training/training-contribution-process.odp] [http://dachary.org/loic/openstack-training/training-contribution-process.pdf] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [http://dachary.org/loic/openstack-training/training-agile-for-contributors.odp] [http://dachary.org/loic/openstack-training/training-agile-for-contributors.pdf] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class
</translate>

OpenStack Upstream Training/Info

2014-10-16T13:00:07Z

Dachary:

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

== Infrastructure ==

[[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop
= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [http://dachary.org/loic/openstack-training/reviewing.odp slides.odp] [http://dachary.org/loic/openstack-training/reviewing.pdf slides.pdf] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [http://dachary.org/loic/openstack-training/training-contribution-process.odp] [http://dachary.org/loic/openstack-training/training-contribution-process.pdf] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [http://dachary.org/loic/openstack-training/training-agile-for-contributors.odp] [http://dachary.org/loic/openstack-training/training-agile-for-contributors.pdf] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

OpenStack Upstream Training/Setup DevStack

2014-10-16T12:56:07Z

Dachary:

* Save the file below in $HOME/devstack_cloudinit.yaml
* nova boot --flavor 4GB-ram-10GB-disk --image "Ubuntu 14.04" --nic port-id=$PORT --key-name mykey --user-data $HOME/devstack_cloudinit.yaml test_devstack

<pre>
#cloud-config

package_update: true
package_upgrade: true
package_reboot_if_required: true

packages:
- git
- mc
- vim
- traceroute
- htop
- tmux
- nmap

ssh_pwauth: True

groups:
- stack

users:
- default
- name: stack
gecos: Foo User
primary-group: stack
groups: admin
plain_text_passwd: 'stack'
sudo: ALL=(ALL) NOPASSWD:ALL
lock-passwd: false
shell: /bin/bash

write_files:
- content: |
[[local|localrc]]
disable_service n-net
disable_service n-obj
disable_service tempest
disable_service cinder
disable_service c-api
disable_service c-vol
disable_service c-sch
#disable_service n-novnc
enable_service horizon
disable_service n-xvnc
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service neutron
#enable_service n-spice
enable_service n-vnc

ADMIN_PASSWORD=password
MYSQL_PASSWORD=password
RABBIT_PASSWORD=password
SERVICE_PASSWORD=password
SERVICE_TOKEN=tokentoken

ROOTSLEEP=0
RECLONE=True
#OFFLINE=True
DATA_DIR=$TOP_DIR/data
SCREEN_LOGDIR=$TOP_DIR/log
VERBOSE=False

MULTI_HOST=True
FIXED_RANGE=192.168.85.0/24

### NEUTRON ###
### ML2 plugin ###
ENABLE_TENANT_TUNNELS=True
Q_ML2_PLUGIN_MECHANISM_DRIVERS=linuxbridge
Q_AGENT=linuxbridge

Q_ML2_PLUGIN_TYPE_DRIVERS=flat,vlan,gre,vxlan

# Prevent L3 agent from using br-ex
PUBLIC_BRIDGE=

# L2 population
Q_ML2_PLUGIN_MECHANISM_DRIVERS=$Q_ML2_PLUGIN_MECHANISM_DRIVERS,l2population

[[post-config|$NOVA_CONF]]
[DEFAULT]
vnc_enabled=True
vnc_keymap=fr
vncserver_listen=0.0.0.0
vncserver_proxyclient_address=$HOST_IP
libvirt_inject_key = False
libvirt_inject_partition = -2

[[post-config|/$Q_PLUGIN_CONF_FILE]]
[ml2]
tenant_network_types=vxlan

[vxlan]
enable_vxlan=true
l2_population=True
local_ip=$HOST_IP

[linux_bridge]
physical_interface_mappings = public:eth0

[ml2_type_flat]
flat_networks = public

[ml2_type_vxlan]
vni_ranges = 1001:2000

[[post-config|/$Q_DHCP_CONF_FILE]]
[DEFAULT]
enable_isolated_metadata = True
dnsmasq_dns_server = 8.8.8.8
dnsmasq_config_file = /etc/dnsmasq.conf

[[post-config|/$Q_L3_CONF_FILE]]
[DEFAULT]
external_network_bridge = ""
path: /opt/local.conf
permissions: 0664
- content: |
#!/usr/bin/env bash

tmux new-session -s devstack -n shell -d
tmux new-window -t devstack:1 -n devstack
tmux send-keys -t devstack:1 'cd ~/devstack; ./stack.sh' C-m
tmux select-window -t devstack:1
path: /opt/run_devstack_into_tmux.sh
permissions: 0775

runcmd:
- [ sh, -xc, "echo '127.0.0.1 $(wget -q -O- http://169.254.169.254/latest/meta-data/hostname | cut -d . -f 1)'' >> /etc/hosts" ]
- [ sh, -xc, "su stack -c 'cd ~; git clone https://github.com/openstack-dev/devstack.git'" ]
- [ sh, -xc, "su stack -c 'cp /opt/local.conf ~/devstack/'" ]
- [ sh, -xc, "su stack -c 'bash /opt/run_devstack_into_tmux.sh'" ]

final_message: "!!! Your devstack is up and running. You can reach the OpenStack dashboard !!! (cloudinit runs in $UPTIME seconds)"
</pre>

OpenStack Upstream Training/Setup DevStack

2014-10-16T12:52:50Z

Dachary: devstack for cloudinit

* Save the file below in $HOME/devstack_cloudinit.yaml
* nova boot --flavor 4GB-ram-10GB-disk --image "Ubuntu 14.04" --nic port-id=$PORT --key-name mykey --user-data $HOME/devstack_cloudinit.yaml test_devstack

<nowiki>
#cloud-config

package_update: true
package_upgrade: true
package_reboot_if_required: true

packages:
- git
- mc
- vim
- traceroute
- htop
- tmux
- nmap

ssh_pwauth: True

groups:
- stack

users:
- default
- name: stack
gecos: Foo User
primary-group: stack
groups: admin
plain_text_passwd: 'stack'
sudo: ALL=(ALL) NOPASSWD:ALL
lock-passwd: false
shell: /bin/bash

write_files:
- content: |
[[local|localrc]]
disable_service n-net
disable_service n-obj
disable_service tempest
disable_service cinder
disable_service c-api
disable_service c-vol
disable_service c-sch
#disable_service n-novnc
enable_service horizon
disable_service n-xvnc
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service neutron
#enable_service n-spice
enable_service n-vnc

ADMIN_PASSWORD=password
MYSQL_PASSWORD=password
RABBIT_PASSWORD=password
SERVICE_PASSWORD=password
SERVICE_TOKEN=tokentoken

ROOTSLEEP=0
RECLONE=True
#OFFLINE=True
DATA_DIR=$TOP_DIR/data
SCREEN_LOGDIR=$TOP_DIR/log
VERBOSE=False

MULTI_HOST=True
FIXED_RANGE=192.168.85.0/24

### NEUTRON ###
### ML2 plugin ###
ENABLE_TENANT_TUNNELS=True
Q_ML2_PLUGIN_MECHANISM_DRIVERS=linuxbridge
Q_AGENT=linuxbridge

Q_ML2_PLUGIN_TYPE_DRIVERS=flat,vlan,gre,vxlan

# Prevent L3 agent from using br-ex
PUBLIC_BRIDGE=

# L2 population
Q_ML2_PLUGIN_MECHANISM_DRIVERS=$Q_ML2_PLUGIN_MECHANISM_DRIVERS,l2population

[[post-config|$NOVA_CONF]]
[DEFAULT]
vnc_enabled=True
vnc_keymap=fr
vncserver_listen=0.0.0.0
vncserver_proxyclient_address=$HOST_IP
libvirt_inject_key = False
libvirt_inject_partition = -2

[[post-config|/$Q_PLUGIN_CONF_FILE]]
[ml2]
tenant_network_types=vxlan

[vxlan]
enable_vxlan=true
l2_population=True
local_ip=$HOST_IP

[linux_bridge]
physical_interface_mappings = public:eth0

[ml2_type_flat]
flat_networks = public

[ml2_type_vxlan]
vni_ranges = 1001:2000

[[post-config|/$Q_DHCP_CONF_FILE]]
[DEFAULT]
enable_isolated_metadata = True
dnsmasq_dns_server = 8.8.8.8
dnsmasq_config_file = /etc/dnsmasq.conf

[[post-config|/$Q_L3_CONF_FILE]]
[DEFAULT]
external_network_bridge = ""
path: /opt/local.conf
permissions: 0664
- content: |
#!/usr/bin/env bash

tmux new-session -s devstack -n shell -d
tmux new-window -t devstack:1 -n devstack
tmux send-keys -t devstack:1 'cd ~/devstack; ./stack.sh' C-m
tmux select-window -t devstack:1
path: /opt/run_devstack_into_tmux.sh
permissions: 0775

runcmd:
- [ sh, -xc, "echo '127.0.0.1 $(wget -q -O- http://169.254.169.254/latest/meta-data/hostname | cut -d . -f 1)'' >> /etc/hosts" ]
- [ sh, -xc, "su stack -c 'cd ~; git clone https://github.com/openstack-dev/devstack.git'" ]
- [ sh, -xc, "su stack -c 'cp /opt/local.conf ~/devstack/'" ]
- [ sh, -xc, "su stack -c 'bash /opt/run_devstack_into_tmux.sh'" ]

final_message: "!!! Your devstack is up and running. You can reach the OpenStack dashboard !!! (cloudinit runs in $UPTIME seconds)"
</nowiki>

OpenStack Upstream Institute

2014-10-03T10:37:28Z

Dachary: Haikel Guemar

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =
* Stefano Maffulli <stefano@openstack.org> (training, mentoring, assistant, english) (2014/05)
* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english) (2014/05, 2014/11)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english) (2014/05, 2014/11)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rodolphe@quiedeville.org> (training, mentoring, assistant, french) (2014/11)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Sahid Ferdjaoui <sahid.ferdjaoui@redhat.com> (assistant, french, english) (2014/05, 2014/11)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english) (2014/11)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, training, french, english) (2014/11)
* Julie Pichon <jpichon@redhat.com> (training, mentoring, assistant, english) (2014/11)
* Adrien Cunin <adrien.cunin@osones.com> (mentoring, assistant, french, english) (2014/11)
* Tim Freund <tim@freunds.net> (assistant, english) (2014/11)
* Syed Armani <syed.armani@hastexo.com> (training, mentoring, assistant, english) (2014/11)
* Victoria Martínez de la Cruz <victoria@vmartinezdelacruz.com> (assistant, english) (2014/11)
* Cindy Pallares <cpallares@redhat.com> (assistant, english) (2014/11)
* Irena Berezovsky <irena.berezovsky@gmail.com> (assistant, mentor, english) (2014/11)
* Haikel Guemar <haikel.guemar@gmail.com> (assistant, mentor, french, english) (2014/11)

OpenStack Upstream Institute

2014-09-16T08:59:04Z

Dachary: Irena Berezovsky

OpenStack Upstream Institute

2014-09-09T12:55:58Z

Dachary: Victoria

OpenStack Upstream Institute

2014-09-04T13:20:11Z

Dachary: Syed Armani

Puppet

2014-06-16T08:16:16Z

Dachary: add puppet-ceph to the list of projects

== Introduction ==

The Puppet modules for OpenStack were written as a collaborative effort between OpenStack operators using Puppet.

== Puppet Modules ==

Puppet modules for the OpenStack project are hosted on [http://ci.openstack.org/stackforge.html StackForge].

The following Puppet modules exist:
* [https://github.com/stackforge/puppet-ceilometer stackforge/puppet-ceilometer]
* [https://github.com/stackforge/puppet-cinder stackforge/puppet-cinder]
* [https://github.com/stackforge/puppet-designate stackforge/puppet-designate]
* [https://github.com/stackforge/puppet-glance stackforge/puppet-glance]
* [https://github.com/stackforge/puppet-heat stackforge/puppet-heat]
* [https://github.com/stackforge/puppet-horizon stackforge/puppet-horizon]
* [https://github.com/stackforge/puppet-ironic stackforge/puppet-ironic]
* [https://github.com/stackforge/puppet-keystone stackforge/puppet-keystone]
* [https://github.com/stackforge/puppet-neutron stackforge/puppet-neutron]
* [https://github.com/stackforge/puppet-nova stackforge/puppet-nova]
* [https://github.com/stackforge/puppet-openstack stackforge/puppet-openstack]
* [https://github.com/stackforge/puppet-swift stackforge/puppet-swift]
* [https://github.com/stackforge/puppet-tempest stackforge/puppet-tempest]
* [https://github.com/stackforge/puppet-vswitch stackforge/puppet-vswitch]
* [https://github.com/stackforge/puppet-ceph stackforge/puppet-ceph]

=== Branches ===

The master branch of each modules corresponds to the master branch of the current OpenStack core projects. Once released, a stable branch will be created and should be considered stable.

For example, the current master branch of stackforge/puppet-keystone is targeting OpenStack Juno, once released, a new stable/juno branch will be created, from that point onward the master branch should target the OpenStack K release.

=== Releases ===

Master version of the modules will be released as a new major version to Puppet Forge (forge.puppetlabs.com) when its related version of OpenStack is released.

Each version of OpenStack have a corresponding release on the forge.

{| class="wikitable"
|-
! Module Version !! OpenStack Version !! OpenStack Version Codename
|-
| 2.y.z || 2013.1.x || Grizzly
|-
| 3.y.z || 2013.2.x || Havana
|-
| 4.y.z || 2014.1.x || Icehouse
|-
| 5.z.y || 2014.2.x || Juno
|}

=== Supported Platforms ===

The following OS/version are supported by the Puppet modules:
* Fedora 18
* RHEL 6.4
* Ubuntu 12.04 (Precise)
* Debian 7.0 (Wheezy)

The modules have been primarily tested on Puppet 2.7.x and Ruby 1.8.7, although they are also being used with Puppet 3.1.x, 3.0.x, with Ruby 1.9.3.

Puppet 2.6.x is currently NOT supported, it has been EOL'ed by PuppetLabs.

== Getting Help ==

=== Mailing list ===

In general, the mailing list is preferred, because it makes the information more readily available so that others who have the same question can search for and find those answers.

You can read and subscribe to the mailing list here: https://groups.google.com/a/puppetlabs.com/forum/#!forum/puppet-openstack

puppet-openstack@puppetlabs.com

=== IRC ===

You can talk to us directly in IRC on the '''#puppet-openstack''' channel. (freenode.net)

IRC logs can be found [http://irclog.perlgeek.de/puppet-openstack/ here].

=== Reporting bugs ===

We are using [https://launchpad.net/ Launchpad] for bugs and features tracking. Issues and requests should be submitted under the [https://launchpad.net/puppet-openstack/ Puppet OpenStack] project.

== Developer documentation ==

=== Contributing to the modules ===

==== Getting Started ====

We follow the same process as all of the other OpenStack projects.

To contribute, the following docs contain enough information to get started:
* https://wiki.openstack.org/wiki/How_To_Contribute
* https://wiki.openstack.org/wiki/GettingTheCode
* https://wiki.openstack.org/wiki/GerritWorkflow

* go to : settings > watched projects and add the puppet projects (all of the form stackforge/puppet-*)

=== How code gets merged ===

Code is merged based on the voting process of the modules in Gerrit. All submitted patches automatically trigger a job that runs its rspec-puppet tests. This job is considered to be a gate in that no code is allowed to be merged that does not pass these tests. The results of this job are listed for every patch as a +1 Verified vote from Jenkins.

Any users can +/- 1 a commit and add comments on commit, but only members of the puppet-manager-core group have the ability to +2 and approve code to be merged.

Puppet OpenStack CI, and SmokeStack are two continuous integration environments that can be used to verify that any given patch can be used to deploy a functional multi-node environments. The integration of both of these systems is an ongoing process, so failures should be followed up on, but are not considered blockers at this moment.

=== Patches ===

Patches waiting to be merged can be viewed in Gerrit e.g. for stackforge/puppet-keystone

https://review.openstack.org/#/q/status:open+project:stackforge/puppet-keystone,n,z

Q. How do I go about submitting a patch for a released branch, what the correct process?
Unless is not relevant all patches should be approved for the master branch before you submit them for a stable branch. This ensures we maintain stability in the stable branches and functionality

==== Downloading a local patch ====

Clone the relevant module from StackForge, ex:

git clone git://github.com/stackforge/puppet-openstack

in the patch, find the git checkout or cherry-pick command, and copy it:

git fetch https://review.openstack.org/stackforge/puppet-openstack refs/changes/52/29452/9 && git checkout FETCH_HEAD

if you wanted to update an existing patch:

make a topic branch:

git checkout -b my_topic

make your changes:

hack,hack,hack

amend the current commit:

git commit --amend .

now resubmit:

git review

=== Rspec puppet tests ===

Rspec puppet tests are a requirement for getting code merged into the StackForge modules.

The best reference for getting started with rspec-puppet can be found [http://rspec-puppet.com/ here]

==== Running local tests ====

The following command can invoked from any if the modules' directories to run their rspec puppet tests.

It assumes that both bundler as well as rubygems (and ruby) are already installed on the system.

mkdir vendor
export GEM_HOME=vendor
bundle install
# bundle exec rake -T
bundle exec rake spec

This relies on the file .fixtures.yaml to install all of the external module required for testing.
The urls in this file use the git:// protocol, so this may need to be updated if you are behind a proxy.

=== stable branches ===

Master of the modules should be targeting the trunk of openstack as soon as a release is announced.

When this happens, a stable branch is created for any previous releases.

ie: stable/grizzly

It is the responsibility for the patch submitted to know if their patch should be backported to previous stable branches.

The general process for this can be found here: https://wiki.openstack.org/wiki/StableBranch#Workflow

OpenStack Upstream Institute

2014-06-05T15:22:12Z

Dachary: /* Staff */

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =
* Stefano Maffulli <stefano@openstack.org> (training, mentoring, assistant, english) (2014/05)
* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english) (2014/05, 2014/11)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english) (2014/05, 2014/11)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rodolphe@quiedeville.org> (training, mentoring, assistant, french) (2014/11)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english) (2014/11)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, french, english)
* Julie Pichon <jpichon@redhat.com> (training, mentoring, assistant, english) (2014/11)
* Adrien Cunin <adrien.cunin@osones.com> (mentoring, assistant, french, english) (2014/11)
* Tim Freund <tim@freunds.net> (assistant, english)

OpenStack Upstream Institute

2014-06-03T17:13:00Z

Dachary: Tim Freund

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =
* Stefano Maffulli <stefano@openstack.org> (training, mentoring, assistant, english) (2014/05)
* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english) (2014/05, 2014/11)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english) (2014/05, 2014/11)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french) (2014/11)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english) (2014/11)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, french, english)
* Julie Pichon <jpichon@redhat.com> (training, mentoring, assistant, english) (2014/11)
* Adrien Cunin <adrien.cunin@osones.com> (mentoring, assistant, french, english) (2014/11)
* Tim Freund <tim@freunds.net> (assistant, english)

OpenStack Upstream Institute

2014-06-03T12:01:57Z

Dachary: Adrien Cunin

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =
* Stefano Maffulli <stefano@openstack.org> (training, mentoring, assistant, english) (2014/05)
* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english) (2014/05, 2014/11)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english) (2014/05, 2014/11)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french) (2014/11)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english) (2014/11)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, french, english)
* Julie Pichon <jpichon@redhat.com> (training, mentoring, assistant, english) (2014/11)
* Adrien Cunin <adrien.cunin@osones.com> (mentoring, assistant, french, english) (2014/11)

OpenStack Upstream Institute

2014-06-03T09:55:46Z

Dachary: Stefano of course !

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =
* Stefano Maffulli <stefano@openstack.org> (training, mentoring, assistant, english) (2014/05)
* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english) (2014/05, 2014/11)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english) (2014/05, 2014/11)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french) (2014/11)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english) (2014/11)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, french, english)
* Julie Pichon <jpichon@redhat.com> (training, mentoring, assistant, english) (2014/11)

OpenStack Upstream Institute

2014-06-03T09:45:37Z

Dachary: english only

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =

* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english) (2014/05, 2014/11)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english) (2014/05, 2014/11)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french) (2014/11)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english) (2014/11)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, french, english)
* Julie Pichon <jpichon@redhat.com> (training, mentoring, assistant, english) (2014/11)

OpenStack Upstream Institute

2014-06-03T09:43:06Z

Dachary: Julie Pichon

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =

* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english) (2014/05, 2014/11)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english) (2014/05, 2014/11)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french) (2014/11)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english) (2014/11)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, french, english)
* Julie Pichon <jpichon@redhat.com> (training, mentoring, assistant, french, english) (2014/11)

OpenStack Upstream Institute

2014-06-03T09:23:34Z

Dachary: Schedule for staff members

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =

* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english) (2014/05, 2014/11)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english) (2014/05, 2014/11)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french) (2014/11)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english) (2014/05, 2014/11)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english) (2014/11)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, french, english)

OpenStack Upstream Institute

2014-06-03T09:16:58Z

Dachary: Sylvain Bauza

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =

* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, french, english)

OpenStack Upstream Institute

2014-05-30T14:17:06Z

Dachary: Add christophe

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =

* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english)
* Christophe Sauthier <christophe.sauthier@objectif-libre.com> (training, mentoring, french) + (assistant, french, english)

OpenStack Upstream Institute

2014-05-16T03:32:48Z

Dachary: wrong mail

OpenStack Upstream Institute

2014-05-16T03:28:53Z

Dachary: /* When & Where to get OpenStack Upstream Training */

OpenStack Upstream Institute

2014-05-16T03:27:34Z

Dachary: /* Staff */

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Atlanta, before the OpenStack Summit, Sat-Sun May 10-11. [http://www.eventbrite.com/e/openstack-upstream-training-tickets-2769119511 Reserve you seat].

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =

* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english)
* Pierre Padruxe <pierre.padruxe@gmail.com> (mentoring, french, english)

OpenStack Upstream Institute

2014-05-16T03:26:22Z

Dachary: /* How to prepare */

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training =

Next installation of the OpenStack Upstream Training will be in Atlanta, before the OpenStack Summit, Sat-Sun May 10-11. [http://www.eventbrite.com/e/openstack-upstream-training-tickets-2769119511 Reserve you seat].

= How to prepare =

* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.

= Staff =

* Loic Dachary <loic@dachary.org> (training, mentoring, assistant, french, english)
* Chris Ricker <chris.ricker@gmail.com> (trainng, mentoring, assistant, english)
* Xavier Antoviaque <xavier@antoviaque.org> (training, mentoring, assistant, french, english)
* Rodolphe Quiedeville <rq@quiedeville.org> (training, mentoring, assistant, french)
* Edouard THULEAU <edouard.thuleau@cloudwatt.com> (assistant, french, english)
* Sahid Ferdjaoui <sahid.ferdjaoui@cloudwatt.com> (assistant, french, english)
* Pierre Padruxe <pierre.padruxe@gmail.com> (mentoring, french, english)

OpenStack Upstream Institute

2014-05-16T03:23:21Z

Dachary: The date is not set yet.

OpenStack Upstream Institute

2014-05-16T03:19:22Z

Dachary: Add staff list

Design Summit/Juno/Etherpads

2014-05-13T12:57:03Z

Dachary: rename the design summit 101 pad

[[Category:Summit]]
[[Category:Juno]]
[[Category:Etherpad]]

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== Barbican ==

* Tue 1115-1155 [https://etherpad.openstack.org/p/barbican-events Barbican Events]
* Tue 1205-1245 [https://etherpad.openstack.org/p/barbican-kite Kite]
* Tue 1640-1720 [https://etherpad.openstack.org/p/barbican-plugins Barbican Plug-in Architecture]
* Tue 1730-1810 [https://etherpad.openstack.org/p/barbican-asym Barbican SSL/TLS Workflow]

== Ceilometer ==

* Wed 0900-0940 [https://etherpad.openstack.org/p/ceilometer-agent-repartition Ceilometer agents repartition]
* Wed 0950-1030 [https://etherpad.openstack.org/p/ceilometer-test-strategy Improve Ceilometer test strategy]
* Wed 1100-1140 Complex query on Ceilometer stats & project-specific meters
* Wed 1150-1230 [https://etherpad.openstack.org/p/ceilometer-tsdaas Rethinking Ceilometer as Time-Series-Data-as-a-Service]
* Wed 1350-1430 [https://etherpad.openstack.org/p/ceilometer-schema Revise Ceilometer data model to improve performance]
* Wed 1440-1520 Ceilometer Dev/Ops Session
* Wed 1530-1610 [https://etherpad.openstack.org/p/ceilometer-snmp-inspector Ceilometer SNMP improvements & code-free meters]
* Wed 1630-1710 [https://etherpad.openstack.org/p/ceilometer-alarm-and-log-improvments Ceilometer alarm evaluation improvements & effective logging]
* Wed 1720-1800 Ironic and Ceilometer
* Thurs 0900-0940 [https://etherpad.openstack.org/p/juno-summit-metering-network-services Deploying Ceilometer w/ TripleO & Metering Network Services]

== Cinder ==

* Thurs 15.30-16:10 [https://etherpad.openstack.org/p/juno-cinder-backup-restore Volume Backup\Restore]
* Thurs 16:10-16:50 [https://etherpad.openstack.org/p/juno-cinder-volume-replication Volume Replication]
* Thurs 17:00-17:40 [https://etherpad.openstack.org/p/juno-cinder-DRBD DRBD For Cinder-Volumes]
* Friday 09:00-09:40 [https://etherpad.openstack.org/p/juno-cinder-nfs-in-cinder NFS and its role within Cinder]
* Friday 10:00-10:40 [https://etherpad.openstack.org/p/juno-cinder-cinder-consistency-groups Adding Consistency Groups to Cinder]
* Friday 10:50-11:30 [https://etherpad.openstack.org/p/juno-cinder-3rd-party-cert-and-verification 3'rd party certificiation and CI systems]
* Friday 11:40-12:20 [https://etherpad.openstack.org/p/juno-cinder-changed-block-list Changed Block List for Cinder Volumes]
* Friday 13:20-14:00 [https://etherpad.openstack.org/p/juno-cinder-state-and-workflow-management Cinder State and Workflow Management]
* Friday 14:10-14:50 [https://etherpad.openstack.org/p/juno-cinder-framework-for-state-reporting Framework for detailed Volume Stats reporting]
* Friday 15:00-15:40 [https://etherpad.openstack.org/p/juno-cinder-multiple-pools-per-backend Mulitple Pools per Cinder Backend]
* Friday 16:00-16:40 [https://etherpad.openstack.org/p/juno-cinder-whats-a-cinder-driver What is a Cinder Driver]

==Cross-Project==
* Tues 11:15-11:55 [https://etherpad.openstack.org/p/juno-cross-project-future-of-python The Future of Python Support]
* Tues 11:15-11:55 [https://etherpad.openstack.org/p/9XQ7Q2NQdv Solum, Murano, Heat: how to handle app lifecycle ?]
* Tues 11:15-12:45 [https://etherpad.openstack.org/p/juno-cross-project-consistency-across-rest-apis Consistency Across OpenStack REST APIs]
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-cross-oslo-library-releases New Oslo Library Releases and Your Project]
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-dealing-rejections Dealing with changes of plans, rejections and more]
* Tues 14:50-15:30 [https://etherpad.openstack.org/p/openstack-and-its-cla Taking another look at our CLA]
* Tues 14:50-15.30[https://etherpad.openstack.org/p/juno-summit-cross-project-user-experience User Experience Designers Gathering]
* Tues 15:40-16:20 [https://etherpad.openstack.org/p/juno-cross-project-quota-management-endpoint Cross-project Quota Management Service Endpoint]
* Tues 15:40 [https://etherpad.openstack.org/p/juno-cross-project-tracking-features Tracking incoming features]
* Tues 16:40 [https://etherpad.openstack.org/p/juno-summit-gate How do we make it easier to fix the Gate?]
* Tues 16:40 [https://etherpad.openstack.org/p/juno-summit-openstackclient Clients and SDKs Part I]
* Tues 17:30 [https://etherpad.openstack.org/p/juno-test-maxtrices Test Matrices and Feature Parity]
* Tues 17:30 [https://etherpad.openstack.org/p/juno-summit-sdk Clients and SDKs Part II]

== Devstack ==
* Fri 16:00 [https://etherpad.openstack.org/p/juno-summit-devstack-update DevStack Update]
* Fri 16:50 [https://etherpad.openstack.org/p/juno-summit-devstack-project-support DevStack Project Support]

== Documentation ==

* Tues 11:05 B304 [https://etherpad.openstack.org/p/summit-session-cross-project-docs Cross-Project Documentation]
* Wed 09:00 [https://etherpad.openstack.org/p/installation-guide-audit Installation Guide Discussion]
* Thu 09:50 [https://etherpad.openstack.org/p/summit0514-session-patching-the-docs-process Patching the Documentation Process]
* Fri 09:00 [https://etherpad.openstack.org/p/summit-b301-ci-doc-automation Continuous Publishing and Automation for Docs]
* Fri 11:40 [http://junodesignsummit.sched.org/event/bd8428a881229a747d9c2c3cab96e1b2#.U3Eitq1dU0w Beef Up User and Operations Guides for Integrated]

== Glance ==
* Wed 5:20-6:00: [https://etherpad.openstack.org/p/juno-hot-artifacts-repository-finalize-design Hot/Artifacts repository finalize design]
* Thur 9:00-9:40: [https://etherpad.openstack.org/p/juno-glance-store-and-future-features Glance Store and Future Features]
* Thur 9:50-10:30: [https://etherpad.openstack.org/p/juno-tasks-review-and-taskflow Task Review and Taskflow]
* Thur 11:00-11:40: [https://etherpad.openstack.org/p/juno-adding-functional-operations-to-glance-api Adding functional operations to Glance API]
* Thur 11:50-12:30: [https://etherpad.openstack.org/p/juno-poking-image-filesystem Poking Image Filesystem]

== Heat ==

* Wed 9.00-9:40 [https://etherpad.openstack.org/p/juno-summit-heat-dev-ops Dev/Ops Session]
* Wed 9.50-10:30 [https://etherpad.openstack.org/p/juno-summit-heat-sw-orch Next Steps for Software Orchestration]
* Wed 11.00-11:40 [https://etherpad.openstack.org/p/heat-workflow-vs-convergence Scaling, Robustness and Convergence]
* Wed 11.50-12:30 [https://etherpad.openstack.org/p/juno-summit-heat-notifications Augmenting Polling with Notifications]
* Wed 13.50-14:30 [https://etherpad.openstack.org/p/juno-summit-heat-event Event notifications]
* Wed 14.40-15:20 [https://etherpad.openstack.org/p/juno-summit-heat-callbacks Stack and Resource lifecycle callbacks]
* Wed 15.30-16:10 [https://etherpad.openstack.org/p/juno-summit-heat-api-v2 API v2]
* Wed 16.30-17:10 [https://etherpad.openstack.org/p/juno-summit-heat-plugin-versioning Resource Plugin Versioning]

== Horizon ==
* Wed 15:30-16:10 [https://etherpad.openstack.org/p/juno-summit-horizon-static-files Handling of static files]
* Wed 16:30-17:10 [https://etherpad.openstack.org/p/juno-summit-horizon-widgets Modular, widget-based views and more pluggability]
* Wed 17:20-18:00 [https://etherpad.openstack.org/p/juno-summit-horizon-client-side Client side development]
* Thu 17:00-17:40 [https://etherpad.openstack.org/p/juno-summit-horizon-tuskar-ui Tuskar-UI and its relationship to Horizon]
* Fri 09:00-09:40 [https://etherpad.openstack.org/p/juno-summit-horizon-usability-test-results Review Horizon Usability Test feedback, proposals]
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/juno-summit-overview-page-horizon Better Overview Pages]
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/Dashboard_Accessibility Dashboard Accessibility]
* Fri 10:50-11:30 [https://etherpad.openstack.org/p/juno-summit-horizon-devops Horizon Dev/Ops Session]

== Infrastructure ==
* Wed 9:50 - [https://etherpad.openstack.org/p/juno-summit-elastic-recheck Elastic Recheck next steps]
* Wed 11:00 - [https://etherpad.openstack.org/p/juno-summit-jenkins-moving-forward Jenkins moving forward]
* Wed 11:50 - [https://etherpad.openstack.org/p/juno-infra-improving-3rd-party-testing Improving Third Party Testing]
* Thu 11:00 - [https://etherpad.openstack.org/p/juno-infra-design-Vinz-review-system Discussion/design talk of Vinz code review system]
* Thu 11:50 - [https://etherpad.openstack.org/p/juno-infra-storyboard StoryBoard: current status & Juno plans]
* Fri 9:50 - [https://etherpad.openstack.org/p/juno-openid Replace Launchpad OpenID authentication]
* Fri 10:50 - [https://etherpad.openstack.org/p/translation-platform-discussion Translation platform discussion]

== Ironic ==

* Tues 11:15 [https://etherpad.openstack.org/p/juno-summit-ironic-python-agent Ironic Python Agent]
* Tues 12:05 [https://etherpad.openstack.org/p/juno-summit-ironic-multitenancy Hardware Multitenancy Risk Mitigation]
* Tues 14:50 [https://etherpad.openstack.org/p/juno-summit-ironic-performance Performance and Scalability]
* Tues 15:40 [https://etherpad.openstack.org/p/juno-summit-ironic-arch Planning changes for Juno]

== Keystone ==

* Wed 11:50-12:30 [https://etherpad.openstack.org/p/juno-keystone-hierarchical-multitenancy Hierarchical Multitenancy]
* Wed 13:50-14:30 [https://etherpad.openstack.org/p/juno-keystone-devops DevOps]
* Wed 14:40-15:20 [https://etherpad.openstack.org/p/juno-keystone-client python-keystoneclient]
* Thurs 11:50-12:30 [https://etherpad.openstack.org/p/juno-keystone-authorization Authorization]
* Thurs 13:30-14:10 [https://etherpad.openstack.org/p/juno-keystone-federation Federation]
* Thurs 14:20-15:00 [https://etherpad.openstack.org/p/juno-keystone-locally-managed-identities Locally-managed identities]
* Fri 11:40-12:20 [https://etherpad.openstack.org/p/juno-keystone-user-ids User & Group IDs]
* Fri 13:20-14:00 [https://etherpad.openstack.org/p/juno-keystone-service-catalog Service Catalog]

== Marconi ==

* Tues 14:50 - [https://etherpad.openstack.org/p/juno-marconi-queue-flavors Queue Flavors]
* Tues 15:40 - [https://etherpad.openstack.org/p/juno-marconi-notifications-on-marconi Notifications on Marconi]
* Tues 16:40 - [https://etherpad.openstack.org/p/ATL-marconi-ops Marconi Dev/Ops Session]
* Tues 17:30 - [https://etherpad.openstack.org/p/juno-marconi-scale-single-queue Scaling an Individual Queue]

== Neutron ==
* Wed 9:00-9:40: [https://etherpad.openstack.org/p/juno-neutron-policies New Policies for Neutron in Juno]
* Wed 9:50-10:30: [https://etherpad.openstack.org/p/juno-neutron-code-review Code Review Process Improvements]
* Wed 11:00-11:40: [https://etherpad.openstack.org/p/neutron-ipv6-atlanta-summit IPv6 status in Neutron]
* Wed 11:50-12:30: [https://etherpad.openstack.org/p/ML2_Juno_Roadmap ML2 Juno Roadmap] and [https://etherpad.openstack.org/p/ML2_mechanismdriver_extensions_support Extensions Support In ML2 Mechanism Drivers]
* Wed 13:50-14:30: Refactoring the Neutron Server Core
* Wed 14:40-15:20: [https://etherpad.openstack.org/p/novanet-neutron-migration Nova-Net to Neutron migration]
* Wed 15:30-14:10: Integrating Tasks into Neutron
* Wed 16:30-17:10: [https://etherpad.openstack.org/p/juno-advanced-services Advanced Services] and [https://etherpad.openstack.org/p/juno-virtual-resource-for-service-chaining Virtual Resource for Service Chaining]
* Wed 17:20-18:00: [https://etherpad.openstack.org/p/Distributed-Virtual-Router Neutron Distributed Virtual Router Progress Update]
* Thu 9:00-9:40: [https://etherpad.openstack.org/p/TempestAndNeutronJuno Neutron QA and Testing]
* Thu 9:50-10:30: [https://etherpad.openstack.org/p/juno-neutron-responsibilities Sharing the load of operational responsibility]
* Thu 11:00-11:40: Neutron LBaaS Update
* Thur 11:50-12:30: [https://etherpad.openstack.org/p/juno-neutron-modular-l2-agent Modular Layer2 Agents]
* Fri 10:50-11:30: [https://etherpad.openstack.org/p/group-based-policy Neutron Group Based Policy]
* Fri 11:40-12:30: [https://etherpad.openstack.org/p/juno-fwaas FWaaS] and [https://etherpad.openstack.org/p/juno-vpnaas VPNaaS]
* Fri 13:20-14:00: LBaaS SSL L7 and automated scenarios
* Fri 14:10-14:50: [https://etherpad.openstack.org/p/hierarchical_network_topology Hierarchical Network Topologies]
* Fri 15:00-15:40: [https://etherpad.openstack.org/p/L3-vendor-plugins L3 Vendor Plugins]
* Fri 16:00-16:40: [https://etherpad.openstack.org/p/juno-dynamic-routing Dynamic routing] and [https://etherpad.openstack.org/p/juno-neutron-pluggable-external-network pluggable external networks]
* Fri 16:50-17:30: [https://etherpad.openstack.org/p/servicevm Service VM Discussion]

== Nova ==

'''Wednesday, May 14'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-third-party-ci Continuation of third party CI]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-clustered-hypervisor-support Clustered hypervisor support in Nova]
* 11:00am [https://etherpad.openstack.org/p/juno-nova-deprecating-baremetal The road to deprecating nova.virt.baremetal]
* 11:50am [https://etherpad.openstack.org/p/juno-nova-data-transfer-service Data transfer service plug-in]
* 1:50pm [https://etherpad.openstack.org/p/juno-nova-live-upgrade Next steps in live upgrade]
* 2:40pm [https://etherpad.openstack.org/p/juno-nova-image-precaching Image precaching service]
* 3:30pm [https://etherpad.openstack.org/p/juno-nova-flavor-storage-revamp Flavor storage re-vamp]
* 4:30pm [https://etherpad.openstack.org/p/juno-nova-cross-project-interactions Rethinking cross project interactions]
* 5:20pm [https://etherpad.openstack.org/p/juno-nova-v2-on-v3-api-poc Nova V2 on V3 API implementation POC]

'''Thursday, May 15'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-hypev-new-features Hyper-V Driver new features]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-libvirt-driver-roadmap Libvirt driver roadmap for Juno]
* 11:00am [https://etherpad.openstack.org/p/juno-nova-kvm-live-migration Improve performance of live migration on KVM]
* 11:50am [https://etherpad.openstack.org/p/juno-nova-conductor-api limited conductor API]
* 1:30pm [https://etherpad.openstack.org/p/juno-nova-quota-state-management Implementing state management for quotas]
* 2:20pm [https://etherpad.openstack.org/p/juno-nova-multi-volume-snapshots Multi-Volume Snapshots]
* 3:10pm [https://etherpad.openstack.org/p/juno-nova-hypervisor-power-mgmt Hypervisor power management]
* 4:10pm [https://etherpad.openstack.org/p/juno-nova-sriov-support SR-IOV support]
* 5:00pm [https://etherpad.openstack.org/p/juno-nova-v3-api Nova V3 API]

'''Friday, May 16'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-vmware-driver-roadmap Vmwareapi driver roadmap for Juno]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-docker-driver-features Docker driver - features & testing]
* 10:50am [https://etherpad.openstack.org/p/juno-nova-gantt-apis Future of Gantt APIs and interfaces]
* 11:40am [https://etherpad.openstack.org/p/juno-nova-no-db-scheduler Common no DB Scheduler]
* 1:20pm [https://etherpad.openstack.org/p/juno-nova-scheduling-server-groups Simultaneous Scheduling for Server Groups]
* 2:10pm [https://etherpad.openstack.org/p/juno-nova-scheduler-hints-vm-lifecycle Scheduler hints for VM life cycle]
* 3:00pm [https://etherpad.openstack.org/p/juno-nova-devops Nova Dev/Ops Session]
* 4:00pm [https://etherpad.openstack.org/p/juno-nova-unsession Unsession]

== Ops ==
* Mon 1115 – 1155 [https://etherpad.openstack.org/p/juno-summit-ops-askthedevs Ask the devs: Meet the PTLs and TC, How to get the best out of the design summit]
* Mon 1205 – 1245 [https://etherpad.openstack.org/p/juno-summit-ops-reasonabledefaults Reasonable Defaults]
* Mon 1400 – 1440 [https://etherpad.openstack.org/p/juno-summit-ops-upgradesdeployment Upgrades and Deployment Approaches]
* Mon 1450 – 1620 [https://etherpad.openstack.org/p/juno-summit-ops-architecture Architecture Show and Tell, Tales and Fails]
* Mon 1640 – 1720 [https://etherpad.openstack.org/p/juno-summit-ops-networking Networking]
* Mon 1730 – 1810 [https://etherpad.openstack.org/p/juno-summit-ops-security Security]

* Fri 9:00 – 9:40 [https://etherpad.openstack.org/p/juno-summit-ops-enterprise Enterprise Gaps]
* Fri 9:50 – 10:30 [https://etherpad.openstack.org/p/juno-summit-ops-database Database]
* Fri 10:50 – 11:30 [https://etherpad.openstack.org/p/juno-summit-ops-issuesatscale Issues at Scale]
* Fri 11:40 – 12:20 [https://etherpad.openstack.org/p/juno-summit-ops-meta Meta Discussion – ops communication and governance]
* Fri 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-ops-ansible Ansible]
* Fri 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-ops-chef Chef]
* Fri 3:00 – 3:40 [https://etherpad.openstack.org/p/juno-summit-ops-puppet Puppet]
* Fri 4:00 – 4:30 [https://etherpad.openstack.org/p/juno-summit-ops-monitoringlogging Monitoring and Logging]

== Oslo ==
* Wed 9:00 - 9:40 [https://etherpad.openstack.org/p/juno-oslo-release-plan Release Plan for Low-level Libraries]
* Wed 9:50 - 10:30 [https://etherpad.openstack.org/p/juno-oslo-messaging oslo.messaging status and plans for Juno]
* Wed 11:00 - 11:40 [https://etherpad.openstack.org/p/olso.messaging_amqp_1.0 AMQP 1.0 protocol driver]
* Thu 9:00 - 9:40 Oslo Library Teams Breakout Session
* Thu 9:50 - 10:30 [https://etherpad.openstack.org/p/juno-infra-library-testing Testing pre-releases of Oslo libs with apps]
* Thu 11:00 - 11:40 [https://etherpad.openstack.org/p/juno-osprofiler OpenStack cross service/project OpenStack profiler]
* Thu 15:10 - 16:00 [https://etherpad.openstack.org/p/juno-oslo-bayer Upstream chat with Mike Bayer]
* Thu 16:10 - 17:00 [https://etherpad.openstack.org/p/juno-summit-oslo-messaging-rpc-proxy rpc proxy(oslo.messaging)]
* Fri 14:10 - 15:50 [https://etherpad.openstack.org/p/juno-summit-oslo-rootwrap oslo.rootwrap: performance and other improvements]
* Fri 15:00 - 16:40 [https://etherpad.openstack.org/p/juno-oslo-semantic-versioning Semantic versioning and oslo]
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-oslo-pki-for-messaging PKI for messaging]

== QA ==

'''Wednesday'''
* 2:40 – 3:20 [https://etherpad.openstack.org/p/juno-summit-branchless-tempest Branchless Tempest]
* 3:30 – 4:10 [https://etherpad.openstack.org/p/juno-summit-tempest-documentation Tempest Documentation Gaps]
* 4:30 – 5:10 [https://etherpad.openstack.org/p/juno-qa-functional-api Functional API Testing - post dev QA vs TDD]
* 5:20 – 6:00 [https://etherpad.openstack.org/p/juno-rally-and-tempest Rally and Tempest Integration]

'''Thursday'''
* 1:30 – 2:10 [https://etherpad.openstack.org/p/juno-summit-api-tests-with-jsonschema API tests with JSONSchema]
* 2:20 – 3:00 [https://etherpad.openstack.org/p/juno-summit-negative-fuzzy-testing Negative Testing: Fuzzy Test Framework]
* 3:10 – 3:50 [https://etherpad.openstack.org/p/juno-summit-improve-ux-tools How to improve the UX of our Testing Tools]
* 4:10 – 4:50 [https://etherpad.openstack.org/p/juno-summit-tempest-gui-client-server Tempest, GUI, Client, Server]

'''Friday'''
* 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-grenade Grenade Current Status and Next Steps]
* 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-qa-policy QA Program Policy and Changes in Juno]

== Release Management ==

* Wednesday 1:50pm [https://etherpad.openstack.org/p/juno-summit-release-branches Release branches, QA and requirements]
* Thursday 9:00am [https://etherpad.openstack.org/p/juno-summit-vmt Vulnerability management in Juno]
* Thursday 5:00pm [https://etherpad.openstack.org/p/StableIcehouse Stable branches maintenance]
* Friday 3:00pm [https://etherpad.openstack.org/p/juno-summit-release-schedule Juno release schedule and processes]
* Friday 4:50pm [https://etherpad.openstack.org/p/juno-summit-feedback Design Summit feedback]

== Sahara (ex. Savanna) ==

* [http://junodesignsummit.sched.org/event/b4f52627efa42f285978d5af3643e189 Thu 13:30] [https://etherpad.openstack.org/p/juno-summit-sahara-relmngmt-backward Releasing and backward compatibility]
* [http://junodesignsummit.sched.org/event/c8774beefd9e9188a3e0729d2bd7131e Thu 14:20] [https://etherpad.openstack.org/p/juno-summit-sahara-testing-plugins CI/gating and plugin requirements]
* [http://junodesignsummit.sched.org/event/10bc9a23eb43eb9df885586035fb2491 Thu 15:10] [https://etherpad.openstack.org/p/juno-summit-sahara-scale-integration Scalable Sahara and further OpenStack integration]
* [http://junodesignsummit.sched.org/event/be842178a085fe95b7665a653f8ab541 Thu 16:10] [https://etherpad.openstack.org/p/juno-summit-sahara-ux UX improvements]
* [http://junodesignsummit.sched.org/event/dfa603324c0bbf29c2f09a77efb82d1d Thu 17:00] [https://etherpad.openstack.org/p/juno-summit-sahara-edp Future of EDP: plugins, SPI, Oozie]
* [http://junodesignsummit.sched.org/event/a64f771cf28ed3ad637730db828668ff Fri 09:00] [https://etherpad.openstack.org/p/juno-summit-sahara-v2-api Next major REST API - v2]
* [http://junodesignsummit.sched.org/event/49089a1d9c8203c6a4c1f0001fa417af Fri 09:50] [https://etherpad.openstack.org/p/juno-summit-sahara-roadmap-retro Sahara in Icehouse and Juno]

== Swift ==
== TripleO (Deployment) ==
* Fri 11:40 - 12:20 [https://etherpad.openstack.org/p/juno-summit-tripleo-tuskar-planning TripleO Tuskar Planning]
* Fri 13:20 - 14:00 [https://etherpad.openstack.org/p/juno-summit-tripleo-environment TripleO Development and Testing Environment]
* Fri 14:10 - 14:50 [https://etherpad.openstack.org/p/juno-summit-tripleo-and-docker TripleO and Docker]
* Fri 15:00 - 15:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-ci TripleO CI]
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-neutron TripleO and Neutron]
* Fri 16:50 - 17:30 [https://etherpad.openstack.org/p/juno-summit-tripleo-devops TripleO Dev/Ops Session]

== Trove ==
== User Committee ==
== Other Projects ==
* [http://junodesignsummit.sched.org/event/e04c26e2a5df3a5089b2ed701d2aac3b Tue 11:15 - 11:55] [https://etherpad.openstack.org/p/juno-101 Design Summit 101]
* [http://junodesignsummit.sched.org/event/6f9fe2ec2e6d3843139663a350cdc511 Tue 17:30 - 18:10] [https://etherpad.openstack.org/p/juno-summit-discovery-and-diagnostic-for-openstack Discovery and Diagnostic for OpenStack]
* [http://junodesignsummit.sched.org/event/ab6d8eed3c6fd85dc450c099aba22e11 Tue 12:05 - 12:45] [https://etherpad.openstack.org/p/juno-design-summit-designate-session-1 Designate Session 1]
* Tue 16:40 - 19:20 [https://etherpad.openstack.org/p/juno-summit-resource-reservation Climate, Resource Reservation for the OpenStack]
* [http://openstacksummitmay2014atlanta.sched.org/event/6e53527347d56d67120decd49bbac53b Wed 13:50 - 17:20] [https://etherpad.openstack.org/p/SolumSummitAgenda Solum Session]

Design Summit/Juno/Etherpads

2014-05-13T12:34:13Z

Dachary: Design summit 101

[[Category:Summit]]
[[Category:Juno]]
[[Category:Etherpad]]

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== Barbican ==

* Tue 1115-1155 [https://etherpad.openstack.org/p/barbican-events Barbican Events]
* Tue 1205-1245 [https://etherpad.openstack.org/p/barbican-kite Kite]
* Tue 1640-1720 [https://etherpad.openstack.org/p/barbican-plugins Barbican Plug-in Architecture]
* Tue 1730-1810 [https://etherpad.openstack.org/p/barbican-asym Barbican SSL/TLS Workflow]

== Ceilometer ==

* Wed 0900-0940 [https://etherpad.openstack.org/p/ceilometer-agent-repartition Ceilometer agents repartition]
* Wed 0950-1030 [https://etherpad.openstack.org/p/ceilometer-test-strategy Improve Ceilometer test strategy]
* Wed 1100-1140 Complex query on Ceilometer stats & project-specific meters
* Wed 1150-1230 [https://etherpad.openstack.org/p/ceilometer-tsdaas Rethinking Ceilometer as Time-Series-Data-as-a-Service]
* Wed 1350-1430 [https://etherpad.openstack.org/p/ceilometer-schema Revise Ceilometer data model to improve performance]
* Wed 1440-1520 Ceilometer Dev/Ops Session
* Wed 1530-1610 [https://etherpad.openstack.org/p/ceilometer-snmp-inspector Ceilometer SNMP improvements & code-free meters]
* Wed 1630-1710 [https://etherpad.openstack.org/p/ceilometer-alarm-and-log-improvments Ceilometer alarm evaluation improvements & effective logging]
* Wed 1720-1800 Ironic and Ceilometer
* Thurs 0900-0940 [https://etherpad.openstack.org/p/juno-summit-metering-network-services Deploying Ceilometer w/ TripleO & Metering Network Services]

== Cinder ==

* Thurs 15.30-16:10 [https://etherpad.openstack.org/p/juno-cinder-backup-restore Volume Backup\Restore]
* Thurs 16:10-16:50 [https://etherpad.openstack.org/p/juno-cinder-volume-replication Volume Replication]
* Thurs 17:00-17:40 [https://etherpad.openstack.org/p/juno-cinder-DRBD DRBD For Cinder-Volumes]
* Friday 09:00-09:40 [https://etherpad.openstack.org/p/juno-cinder-nfs-in-cinder NFS and its role within Cinder]
* Friday 10:00-10:40 [https://etherpad.openstack.org/p/juno-cinder-cinder-consistency-groups Adding Consistency Groups to Cinder]
* Friday 10:50-11:30 [https://etherpad.openstack.org/p/juno-cinder-3rd-party-cert-and-verification 3'rd party certificiation and CI systems]
* Friday 11:40-12:20 [https://etherpad.openstack.org/p/juno-cinder-changed-block-list Changed Block List for Cinder Volumes]
* Friday 13:20-14:00 [https://etherpad.openstack.org/p/juno-cinder-state-and-workflow-management Cinder State and Workflow Management]
* Friday 14:10-14:50 [https://etherpad.openstack.org/p/juno-cinder-framework-for-state-reporting Framework for detailed Volume Stats reporting]
* Friday 15:00-15:40 [https://etherpad.openstack.org/p/juno-cinder-multiple-pools-per-backend Mulitple Pools per Cinder Backend]
* Friday 16:00-16:40 [https://etherpad.openstack.org/p/juno-cinder-whats-a-cinder-driver What is a Cinder Driver]

==Cross-Project==
* Tues 11:15-11:55 [https://etherpad.openstack.org/p/juno-cross-project-future-of-python The Future of Python Support]
* Tues 11:15-11:55 [https://etherpad.openstack.org/p/9XQ7Q2NQdv Solum, Murano, Heat: how to handle app lifecycle ?]
* Tues 11:15-12:45 [https://etherpad.openstack.org/p/juno-cross-project-consistency-across-rest-apis Consistency Across OpenStack REST APIs]
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-cross-oslo-library-releases New Oslo Library Releases and Your Project]
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-dealing-rejections Dealing with changes of plans, rejections and more]
* Tues 14:50-15:30 [https://etherpad.openstack.org/p/openstack-and-its-cla Taking another look at our CLA]
* Tues 14:50-15.30[https://etherpad.openstack.org/p/juno-summit-cross-project-user-experience User Experience Designers Gathering]
* Tues 15:40-16:20 [https://etherpad.openstack.org/p/juno-cross-project-quota-management-endpoint Cross-project Quota Management Service Endpoint]
* Tues 15:40 [https://etherpad.openstack.org/p/juno-cross-project-tracking-features Tracking incoming features]
* Tues 16:40 [https://etherpad.openstack.org/p/juno-summit-gate How do we make it easier to fix the Gate?]
* Tues 16:40 [https://etherpad.openstack.org/p/juno-summit-openstackclient Clients and SDKs Part I]
* Tues 17:30 [https://etherpad.openstack.org/p/juno-test-maxtrices Test Matrices and Feature Parity]
* Tues 17:30 [https://etherpad.openstack.org/p/juno-summit-sdk Clients and SDKs Part II]

== Devstack ==
* Fri 16:00 [https://etherpad.openstack.org/p/juno-summit-devstack-update DevStack Update]
* Fri 16:50 [https://etherpad.openstack.org/p/juno-summit-devstack-project-support DevStack Project Support]

== Documentation ==

* Tues 11:05 B304 [https://etherpad.openstack.org/p/summit-session-cross-project-docs Cross-Project Documentation]
* Wed 09:00 [https://etherpad.openstack.org/p/installation-guide-audit Installation Guide Discussion]
* Thu 09:50 [https://etherpad.openstack.org/p/summit0514-session-patching-the-docs-process Patching the Documentation Process]
* Fri 09:00 [https://etherpad.openstack.org/p/summit-b301-ci-doc-automation Continuous Publishing and Automation for Docs]
* Fri 11:40 [http://junodesignsummit.sched.org/event/bd8428a881229a747d9c2c3cab96e1b2#.U3Eitq1dU0w Beef Up User and Operations Guides for Integrated]

== Glance ==
* Wed 5:20-6:00: [https://etherpad.openstack.org/p/juno-hot-artifacts-repository-finalize-design Hot/Artifacts repository finalize design]
* Thur 9:00-9:40: [https://etherpad.openstack.org/p/juno-glance-store-and-future-features Glance Store and Future Features]
* Thur 9:50-10:30: [https://etherpad.openstack.org/p/juno-tasks-review-and-taskflow Task Review and Taskflow]
* Thur 11:00-11:40: [https://etherpad.openstack.org/p/juno-adding-functional-operations-to-glance-api Adding functional operations to Glance API]
* Thur 11:50-12:30: [https://etherpad.openstack.org/p/juno-poking-image-filesystem Poking Image Filesystem]

== Heat ==

* Wed 9.00-9:40 [https://etherpad.openstack.org/p/juno-summit-heat-dev-ops Dev/Ops Session]
* Wed 9.50-10:30 [https://etherpad.openstack.org/p/juno-summit-heat-sw-orch Next Steps for Software Orchestration]
* Wed 11.00-11:40 [https://etherpad.openstack.org/p/heat-workflow-vs-convergence Scaling, Robustness and Convergence]
* Wed 11.50-12:30 [https://etherpad.openstack.org/p/juno-summit-heat-notifications Augmenting Polling with Notifications]
* Wed 13.50-14:30 [https://etherpad.openstack.org/p/juno-summit-heat-event Event notifications]
* Wed 14.40-15:20 [https://etherpad.openstack.org/p/juno-summit-heat-callbacks Stack and Resource lifecycle callbacks]
* Wed 15.30-16:10 [https://etherpad.openstack.org/p/juno-summit-heat-api-v2 API v2]
* Wed 16.30-17:10 [https://etherpad.openstack.org/p/juno-summit-heat-plugin-versioning Resource Plugin Versioning]

== Horizon ==
* Wed 15:30-16:10 [https://etherpad.openstack.org/p/juno-summit-horizon-static-files Handling of static files]
* Wed 16:30-17:10 [https://etherpad.openstack.org/p/juno-summit-horizon-widgets Modular, widget-based views and more pluggability]
* Wed 17:20-18:00 [https://etherpad.openstack.org/p/juno-summit-horizon-client-side Client side development]
* Thu 17:00-17:40 [https://etherpad.openstack.org/p/juno-summit-horizon-tuskar-ui Tuskar-UI and its relationship to Horizon]
* Fri 09:00-09:40 [https://etherpad.openstack.org/p/juno-summit-horizon-usability-test-results Review Horizon Usability Test feedback, proposals]
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/juno-summit-overview-page-horizon Better Overview Pages]
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/Dashboard_Accessibility Dashboard Accessibility]
* Fri 10:50-11:30 [https://etherpad.openstack.org/p/juno-summit-horizon-devops Horizon Dev/Ops Session]

== Infrastructure ==
* Wed 9:50 - [https://etherpad.openstack.org/p/juno-summit-elastic-recheck Elastic Recheck next steps]
* Wed 11:00 - [https://etherpad.openstack.org/p/juno-summit-jenkins-moving-forward Jenkins moving forward]
* Wed 11:50 - [https://etherpad.openstack.org/p/juno-infra-improving-3rd-party-testing Improving Third Party Testing]
* Thu 11:00 - [https://etherpad.openstack.org/p/juno-infra-design-Vinz-review-system Discussion/design talk of Vinz code review system]
* Thu 11:50 - [https://etherpad.openstack.org/p/juno-infra-storyboard StoryBoard: current status & Juno plans]
* Fri 9:50 - [https://etherpad.openstack.org/p/juno-openid Replace Launchpad OpenID authentication]
* Fri 10:50 - [https://etherpad.openstack.org/p/translation-platform-discussion Translation platform discussion]

== Ironic ==

* Tues 11:15 [https://etherpad.openstack.org/p/juno-summit-ironic-python-agent Ironic Python Agent]
* Tues 12:05 [https://etherpad.openstack.org/p/juno-summit-ironic-multitenancy Hardware Multitenancy Risk Mitigation]
* Tues 14:50 [https://etherpad.openstack.org/p/juno-summit-ironic-performance Performance and Scalability]
* Tues 15:40 [https://etherpad.openstack.org/p/juno-summit-ironic-arch Planning changes for Juno]

== Keystone ==

* Wed 11:50-12:30 [https://etherpad.openstack.org/p/juno-keystone-hierarchical-multitenancy Hierarchical Multitenancy]
* Wed 13:50-14:30 [https://etherpad.openstack.org/p/juno-keystone-devops DevOps]
* Wed 14:40-15:20 [https://etherpad.openstack.org/p/juno-keystone-client python-keystoneclient]
* Thurs 11:50-12:30 [https://etherpad.openstack.org/p/juno-keystone-authorization Authorization]
* Thurs 13:30-14:10 [https://etherpad.openstack.org/p/juno-keystone-federation Federation]
* Thurs 14:20-15:00 [https://etherpad.openstack.org/p/juno-keystone-locally-managed-identities Locally-managed identities]
* Fri 11:40-12:20 [https://etherpad.openstack.org/p/juno-keystone-user-ids User & Group IDs]
* Fri 13:20-14:00 [https://etherpad.openstack.org/p/juno-keystone-service-catalog Service Catalog]

== Marconi ==

* Tues 14:50 - [https://etherpad.openstack.org/p/juno-marconi-queue-flavors Queue Flavors]
* Tues 15:40 - [https://etherpad.openstack.org/p/juno-marconi-notifications-on-marconi Notifications on Marconi]
* Tues 16:40 - [https://etherpad.openstack.org/p/ATL-marconi-ops Marconi Dev/Ops Session]
* Tues 17:30 - [https://etherpad.openstack.org/p/juno-marconi-scale-single-queue Scaling an Individual Queue]

== Neutron ==
* Wed 9:00-9:40: [https://etherpad.openstack.org/p/juno-neutron-policies New Policies for Neutron in Juno]
* Wed 9:50-10:30: [https://etherpad.openstack.org/p/juno-neutron-code-review Code Review Process Improvements]
* Wed 11:00-11:40: [https://etherpad.openstack.org/p/neutron-ipv6-atlanta-summit IPv6 status in Neutron]
* Wed 11:50-12:30: [https://etherpad.openstack.org/p/ML2_Juno_Roadmap ML2 Juno Roadmap] and [https://etherpad.openstack.org/p/ML2_mechanismdriver_extensions_support Extensions Support In ML2 Mechanism Drivers]
* Wed 13:50-14:30: Refactoring the Neutron Server Core
* Wed 14:40-15:20: [https://etherpad.openstack.org/p/novanet-neutron-migration Nova-Net to Neutron migration]
* Wed 15:30-14:10: Integrating Tasks into Neutron
* Wed 16:30-17:10: [https://etherpad.openstack.org/p/juno-advanced-services Advanced Services] and [https://etherpad.openstack.org/p/juno-virtual-resource-for-service-chaining Virtual Resource for Service Chaining]
* Wed 17:20-18:00: [https://etherpad.openstack.org/p/Distributed-Virtual-Router Neutron Distributed Virtual Router Progress Update]
* Thu 9:00-9:40: [https://etherpad.openstack.org/p/TempestAndNeutronJuno Neutron QA and Testing]
* Thu 9:50-10:30: [https://etherpad.openstack.org/p/juno-neutron-responsibilities Sharing the load of operational responsibility]
* Thu 11:00-11:40: Neutron LBaaS Update
* Thur 11:50-12:30: [https://etherpad.openstack.org/p/juno-neutron-modular-l2-agent Modular Layer2 Agents]
* Fri 10:50-11:30: [https://etherpad.openstack.org/p/group-based-policy Neutron Group Based Policy]
* Fri 11:40-12:30: [https://etherpad.openstack.org/p/juno-fwaas FWaaS] and [https://etherpad.openstack.org/p/juno-vpnaas VPNaaS]
* Fri 13:20-14:00: LBaaS SSL L7 and automated scenarios
* Fri 14:10-14:50: [https://etherpad.openstack.org/p/hierarchical_network_topology Hierarchical Network Topologies]
* Fri 15:00-15:40: [https://etherpad.openstack.org/p/L3-vendor-plugins L3 Vendor Plugins]
* Fri 16:00-16:40: [https://etherpad.openstack.org/p/juno-dynamic-routing Dynamic routing] and [https://etherpad.openstack.org/p/juno-neutron-pluggable-external-network pluggable external networks]
* Fri 16:50-17:30: [https://etherpad.openstack.org/p/servicevm Service VM Discussion]

== Nova ==

'''Wednesday, May 14'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-third-party-ci Continuation of third party CI]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-clustered-hypervisor-support Clustered hypervisor support in Nova]
* 11:00am [https://etherpad.openstack.org/p/juno-nova-deprecating-baremetal The road to deprecating nova.virt.baremetal]
* 11:50am [https://etherpad.openstack.org/p/juno-nova-data-transfer-service Data transfer service plug-in]
* 1:50pm [https://etherpad.openstack.org/p/juno-nova-live-upgrade Next steps in live upgrade]
* 2:40pm [https://etherpad.openstack.org/p/juno-nova-image-precaching Image precaching service]
* 3:30pm [https://etherpad.openstack.org/p/juno-nova-flavor-storage-revamp Flavor storage re-vamp]
* 4:30pm [https://etherpad.openstack.org/p/juno-nova-cross-project-interactions Rethinking cross project interactions]
* 5:20pm [https://etherpad.openstack.org/p/juno-nova-v2-on-v3-api-poc Nova V2 on V3 API implementation POC]

'''Thursday, May 15'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-hypev-new-features Hyper-V Driver new features]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-libvirt-driver-roadmap Libvirt driver roadmap for Juno]
* 11:00am [https://etherpad.openstack.org/p/juno-nova-kvm-live-migration Improve performance of live migration on KVM]
* 11:50am [https://etherpad.openstack.org/p/juno-nova-conductor-api limited conductor API]
* 1:30pm [https://etherpad.openstack.org/p/juno-nova-quota-state-management Implementing state management for quotas]
* 2:20pm [https://etherpad.openstack.org/p/juno-nova-multi-volume-snapshots Multi-Volume Snapshots]
* 3:10pm [https://etherpad.openstack.org/p/juno-nova-hypervisor-power-mgmt Hypervisor power management]
* 4:10pm [https://etherpad.openstack.org/p/juno-nova-sriov-support SR-IOV support]
* 5:00pm [https://etherpad.openstack.org/p/juno-nova-v3-api Nova V3 API]

'''Friday, May 16'''

* 9:00am [https://etherpad.openstack.org/p/juno-nova-vmware-driver-roadmap Vmwareapi driver roadmap for Juno]
* 9:50am [https://etherpad.openstack.org/p/juno-nova-docker-driver-features Docker driver - features & testing]
* 10:50am [https://etherpad.openstack.org/p/juno-nova-gantt-apis Future of Gantt APIs and interfaces]
* 11:40am [https://etherpad.openstack.org/p/juno-nova-no-db-scheduler Common no DB Scheduler]
* 1:20pm [https://etherpad.openstack.org/p/juno-nova-scheduling-server-groups Simultaneous Scheduling for Server Groups]
* 2:10pm [https://etherpad.openstack.org/p/juno-nova-scheduler-hints-vm-lifecycle Scheduler hints for VM life cycle]
* 3:00pm [https://etherpad.openstack.org/p/juno-nova-devops Nova Dev/Ops Session]
* 4:00pm [https://etherpad.openstack.org/p/juno-nova-unsession Unsession]

== Ops ==
* Mon 1115 – 1155 [https://etherpad.openstack.org/p/juno-summit-ops-askthedevs Ask the devs: Meet the PTLs and TC, How to get the best out of the design summit]
* Mon 1205 – 1245 [https://etherpad.openstack.org/p/juno-summit-ops-reasonabledefaults Reasonable Defaults]
* Mon 1400 – 1440 [https://etherpad.openstack.org/p/juno-summit-ops-upgradesdeployment Upgrades and Deployment Approaches]
* Mon 1450 – 1620 [https://etherpad.openstack.org/p/juno-summit-ops-architecture Architecture Show and Tell, Tales and Fails]
* Mon 1640 – 1720 [https://etherpad.openstack.org/p/juno-summit-ops-networking Networking]
* Mon 1730 – 1810 [https://etherpad.openstack.org/p/juno-summit-ops-security Security]

* Fri 9:00 – 9:40 [https://etherpad.openstack.org/p/juno-summit-ops-enterprise Enterprise Gaps]
* Fri 9:50 – 10:30 [https://etherpad.openstack.org/p/juno-summit-ops-database Database]
* Fri 10:50 – 11:30 [https://etherpad.openstack.org/p/juno-summit-ops-issuesatscale Issues at Scale]
* Fri 11:40 – 12:20 [https://etherpad.openstack.org/p/juno-summit-ops-meta Meta Discussion – ops communication and governance]
* Fri 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-ops-ansible Ansible]
* Fri 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-ops-chef Chef]
* Fri 3:00 – 3:40 [https://etherpad.openstack.org/p/juno-summit-ops-puppet Puppet]
* Fri 4:00 – 4:30 [https://etherpad.openstack.org/p/juno-summit-ops-monitoringlogging Monitoring and Logging]

== Oslo ==
* Wed 9:00 - 9:40 [https://etherpad.openstack.org/p/juno-oslo-release-plan Release Plan for Low-level Libraries]
* Wed 9:50 - 10:30 [https://etherpad.openstack.org/p/juno-oslo-messaging oslo.messaging status and plans for Juno]
* Wed 11:00 - 11:40 [https://etherpad.openstack.org/p/olso.messaging_amqp_1.0 AMQP 1.0 protocol driver]
* Thu 9:00 - 9:40 Oslo Library Teams Breakout Session
* Thu 9:50 - 10:30 [https://etherpad.openstack.org/p/juno-infra-library-testing Testing pre-releases of Oslo libs with apps]
* Thu 11:00 - 11:40 [https://etherpad.openstack.org/p/juno-osprofiler OpenStack cross service/project OpenStack profiler]
* Thu 15:10 - 16:00 [https://etherpad.openstack.org/p/juno-oslo-bayer Upstream chat with Mike Bayer]
* Thu 16:10 - 17:00 [https://etherpad.openstack.org/p/juno-summit-oslo-messaging-rpc-proxy rpc proxy(oslo.messaging)]
* Fri 14:10 - 15:50 [https://etherpad.openstack.org/p/juno-summit-oslo-rootwrap oslo.rootwrap: performance and other improvements]
* Fri 15:00 - 16:40 [https://etherpad.openstack.org/p/juno-oslo-semantic-versioning Semantic versioning and oslo]
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-oslo-pki-for-messaging PKI for messaging]

== QA ==

'''Wednesday'''
* 2:40 – 3:20 [https://etherpad.openstack.org/p/juno-summit-branchless-tempest Branchless Tempest]
* 3:30 – 4:10 [https://etherpad.openstack.org/p/juno-summit-tempest-documentation Tempest Documentation Gaps]
* 4:30 – 5:10 [https://etherpad.openstack.org/p/juno-qa-functional-api Functional API Testing - post dev QA vs TDD]
* 5:20 – 6:00 [https://etherpad.openstack.org/p/juno-rally-and-tempest Rally and Tempest Integration]

'''Thursday'''
* 1:30 – 2:10 [https://etherpad.openstack.org/p/juno-summit-api-tests-with-jsonschema API tests with JSONSchema]
* 2:20 – 3:00 [https://etherpad.openstack.org/p/juno-summit-negative-fuzzy-testing Negative Testing: Fuzzy Test Framework]
* 3:10 – 3:50 [https://etherpad.openstack.org/p/juno-summit-improve-ux-tools How to improve the UX of our Testing Tools]
* 4:10 – 4:50 [https://etherpad.openstack.org/p/juno-summit-tempest-gui-client-server Tempest, GUI, Client, Server]

'''Friday'''
* 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-grenade Grenade Current Status and Next Steps]
* 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-qa-policy QA Program Policy and Changes in Juno]

== Release Management ==

* Wednesday 1:50pm [https://etherpad.openstack.org/p/juno-summit-release-branches Release branches, QA and requirements]
* Thursday 9:00am [https://etherpad.openstack.org/p/juno-summit-vmt Vulnerability management in Juno]
* Thursday 5:00pm [https://etherpad.openstack.org/p/StableIcehouse Stable branches maintenance]
* Friday 3:00pm [https://etherpad.openstack.org/p/juno-summit-release-schedule Juno release schedule and processes]
* Friday 4:50pm [https://etherpad.openstack.org/p/juno-summit-feedback Design Summit feedback]

== Sahara (ex. Savanna) ==

* [http://junodesignsummit.sched.org/event/b4f52627efa42f285978d5af3643e189 Thu 13:30] [https://etherpad.openstack.org/p/juno-summit-sahara-relmngmt-backward Releasing and backward compatibility]
* [http://junodesignsummit.sched.org/event/c8774beefd9e9188a3e0729d2bd7131e Thu 14:20] [https://etherpad.openstack.org/p/juno-summit-sahara-testing-plugins CI/gating and plugin requirements]
* [http://junodesignsummit.sched.org/event/10bc9a23eb43eb9df885586035fb2491 Thu 15:10] [https://etherpad.openstack.org/p/juno-summit-sahara-scale-integration Scalable Sahara and further OpenStack integration]
* [http://junodesignsummit.sched.org/event/be842178a085fe95b7665a653f8ab541 Thu 16:10] [https://etherpad.openstack.org/p/juno-summit-sahara-ux UX improvements]
* [http://junodesignsummit.sched.org/event/dfa603324c0bbf29c2f09a77efb82d1d Thu 17:00] [https://etherpad.openstack.org/p/juno-summit-sahara-edp Future of EDP: plugins, SPI, Oozie]
* [http://junodesignsummit.sched.org/event/a64f771cf28ed3ad637730db828668ff Fri 09:00] [https://etherpad.openstack.org/p/juno-summit-sahara-v2-api Next major REST API - v2]
* [http://junodesignsummit.sched.org/event/49089a1d9c8203c6a4c1f0001fa417af Fri 09:50] [https://etherpad.openstack.org/p/juno-summit-sahara-roadmap-retro Sahara in Icehouse and Juno]

== Swift ==
== TripleO (Deployment) ==
* Fri 11:40 - 12:20 [https://etherpad.openstack.org/p/juno-summit-tripleo-tuskar-planning TripleO Tuskar Planning]
* Fri 13:20 - 14:00 [https://etherpad.openstack.org/p/juno-summit-tripleo-environment TripleO Development and Testing Environment]
* Fri 14:10 - 14:50 [https://etherpad.openstack.org/p/juno-summit-tripleo-and-docker TripleO and Docker]
* Fri 15:00 - 15:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-ci TripleO CI]
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-neutron TripleO and Neutron]
* Fri 16:50 - 17:30 [https://etherpad.openstack.org/p/juno-summit-tripleo-devops TripleO Dev/Ops Session]

== Trove ==
== User Committee ==
== Other Projects ==
* [http://junodesignsummit.sched.org/event/e04c26e2a5df3a5089b2ed701d2aac3b Tue 11:15 - 11:55] [https://etherpad.openstack.org/p/summit-101 Design Summit 101]
* [http://junodesignsummit.sched.org/event/6f9fe2ec2e6d3843139663a350cdc511 Tue 17:30 - 18:10] [https://etherpad.openstack.org/p/juno-summit-discovery-and-diagnostic-for-openstack Discovery and Diagnostic for OpenStack]
* [http://junodesignsummit.sched.org/event/ab6d8eed3c6fd85dc450c099aba22e11 Tue 12:05 - 12:45] [https://etherpad.openstack.org/p/juno-design-summit-designate-session-1 Designate Session 1]
* Tue 16:40 - 19:20 [https://etherpad.openstack.org/p/juno-summit-resource-reservation Climate, Resource Reservation for the OpenStack]
* [http://openstacksummitmay2014atlanta.sched.org/event/6e53527347d56d67120decd49bbac53b Wed 13:50 - 17:20] [https://etherpad.openstack.org/p/SolumSummitAgenda Solum Session]

OpenStack Upstream Training/Info

2014-05-11T20:32:03Z

Dachary: links to slides

== Introduction ==

With over 2000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [http://dachary.org/loic/openstack-training/reviewing.odp slides.odp] [http://dachary.org/loic/openstack-training/reviewing.pdf slides.pdf] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

( [http://dachary.org/loic/openstack-training/training-contribution-process.odp] [http://dachary.org/loic/openstack-training/training-contribution-process.pdf] )
* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

( [http://dachary.org/loic/openstack-training/training-agile-for-contributors.odp] [http://dachary.org/loic/openstack-training/training-agile-for-contributors.pdf] )
* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

( [http://dachary.org/loic/openstack-training/training-student-project-sample.odp] [http://dachary.org/loic/openstack-training/training-student-project-sample.pdf] )

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

OpenStack Upstream Training/Info

2014-04-13T12:30:05Z

Dachary: reviewing moves before the exercise

== Introduction ==

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [http://dachary.org/loic/openstack-training/reviewing.odp slides.odp] [http://dachary.org/loic/openstack-training/reviewing.pdf slides.pdf] )
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message

== Second day ==

=== The Contribution Process (3 hours) ===

* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

OpenStack Upstream Training/Info

2014-04-13T12:26:57Z

Dachary: reviewing slides

== Introduction ==

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [http://dachary.org/loic/openstack-training/reviewing.odp slides.odp] [http://dachary.org/loic/openstack-training/reviewing.pdf slides.pdf] )

== Second day ==

=== The Contribution Process (3 hours) ===

* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

OpenStack Upstream Training/Info

2014-04-13T11:58:55Z

Dachary: jenkins slides

== Introduction ==

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]] ( [http://dachary.org/loic/openstack-training/jenkins.odp slides.odp] [http://dachary.org/loic/openstack-training/jenkins.pdf slides.pdf] )
** Exercise: add an error and match it to the jenkins message
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]]
** [[GerritJenkinsGit#Gerrit_Comment_Formatting|comment formatting]]
** [[GerritJenkinsGit#Gerrit_Best_Practices|use a topic branch]]
** more than one change for a single bug multiple changes

== Second day ==

=== The Contribution Process (3 hours) ===

* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

OpenStack Upstream Training/Info

2014-04-13T11:15:30Z

Dachary: commit message slides

== Introduction ==

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [http://dachary.org/loic/openstack-training/commit-message.odp slides.odp] [http://dachary.org/loic/openstack-training/commit-message.pdf slides.pdf] )
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]]
** Exercise: add an error and match it to the jenkins message
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]]
** [[GerritJenkinsGit#Gerrit_Comment_Formatting|comment formatting]]
** [[GerritJenkinsGit#Gerrit_Best_Practices|use a topic branch]]
** more than one change for a single bug multiple changes

== Second day ==

=== The Contribution Process (3 hours) ===

* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

OpenStack Upstream Training/Info

2014-04-13T10:49:49Z

Dachary: gerrit slides

== Introduction ==

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]] ( [http://dachary.org/loic/openstack-training/gerrit.odp slides.odp] [http://dachary.org/loic/openstack-training/gerrit.pdf slides.pdf] )
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritWorkflow#Committing_Changes|writing a commit message]]
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]]
** Exercise: add an error and match it to the jenkins message
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]]
** [[GerritJenkinsGit#Gerrit_Comment_Formatting|comment formatting]]
** [[GerritJenkinsGit#Gerrit_Best_Practices|use a topic branch]]
** more than one change for a single bug multiple changes

== Second day ==

=== The Contribution Process (3 hours) ===

* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

OpenStack Upstream Training/Info

2014-04-13T08:48:33Z

Dachary: do not include bug selection strategy in the first day

== Introduction ==

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]]
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritWorkflow#Committing_Changes|writing a commit message]]
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]]
** Exercise: add an error and match it to the jenkins message
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]]
** [[GerritJenkinsGit#Gerrit_Comment_Formatting|comment formatting]]
** [[GerritJenkinsGit#Gerrit_Best_Practices|use a topic branch]]
** more than one change for a single bug multiple changes

== Second day ==

=== The Contribution Process (3 hours) ===

* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

OpenStack Upstream Training/Info

2014-04-13T08:45:30Z

Dachary: launchpad slides

== Introduction ==

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad] ( [http://dachary.org/loic/openstack-training/launchpad.odp slides.odp] [http://dachary.org/loic/openstack-training/launchpad.pdf slides.pdf] )
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Selecting a bug
*** age
*** complexity
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]]
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritWorkflow#Committing_Changes|writing a commit message]]
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]]
** Exercise: add an error and match it to the jenkins message
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]]
** [[GerritJenkinsGit#Gerrit_Comment_Formatting|comment formatting]]
** [[GerritJenkinsGit#Gerrit_Best_Practices|use a topic branch]]
** more than one change for a single bug multiple changes

== Second day ==

=== The Contribution Process (3 hours) ===

* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class

Bugs

2014-04-13T08:36:25Z

Dachary: remove extra )

Launchpad bugs are used to track known issues and defects in OpenStack software.

= Bugs reference =

Here are the different fields available in Launchpad bugs, and how we use them within the OpenStack project.

=== Status ===

{| border="1" cellpadding="2" cellspacing="0"
| ''New''
| The bug was just created
|-
| ''Incomplete''
| The bug is waiting on input from the reporter
|-
| ''Confirmed''
| The bug was reproduced or confirmed as a genuine bug
|-
| ''Triaged''
| The bug comments contain a full analysis on how to properly fix the issue
|-
| ''In Progress''
| Work on the fix is in progress, bug has an assignee
|-
| ''Fix Committed''
| The branch containing the fix was merged into master
|-
| ''Fix Released''
| The fix is included in the milestone-proposed branch, a past milestone or a past release
|-
| ''Invalid''
| This is not a bug
|-
| ''Opinion''
| This is a valid issue, but it is the way it should be
|-
| ''Won't Fix''
| This is a valid issue, but we don't intend to fix that
|}

=== Importance ===

This should be set when the status reaches ''Confirmed'' stage. It is a combination of short-term impact (unavailability of a feature), long-term impact (data corruption, security breach), number of people affected, and presence of a documented workaround. Use these as guidelines:

{| border="1" cellpadding="2" cellspacing="0"
| ''Critical''
| Data corruption / complete failure affecting most users, no workaround
|-
|rowspan="2" | ''High''
| Data corruption / complete failure affecting most users, with workaround
|-
| Failure of a significant feature, no workaround
|-
|rowspan="2" | ''Medium''
| Failure of a significant feature, with workaround
|-
| Failure of a fringe feature, no workaround
|-
|rowspan="2" | ''Low''
| Small issue with an easy workaround
|-
| Any other insignificant bug
|-
| ''Wishlist''
| Not really a bug, but a suggested improvement
|-
| ''Undefined''
| Impact was not assessed yet
|}

Note that presence of ''Critical'' bugs will delay the release.

=== Assigned To ===
The person currently working to fix this bug. Must be set by ''In progress'' stage.

=== Milestone ===
The milestone we need to fix the bug for, or the milestone/version it was fixed in.

=== Tags ===
Free-form tags you can use to search bugs with. Here is the list of [[BugTags|official tags]].

= Bugs lifecycle =

Bugs go through multiple stages before final resolution.

=== Reporting ===

When you find a bug, you should file it against the proper OpenStack project using the corresponding link:
* Report a [https://bugs.launchpad.net/nova/+filebug bug in Nova]
* Report a [https://bugs.launchpad.net/glance/+filebug bug in Glance]
* Report a [https://bugs.launchpad.net/swift/+filebug bug in Swift]
* Report a [https://bugs.launchpad.net/horizon/+filebug bug in Horizon]
* Report a [https://bugs.launchpad.net/keystone/+filebug bug in Keystone]
* Report a [https://bugs.launchpad.net/cinder/+filebug bug in Cinder]
* Report a [https://bugs.launchpad.net/neutron/+filebug bug in Neutron]
* Report a [https://bugs.launchpad.net/heat/+filebug bug in Heat]
* Report a [https://bugs.launchpad.net/openstack-manuals/+filebug bug in the manuals]
* Report a [https://bugs.launchpad.net/openstack-api-site/+filebug bug in the api documentation]
* Report a [https://bugs.launchpad.net/openstack-community/+filebug bug in the community tools]

Make sure there is no bug already filed for the same issue, then enter the details of your report. It should at least include:
* The release, or milestone, or commitid corresponding to the software that you are running

When this is done, the bug is created with:

* Status: ''New''

=== Confirming & prioritizing ===

This stage is about checking that a bug is real and assessing its impact. If you are lacking information to properly reproduce or assess the importance of the bug, you should ask the original reporter for more information and set the bug to:

* Status: ''Incomplete''

Once you have reproduced the issue (or are 100% confident that this is indeed a valid bug), you should set:

* Status: ''Confirmed''

If you're a core developer or a member of the project bug supervision team, you should also prioritize the bug:

* Importance: <Bug impact> (see above)

=== Debugging (optional) ===

This optional stage is about determining how to fix the bug and posting the solution in the comments. Sometimes the implementation of the fix will be straightforward and you would jump directly to bugfixing, but in some other cases, you would just post your complete debugging analysis and give someone else the opportunity of fixing the bug. Then you should ask a core developer or bug supervisor to set:

* Status: ''Triaged''

=== Bugfixing ===

At this stage, a developer will work on a fix. During that time, in order to avoid duplicating the work, he should set:

* Status: ''In progress''
* Assignee: <yourself>

When the fix is ready, he will propose the change and get it reviewed.

Note that Gerrit will automatically set the status and assignee when a change is proposed that mentions the bug number.

=== After the change is accepted ===

Once the change is reviewed, accepted, and has landed in master, it will automatically move to:

* Status: ''Fix Committed''

When the fix makes it into a milestone or release branch, it will automatically move to:

* Milestone: Milestone the bug was fixed in
* Status: ''Fix Released''

= See also =
* [[ReleaseCycle]]
* [[Blueprints]]
* [[BugTags]]

OpenStack Upstream Training/Info

2014-04-13T08:19:17Z

Dachary: branching model slides

== Introduction ==

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which newcomers are successful at integrating their own roadmap into that of the OpenStack project.

We've designed a training program to help professional developers negotiate this hurdle. It shows them how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. The educational program requires students to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In a followup session, the students benefit from individual online sessions to help them resolve any remaining problems they might have.

== Objectives ==

* Faster integration of the companies product roadmap into the OpenStack release cycle
* Successfully contribute one real world patch to an OpenStack component
* Master the technical tools
* Understand the OpenStack contribution workflow and social norms

== Target Audience ==

* Developers
* System administrators

== Prerequisites ==

* Being able to read and write English at a technical level.
* If contributing code, being technically proficient enough to carry out simple bug fixes in the project.
* If contributing documentation, being able to produce documents in the project's chosen infrastructure.
* Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.

== Duration ==

* Face-to-face section: 2 days
* Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks

= Course Outline =

== First day ==

=== Introduction ===
* A week before Day 1: choice of a contribution, via email, with each participant
* Day 1: How OpenStack is made
* Day 1: Learn and practice git, gerrit, IRC

* Day 2: The theory of contribution
* Day 2: Lego contribution simulation
* Day 2: Individual presentation of the contribution plan
* Day 2: Online mentoring

=== How OpenStack is made (3h including 1h30 exercises) ===

* [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [http://dachary.org/loic/openstack-training/release-cycle.odp slides.odp] [http://dachary.org/loic/openstack-training/release-cycle.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]
** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]
*** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]
** Exercise: based on the [https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse release schedule] find the URL of a document or a patch that belongs to each of the above steps.
* Relevant actors ( [http://dachary.org/loic/openstack-training/relevant-actors.odp slides.odp] [http://dachary.org/loic/openstack-training/relevant-actors.pdf slides.pdf] )
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] companies
** [http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id= commiters] individuals
** Your management
* [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [http://dachary.org/loic/openstack-training/technical-committee.odp slides.odp] [http://dachary.org/loic/openstack-training/technical-committee.pdf slides.pdf] )
** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]
** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings]
** Exercise: read [http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html archived] and briefly comment on [https://etherpad.openstack.org/p/keystone-incubation-integration-requirements keystone document]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]
** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]
** Exercise: each APC / ATC in the class add a URL to the etherpad proving it
* [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [http://dachary.org/loic/openstack-training/program-ecosystem.odp slides.odp] [http://dachary.org/loic/openstack-training/program-ecosystem.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]
** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]
** [http://ci.openstack.org/stackforge.html Stackforge]
** Exercise: What kind of Program do you contribute to ?
* [https://wiki.openstack.org/wiki/Summit Design summits] ( [http://dachary.org/loic/openstack-training/design-summit.odp slides.odp] [http://dachary.org/loic/openstack-training/design-summit.pdf slides.pdf] )
** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]
** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]
** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals
* [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [http://dachary.org/loic/openstack-training/irc-meetings.odp slides.odp] [http://dachary.org/loic/openstack-training/irc-meetings.pdf slides.pdf] )
** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]
** #info - Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
** #action - Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
** #help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
** Exercise: lunch menu online meeting

<br />

=== Workflow of an OpenStack contribution and tools (3h including 2h exercises) ===

* [http://devstack.org/ devstack] ( [http://dachary.org/loic/openstack-training/devstack.odp slides.odp] [http://dachary.org/loic/openstack-training/devstack.pdf slides.pdf] )
** Ubuntu or Fedora
** git clone https://github.com/openstack-dev/devstack.git
** [http://devstack.org/configuration.html minimal configuration]
** cd devstack; ./stack.sh
** Exercise: get the code for the targeted contribution
* [[How_To_Contribute|HOW to contribute URL]] ( [http://dachary.org/loic/openstack-training/howtocontribute.odp slides.odp] [http://dachary.org/loic/openstack-training/howtocontribute.pdf slides.pdf] )
** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]
** [[Documentation/HowTo|documentation]]
** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]
** Excercise: Apply for individual membership and sign the CLA
* [https://help.launchpad.net/ launchpad]
** [[Blueprints|blueprints]]
** [[Bugs|bugs]]
*** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]
*** [[Bugs#Reporting|reporting a bug]]
*** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]
*** [[Bugs#Debugging_.28optional.29|debugging]]
*** [[Bugs#Bugfixing|bugfixing]]
** Selecting a bug
*** age
*** complexity
** Exercise: review other launchpad bugs and improve yours
* [[GerritWorkflow|gerrit workflow]]
** [[GerritWorkflow#Account_Setup|account setup]]
** [[GerritWorkflow#Git_Review_Installation|git review installation]]
** [[GerritWorkflow#SSH_Setup|ssh setup]]
** [[GerritWorkflow#Project_Setup|project setup]]
** [[GerritWorkflow#Normal_Workflow|gerrit workflow]]
** [[Testing#Unit_Tests|running unit tests]]
** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]
** Exercise: push a wip or draft and invite reviewers
* Branching model ( [http://dachary.org/loic/openstack-training/branching-model.odp slides.odp] [http://dachary.org/loic/openstack-training/branching-model.pdf slides.pdf] )
** [[BranchModel|development]]
** [[StableBranch|stable]]
** Exercise: checkout the latest stable branch
* [[GerritWorkflow#Committing_Changes|writing a commit message]]
** reference to a bug or a blueprint
** amending a commit message
** Exercise: review each other messages on the draft
* [[GerritJenkinsGit|jenkins]]
** Exercise: add an error and match it to the jenkins message
* [[GerritJenkinsGit#Reviewing_a_Change|reviewing]]
** [[GerritJenkinsGit#Gerrit_Comment_Formatting|comment formatting]]
** [[GerritJenkinsGit#Gerrit_Best_Practices|use a topic branch]]
** more than one change for a single bug multiple changes

== Second day ==

=== The Contribution Process (3 hours) ===

* Take the pulse of the project.
* Figure out who's behind it.
* Determine the project's social groups.
* Assess your approach.
* Engage immediately.
* Play with your network.
* Perform the smaller tasks.
* Choose a question.
* Familiarize yourself with the code of conduct.
* Understand the conventions.
* Explain what you do.
* Prepare the backport.
* Learn what's local and what's upstream.
* Learn what distinguishes good work flow from bad work flow.
* Quantify the delta.
* Speed up the acceptance.
* Determine the time frame.
* Maximize karma.
* Work in parallel.
* Archive and collect.

=== Agile for Contributors (15 min) ===

* Apply agile
* Who is the customer?
* Company & Upstream product owner
* Sprint review presentation to Upstream

=== Contribution Simulation (1 hour) ===

The students make a virtual contribution simulation using Lego bricks as props, with the goal of expanding a Lego town, built by upstream. They are divided into teams; the teacher is by turns the product owner in the company and the upstream.

=== Contribution Planning (2 hours) ===

* The students use template slides to prepare a 5-minute presentation of their planned contribution.
* A sample presentation is given by the teacher, as an example.
* Each student group prepares a presentation describing:
** the contribution they plan to work on during the online sessions,
** how they will engage with the Upstream,
** how it contributes to the company's agenda
** and whom they will be working with.
* Each student group presents its slides to the class