https://wiki.openstack.org/w/api.php?action=feedcontributions&feedformat=atom&user=Fdot 2026-06-30T09:47:41Z User contributions MediaWiki 1.28.2 https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=89246 2015-09-01T07:08:55Z

<p>Fdot: </p> <hr /> <div>[[Category:I18n]]<br /> <br /> = Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:bureaufrancois@gmail.com François Bureau]<br /> <br /> == Echanges ==<br /> La communauté française utilise actuellement Slack pour se synchroniser : [https://openstacki18nteam.slack.com https://openstacki18nteam.slack.com].<br /> <br /> Pour y accéder contacter l'un des points de contact ci-dessus<br /> <br /> == Comment nous rejoindre ? ==<br /> <br /> '''Dans le cadre de version Liberty, les outils et le process pour rejoindre la communauté de traducteur change : [https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-translator&amp;redirect=no https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-translator&amp;redirect=no].'''<br /> <br /> '''Toutes les demandes sur Transifex, ne seront plus traitées et les traductions effectuées ne seront plus prises en compte.'''<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Liberty - Horizon Java Script Translations<br /> # Liberty - Horizon Translations<br /> # Liberty - OpenStack Dashboard Translations<br /> # Liberty - OpenStack Dashboard<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : Rw5xHz58LfEzByCZ<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> <br /> == Petit dictionnaire Français ==<br /> <br /> L'objectif de ce petit dictionnaire est de créer une base de mot à réutiliser lors des traductions.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; French:Français<br /> ;aggregate: Aggrégat<br /> ;availability zone: zone de disponibilité<br /> ;backend: Backend =&gt; D'autres propositions ?<br /> ;backup: Sauvegarde<br /> ;cache: cache<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute: Compute<br /> ;container: Conteneur <br /> ;Data Processing: Traitement des données<br /> ;disk: disque<br /> ;domain:Domaine<br /> ;domain group: groupe de domaine<br /> ;Ephemeral Disk: Disque éphémere<br /> ;Ephemeral Drive: Lecteur ephémere<br /> ;flavor: Gabarit<br /> ;floating ip: IP flottante<br /> ;gateway: Passerelle<br /> ;health Monitor: Supervision du statut des services<br /> ;host: Host<br /> ;Host Aggregate: Agrégat de machines<br /> ;hypervisor: Hyperviseur<br /> ;image: Image<br /> ;interface: Interface<br /> ;job: tâche<br /> ;load balancer: Load balancer<br /> ;meter: métriques<br /> ;node: Node<br /> ;over commit: mise à jour<br /> ;plugin: Extension<br /> ;policy: stratégie<br /> ;quota: Quota<br /> ;router: Routeur<br /> ;Security Group: Groupe de sécurité<br /> ;server: Serveur<br /> ;snapshot: Instantané<br /> ;stack: Stack<br /> ;storage: Stockage<br /> ;subnet: Sous-réseau<br /> ;Swap-Disk: disque swap =&gt; D'autres propositions ?<br /> ;tag: tag<br /> ;template: modèle =&gt; D'autres propositions ?<br /> ;Tenant: Tenant<br /> ;token: Token<br /> ;usage: usage<br /> ;volume:Volume</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=82641 2015-06-04T05:54:55Z

<p>Fdot: </p> <hr /> <div>[[Category:I18n]]<br /> <br /> = Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:bureaufrancois@gmail.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> == Echanges ==<br /> La communauté française utilise actuellement Slack pour se synchroniser : [https://openstacki18nteam.slack.com https://openstacki18nteam.slack.com].<br /> <br /> Pour y accéder contacter l'un des points de contact ci-dessus<br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Liberty - Horizon Java Script Translations<br /> # Liberty - Horizon Translations<br /> # Liberty - OpenStack Dashboard Translations<br /> # Liberty - OpenStack Dashboard<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : Rw5xHz58LfEzByCZ<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> <br /> == Petit dictionnaire Français ==<br /> <br /> L'objectif de ce petit dictionnaire est de créer une base de mot à réutiliser lors des traductions.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; French:Français<br /> ;aggregate: Aggrégat<br /> ;availability zone: zone de disponibilité<br /> ;backend: Backend =&gt; D'autres propositions ?<br /> ;backup: Sauvegarde<br /> ;cache: cache<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute: Compute<br /> ;container: Conteneur <br /> ;Data Processing: Traitement des données<br /> ;disk: disque<br /> ;domain:Domaine<br /> ;domain group: groupe de domaine<br /> ;Ephemeral Disk: Disque éphémere<br /> ;Ephemeral Drive: Lecteur ephémere<br /> ;flavor: Gabarit<br /> ;floating ip: IP flottante<br /> ;gateway: Passerelle<br /> ;health Monitor: Supervision du statut des services<br /> ;host: Host<br /> ;Host Aggregate: Agrégat de machines<br /> ;hypervisor: Hyperviseur<br /> ;image: Image<br /> ;interface: Interface<br /> ;job: tâche<br /> ;load balancer: Load balancer<br /> ;meter: métriques<br /> ;node: Node<br /> ;over commit: mise à jour<br /> ;plugin: Extension<br /> ;policy: stratégie<br /> ;quota: Quota<br /> ;router: Routeur<br /> ;Security Group: Groupe de sécurité<br /> ;server: Serveur<br /> ;snapshot: Instantané<br /> ;stack: Stack<br /> ;storage: Stockage<br /> ;subnet: Sous-réseau<br /> ;Swap-Disk: disque swap =&gt; D'autres propositions ?<br /> ;tag: tag<br /> ;template: modèle =&gt; D'autres propositions ?<br /> ;Tenant: Tenant<br /> ;token: Token<br /> ;usage: usage<br /> ;volume:Volume</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=81564 2015-05-20T23:24:46Z

<p>Fdot: </p> <hr /> <div>[[Category:I18n]]<br /> <br /> === Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable sortable centre&quot; style=&quot;text-align: center;&quot;<br /> |- <br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | OpenStack Manuals || admin-guide-cloud || Documentation || Developers || ??? || 3 - Low || <br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1 - High || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 3 - Low || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 3 - Low || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || arch-design || Documentation || Developers || ??? || 3 - Low || <br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 2 - Medium || Config tables will be moved out of common into config-reference. Content is used by other books, especially translate preface and support appendix (ch_preface.xml and app_support.xml)!<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || hot-reference || Documentation || End users || ??? || 1 - High || <br /> |-<br /> | OpenStack Manuals || glossary || Documentation || Common || Stable || 1 - High || 08/21/2014 - Waiting for a feedback from the doc team about the content of the Glossary<br /> |-<br /> | OpenStack Manuals || openstack-ops || Documentation || End users || Becoming Stable || 3 - Low || <br /> |-<br /> | OpenStack Manuals || admin-guide-cloud || Documentation || Admin || Unstable || 3 - Low || <br /> |-<br /> | OpenStack Manuals || config-reference || Documentation || Admin || Unstable || 3 - Low || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || image-guide || Documentation || End users || Becoming Stable || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || security-guide || Documentation || Admin || Becoming Stable || 3 - Low || <br /> |-<br /> | OpenStack Manuals || upgrade-guide || Documentation || Admin || ??? || 3 - Low || <br /> |-<br /> | OpenStack Manuals || arch-design || Documentation || Admin || Unstable || 3 - Low || <br /> |-<br /> | OpenStack Manuals || networking-guide || Documentation || Admin || Unstable - draft || 4 - Do not translate yet || <br /> |-<br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81375 2015-05-16T21:19:20Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning Propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://docs.openstack.org/infra/system-config/irc.html IRC Services] <br /> ** [http://wiki.debian.org/MeetBot meetbot]<br /> ** [https://wiki.openstack.org/wiki/IRC OpenStack IRC channels]<br /> ** [http://eavesdrop.openstack.org/irclogs/ IRC Logs]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * How to contribute ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** [http://docs.openstack.org/infra/manual/developers.html Developer’s Guide]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#account-setup Account setup]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#installing-git-review Git review installation]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#starting-work-on-a-new-repository Starting Work on a New Repository]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#running-unit-tests Running unit tests]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#cross-repository-dependencies Cross-Repository Dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[Branch_Model|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [http://docs.openstack.org/infra/manual/developers.html#code-review Code Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [http://docs.openstack.org/infra/manual/developers.html#peer-review Peer Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/GitCommitMessages Git Commit Good Practice]<br /> ** Gerrit Documentation: [https://review.openstack.org/Documentation/intro-quick.html Gerrit Code Review - A Quick Introduction]<br /> ** Gerrit Documentation: [https://review.openstack.org/Documentation/intro-quick.html#_reviewing_the_change Reviewing the Change]<br /> ** Exercise: review each other messages on the draft<br /> * [http://docs.openstack.org/infra/manual/developers.html#automated-testing Jenkins (Automated Testing)] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81374 2015-05-16T21:16:18Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning Propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://docs.openstack.org/infra/system-config/irc.html IRC Services] <br /> ** [http://wiki.debian.org/MeetBot meetbot]<br /> ** [https://wiki.openstack.org/wiki/IRC OpenStack IRC channels]<br /> ** [http://eavesdrop.openstack.org/irclogs/ IRC Logs]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html Developer’s Guide] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** [http://docs.openstack.org/infra/manual/developers.html#account-setup Account setup]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#installing-git-review Git review installation]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#starting-work-on-a-new-repository Starting Work on a New Repository]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#running-unit-tests Running unit tests]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#cross-repository-dependencies Cross-Repository Dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[Branch_Model|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [http://docs.openstack.org/infra/manual/developers.html#code-review Code Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [http://docs.openstack.org/infra/manual/developers.html#peer-review Peer Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/GitCommitMessages Git Commit Good Practice]<br /> ** Gerrit Documentation: [https://review.openstack.org/Documentation/intro-quick.html Gerrit Code Review - A Quick Introduction]<br /> ** Gerrit Documentation: [https://review.openstack.org/Documentation/intro-quick.html#_reviewing_the_change Reviewing the Change]<br /> ** Exercise: review each other messages on the draft<br /> * [http://docs.openstack.org/infra/manual/developers.html#automated-testing Jenkins (Automated Testing)] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81373 2015-05-16T21:13:15Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning Propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://docs.openstack.org/infra/system-config/irc.html IRC Services] <br /> ** [http://wiki.debian.org/MeetBot meetbot]<br /> ** [https://wiki.openstack.org/wiki/IRC OpenStack IRC channels]<br /> ** [http://eavesdrop.openstack.org/irclogs/ IRC Logs]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html Developer’s Guide] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** [http://docs.openstack.org/infra/manual/developers.html#account-setup Account setup]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#installing-git-review Git review installation]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#starting-work-on-a-new-repository Starting Work on a New Repository]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#running-unit-tests Running unit tests]<br /> ** [http://docs.openstack.org/infra/manual/developers.html#cross-repository-dependencies Cross-Repository Dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [http://docs.openstack.org/infra/manual/developers.html#code-review Code Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [http://docs.openstack.org/infra/manual/developers.html#peer-review Peer Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/GitCommitMessages Git Commit Good Practice]<br /> ** Gerrit Documentation: [https://review.openstack.org/Documentation/intro-quick.html Gerrit Code Review - A Quick Introduction]<br /> ** Gerrit Documentation: [https://review.openstack.org/Documentation/intro-quick.html#_reviewing_the_change Reviewing the Change]<br /> ** Exercise: review each other messages on the draft<br /> * [http://docs.openstack.org/infra/manual/developers.html#automated-testing Jenkins (Automated Testing)] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81372 2015-05-16T20:57:43Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning Propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://docs.openstack.org/infra/system-config/irc.html IRC Services] <br /> ** [http://wiki.debian.org/MeetBot meetbot]<br /> ** [https://wiki.openstack.org/wiki/IRC OpenStack IRC channels]<br /> ** [http://eavesdrop.openstack.org/irclogs/ IRC Logs]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [http://docs.openstack.org/infra/manual/developers.html#code-review Code Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [http://docs.openstack.org/infra/manual/developers.html#peer-review Peer Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/GitCommitMessages Git Commit Good Practice]<br /> ** Gerrit documentation: [https://review.openstack.org/Documentation/intro-quick.html#_reviewing_the_change Reviewing the Change]<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81371 2015-05-16T20:53:20Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning Propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://docs.openstack.org/infra/system-config/irc.html IRC Services] <br /> ** [http://wiki.debian.org/MeetBot meetbot]<br /> ** [https://wiki.openstack.org/wiki/IRC OpenStack IRC channels]<br /> ** [http://eavesdrop.openstack.org/irclogs/ IRC Logs]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [http://docs.openstack.org/infra/manual/developers.html#code-review Code Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [http://docs.openstack.org/infra/manual/developers.html#peer-review Peer Review] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/GitCommitMessages Git Commit Good Practice]<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81370 2015-05-16T19:30:09Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning Propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://docs.openstack.org/infra/system-config/irc.html IRC Services] <br /> ** [http://wiki.debian.org/MeetBot meetbot]<br /> ** [https://wiki.openstack.org/wiki/IRC OpenStack IRC channels]<br /> ** [http://eavesdrop.openstack.org/irclogs/ IRC Logs]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81369 2015-05-16T19:29:15Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning Propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://docs.openstack.org/infra/system-config/irc.html IRC Services] <br /> ** [http://wiki.debian.org/MeetBot meetbot]<br /> ** [https://wiki.openstack.org/wiki/IRC OpenStack IRC channel]<br /> ** [http://eavesdrop.openstack.org/irclogs/ IRC Logs]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81368 2015-05-16T19:25:47Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning Propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://docs.openstack.org/infra/system-config/irc.html IRC Services] <br /> ** [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81367 2015-05-16T19:20:52Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Design_Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Planning propose sessions]<br /> ** [https://libertydesignsummit.sched.org/overview/type/design+summit#.VVeYTt-uNNw List of sessions]<br /> ** [https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads Liberty Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81366 2015-05-16T19:13:37Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore Understanding the DefCore Guidelines]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]<br /> ** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]<br /> ** [https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads Kilo Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81365 2015-05-16T19:07:58Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [http://governance.openstack.org/reference/new-projects-requirements.html &quot;Big Tent&quot; and tags] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/tags/index.html List of approved tags]<br /> ** [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst Core Definition]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** [http://docs.openstack.org/infra/manual/creators.html How to add a project to Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]<br /> ** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]<br /> ** [https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads Kilo Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81364 2015-05-16T18:31:55Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [http://governance.openstack.org/ OpenStack Governance] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** [http://governance.openstack.org/reference/charter.html Technical Committee]<br /> ** The role of the [http://governance.openstack.org/reference/charter.html#mission Technical Committee]<br /> ** [http://governance.openstack.org/reference/charter.html#openstack-project-teams OpenStack Project Teams]<br /> ** [http://governance.openstack.org/reference/projects/index.html OpenStack Project Teams list]<br /> ** [https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting Meetings] <br /> ** 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]<br /> ** [http://governance.openstack.org/reference/charter.html#project-team-leads PTLs]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc APC]<br /> ** [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> <br /> * [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> <br /> * [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]<br /> ** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]<br /> ** [https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads Kilo Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81363 2015-05-16T17:30:45Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=kilo&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]<br /> ** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings] <br /> ** 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]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]<br /> ** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]<br /> ** [https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads Kilo Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81362 2015-05-16T17:27:11Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://wiki.openstack.org/wiki/Kilo_Release_Schedule Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=juno&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=juno&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]<br /> ** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings] <br /> ** 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]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]<br /> ** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]<br /> ** [https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads Kilo Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81361 2015-05-16T17:25:46Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** Exercise: based on the [https://github.com/openstack/training-guides.git Kilo release schedule] find the URL of a document or a patch that belongs to each of the above steps.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=juno&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=juno&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]<br /> ** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings] <br /> ** 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]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]<br /> ** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]<br /> ** [https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads Kilo Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Training/Info&diff=81360 2015-05-16T17:07:05Z

<p>Fdot: </p> <hr /> <div>&lt;translate&gt;<br /> <br /> == Introduction == &lt;!--T:1--&gt; <br /> <br /> &lt;!--T:2--&gt;<br /> 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.<br /> <br /> &lt;!--T:3--&gt;<br /> 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.<br /> <br /> == Objectives == &lt;!--T:4--&gt; <br /> <br /> &lt;!--T:5--&gt;<br /> * Faster integration of the companies product roadmap into the OpenStack release cycle<br /> * Successfully contribute one real world patch to an OpenStack component<br /> * Master the technical tools<br /> * Understand the OpenStack contribution workflow and social norms<br /> <br /> == Target Audience == &lt;!--T:6--&gt; <br /> <br /> &lt;!--T:7--&gt;<br /> * Developers<br /> * System administrators<br /> <br /> == Prerequisites == &lt;!--T:8--&gt; <br /> <br /> &lt;!--T:9--&gt;<br /> * Being able to read and write English at a technical level.<br /> * If contributing code, being technically proficient enough to carry out simple bug fixes in the project.<br /> * If contributing documentation, being able to produce documents in the project's chosen infrastructure.<br /> * Having at least 8 hours a week to dedicate to the project, be it through programming or through interacting with the community.<br /> <br /> == Duration == &lt;!--T:10--&gt; <br /> <br /> &lt;!--T:11--&gt;<br /> * Face-to-face section: 2 days<br /> * Online section: 10 one-hour individual mentoring sessions over a period of 4 to 10 weeks<br /> <br /> == Infrastructure == &lt;!--T:12--&gt; <br /> <br /> &lt;!--T:13--&gt;<br /> [[OpenStack_Upstream_Training/Setup_DevStack|ready to use devstack VM]] for participants with network connectivity but troubles with their laptop<br /> <br /> = Course Outline = &lt;!--T:14--&gt; <br /> <br /> == First day == &lt;!--T:15--&gt; <br /> <br /> === Introduction === &lt;!--T:16--&gt; <br /> <br /> &lt;!--T:17--&gt;<br /> * A week before Day 1: choice of a contribution, via email, with each participant<br /> * Day 1: How OpenStack is made<br /> * Day 1: Learn and practice git, gerrit, IRC<br /> <br /> &lt;!--T:18--&gt;<br /> * Day 2: The theory of contribution<br /> * Day 2: Lego contribution simulation<br /> * Day 2: Individual presentation of the contribution plan<br /> * Day 2: Online mentoring<br /> <br /> === How OpenStack is made (3h including 1h30 exercises) === &lt;!--T:19--&gt; <br /> <br /> &lt;!--T:20--&gt;<br /> * [https://wiki.openstack.org/wiki/Release_Cycle Release cycle] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/01-release-cycle.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Planning_.28Design.2C_Discuss_and_Target.29 Planning (Design, Discuss and Target)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Implementation_.28Milestone_iterations.29 Implementation (Milestone iterations)]<br /> ** [https://wiki.openstack.org/wiki/Release_Cycle#Pre-release_.28Release_Candidates_dance.29 Pre-release (Release Candidates dance)]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_candidate_1 Release candidate 1]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Other_release_candidates Other release candidates]<br /> *** [https://wiki.openstack.org/wiki/Release_Cycle#Release_day Release day]<br /> ** 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.<br /> * Relevant actors ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/02-relevant-actors.rst slides] )<br /> ** [http://www.stackalytics.com/?release=juno&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] companies<br /> ** [http://www.stackalytics.com/?release=juno&amp;metric=commits&amp;project_type=integrated&amp;module=&amp;company=&amp;user_id= commiters] individuals (bottom of the page)<br /> ** Your management<br /> * [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee Technical Committee] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/03-technical-committee.rst slides] )<br /> ** Decide what is an [https://wiki.openstack.org/wiki/Programs OpenStack Program]<br /> ** [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee meetings] <br /> ** 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]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Program_Leads PTLs]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_PTL_seats_.28.22APC.22.29 APC]<br /> ** [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee#Voters_for_TC_seats_.28.22ATC.22.29 ATC]<br /> ** Exercise: each APC / ATC in the class add a URL to the etherpad proving it<br /> * [https://wiki.openstack.org/wiki/Governance/NewProjects Program ecosystem] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/04-program-ecosystem.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Incubation Incubated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Integrated Integrated]<br /> ** [https://wiki.openstack.org/wiki/Governance/NewProjects#Core_.3F Core]<br /> ** [http://ci.openstack.org/stackforge.html Stackforge]<br /> ** Exercise: What kind of Program do you contribute to ?<br /> * [https://wiki.openstack.org/wiki/Summit Design summits] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/05-design-summit.rst slides] )<br /> ** [https://wiki.openstack.org/wiki/Summit#Propose_sessions propose sessions]<br /> ** [https://wiki.openstack.org/wiki/Summit#At_the_Design_Summit attend or lead a session]<br /> ** [https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads Kilo Summit Etherpads]<br /> ** Exercise: Add a session proposal regarding your contribution in an etherpad, review two proposals<br /> * [https://wiki.openstack.org/wiki/Meetings IRC meetings] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/06-irc-meetings.rst slides] )<br /> ** [http://ci.openstack.org/meetbot.html modified] [http://wiki.debian.org/MeetBot meetbot]<br /> ** #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. <br /> ** #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) <br /> ** #help - Add a &quot;Call for Help&quot; 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)<br /> ** Exercise: lunch menu online meeting<br /> <br /> === Workflow of an OpenStack contribution and tools (3h including 2h exercises) === &lt;!--T:21--&gt; <br /> <br /> &lt;!--T:22--&gt;<br /> * [http://devstack.org/ devstack] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/11-devstack.rst slides] )<br /> ** Ubuntu or Fedora<br /> ** git clone https://github.com/openstack-dev/devstack.git<br /> ** [http://devstack.org/configuration.html minimal configuration]<br /> ** cd devstack; ./stack.sh<br /> ** Exercise: get the code for the targeted contribution<br /> * [[How_To_Contribute|HOW to contribute URL]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/12-howtocontribute.rst slides] )<br /> ** [[Puppet-openstack#Contributing_to_the_modules|puppet stackforge]]<br /> ** [[Documentation/HowTo|documentation]]<br /> ** [http://docs.openstack.org/training-guides/content/under-construction.html training guides]<br /> ** Excercise: Apply for individual membership and sign the CLA<br /> * [https://help.launchpad.net/ launchpad] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/13-launchpad.rst slides] )<br /> ** [[Blueprints|blueprints]]<br /> ** [[Bugs|bugs]]<br /> *** [[Bugs#Bugs_reference|Status, Importance, Assigned To, Milestone, Tags]]<br /> *** [[Bugs#Reporting|reporting a bug]]<br /> *** [[Bugs#Confirming_.26_prioritizing|confirming and prioritizing]]<br /> *** [[Bugs#Debugging_.28optional.29|debugging]]<br /> *** [[Bugs#Bugfixing|bugfixing]]<br /> ** Exercise: review other launchpad bugs and improve yours<br /> * [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/14-gerrit.rst slides] )<br /> ** account setup<br /> ** git review installation<br /> ** ssh setup<br /> ** project setup<br /> ** Development Workflow<br /> ** [[Testing#Unit_Tests|running unit tests]]<br /> ** [http://www.mediawiki.org/wiki/Gerrit/Advanced_usage review dependencies]<br /> ** Exercise: push a wip or draft and invite reviewers<br /> * Branching model ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/15-branching-model.rst slides] )<br /> ** [[BranchModel|development]]<br /> ** [[StableBranch|stable]]<br /> ** Exercise: checkout the latest stable branch<br /> * [[GerritJenkinsGit#Reviewing_a_Change|reviewing]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/16-reviewing.rst slides] )<br /> * [[GerritWorkflow#Committing_Changes|writing a commit message]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/17-commit-message.rst slides] )<br /> ** reference to a bug or a blueprint<br /> ** amending a commit message<br /> ** Exercise: review each other messages on the draft<br /> * [[GerritJenkinsGit|jenkins]] ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/18-jenkins.rst slides] )<br /> ** Exercise: add an error and match it to the jenkins message<br /> <br /> == Second day == &lt;!--T:23--&gt; <br /> <br /> === The Contribution Process (1 hour) === &lt;!--T:24--&gt; <br /> <br /> &lt;!--T:25--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/19-training-contribution-process.rst slides] )<br /> * Take the pulse of the project.<br /> * Figure out who's behind it.<br /> * Determine the project's social groups.<br /> * Assess your approach.<br /> * Engage immediately.<br /> * Play with your network.<br /> * Perform the smaller tasks.<br /> * Choose a question.<br /> * Familiarize yourself with the code of conduct.<br /> * Understand the conventions.<br /> * Explain what you do.<br /> * Prepare the backport.<br /> * Learn what's local and what's upstream.<br /> * Learn what distinguishes good work flow from bad work flow.<br /> * Quantify the delta.<br /> * Speed up the acceptance.<br /> * Determine the time frame.<br /> * Maximize karma.<br /> * Work in parallel.<br /> * Archive and collect.<br /> <br /> === Agile for Contributors (15 min) === &lt;!--T:26--&gt; <br /> <br /> &lt;!--T:27--&gt;<br /> ( [https://github.com/openstack/training-guides/blob/master/doc/upstream-training/source/20-training-agile-for-contributors.rst slides] )<br /> * Apply agile<br /> * Who is the customer?<br /> * Company &amp; Upstream product owner<br /> * Sprint review presentation to Upstream<br /> <br /> === Contribution Simulation (2 hour) === &lt;!--T:28--&gt; <br /> <br /> &lt;!--T:29--&gt;<br /> 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.<br /> <br /> === Contribution Planning (2 hours) === &lt;!--T:30--&gt; <br /> <br /> &lt;!--T:31--&gt;<br /> ( [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] )<br /> <br /> <br /> &lt;!--T:32--&gt;<br /> * The students use template slides to prepare a 5-minute presentation of their planned contribution.<br /> * A sample presentation is given by the teacher, as an example.<br /> * Each student group prepares a presentation describing:<br /> ** the contribution they plan to work on during the online sessions,<br /> ** how they will engage with the Upstream,<br /> ** how it contributes to the company's agenda<br /> ** and whom they will be working with.<br /> * Each student group presents its slides to the class<br /> <br /> === Etherpad === &lt;!--T:33--&gt;<br /> <br /> &lt;!--T:34--&gt;<br /> https://etherpad.openstack.org/p/upstream-training-vancouver<br /> <br /> &lt;/translate&gt;</div>

Fdot https://wiki.openstack.org/w/index.php?title=OldMentorListing&diff=81337 2015-05-15T19:35:10Z

<p>Fdot: </p> <hr /> <div><br /> Good mentorship is a cornerstone of this program. These resources are very useful for prospective mentors to review prior to adding their name to the table below:<br /> <br /> * [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/index.html Federico Mena-Quintero's Mentoring HOWTO]<br /> * [https://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Google Summer of Code mentors]<br /> * [https://flossmanuals.net/GSoCMentoring/ Google Summer of Code Mentor's Guide]<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Name !! Area of expertise !! Availability !! Contact !! Program <br /> |-<br /> | Davanum Srinivas || Oslo, Nova || 1 or 2 hours per week (EDT) || IRC nick - dims || <br /> |-<br /> | Joshua Harlow || TaskFlow, Oslo, Anvil, Cloud-Init; Parts of Cinder, Doc8, ... || 3 or 4 hours per week (PDT) || IRC nick - harlowja ||<br /> |-<br /> | Ajaya Agrawal || Keystone || 1 or 2 hours per week (IST) || IRC nick - ajayaa ||<br /> |-<br /> | Rossella Sblendido || Neutron || 2 hours per week (CET) || IRC nick - rossella_s ||<br /> |-<br /> | Baohua Yang || Neutron, Oslo || 2 hours per week (CCT) || IRC nick - baohua || <br /> |-<br /> | Ghe Rivero || TripleO, Ironic || 3 or 4 hours per week (CEST) || IRC nick - GheRivero ||<br /> |-<br /> | Sean Roberts || Training, Congress, General || 3 or 4 hours per week (PDT) || IRC nick - sarob ||<br /> |-<br /> | Ilya Sviridov || MagnetoDB || 3 or 4 hours per week (EEST) || IRC nick - isviridov ||<br /> |-<br /> | Joshua Hesketh || Infrastructure, 3rd party CI || Australian time || IRC nick - jhesketh ||<br /> |-<br /> | Fawad Khaliq || Neutron, Designate, 3rd party CI || 2 hours per week (PST) || IRC nick - fawadkhaliq ||<br /> |-<br /> | Boris Pavlovic || Rally || 3 or 4 hours per week (All TZ) || IRC nick - boris-42 ||<br /> |-<br /> | Edgar Magana || Neutron, Nova, 3rd party CI || 1 or 2 hours per week (PST) || IRC nick - emagana || <br /> |-<br /> | Dolph Mathews || Keystone || 1 or 2 hours per week (CT) || IRC nick - dolphm ||<br /> |-<br /> | Sylvain Bauza || Nova || 1 hour per week (CET) || IRC nick - bauzas || Upstream<br /> |-<br /> | John Garbutt || Nova || UK time || IRC nick - johnthetubaguy ||<br /> |-<br /> | Lana Brindley || Documentation || Australian time || IRC nick - loquacities ||<br /> |-<br /> | Spencer Krum || Infra, Puppet || Pacific Time || IRC nick - nibalizer ||<br /> |-<br /> | Stefano Maffulli || Community || Pacific time || IRC nick - reed || GSoC, Outreachy, Upstream<br /> |-<br /> | Victoria Martínez de la Cruz || Zaqar, Trove || 4 hours per week (ART) || IRC nick - vkmc || GSoC, Outreachy, Upstream<br /> |-<br /> | David Lyle || Horizon || Mountain Time, US || IRC nick - david-lyle || <br /> |-<br /> | Jeremy Stanley || Project Infrastructure || Americas/Eastern (EST/EDT) || IRC nick - fungi || All<br /> |-<br /> | Elizabeth K. Joseph || Project Infrastructure || Americas/Pacific (PST/PDT) || IRC nick - pleia2 || Outreachy<br /> |-<br /> | Jonathan Harker || Project Infrastructure || Americas/Pacific (PST/PDT) || IRC nick - jesusaurus || <br /> |-<br /> | François Bureau || Translation || 1 hour per week (FR Time) || IRC nick - Fdot || Upstream<br /> |}<br /> <br /> New comers are welcome to ask questions in irc://irc.freenode.net/#openstack-101<br /> <br /> = How to identify newcomers = <br /> <br /> The easiest thing to do at the moment is to look at the reviews done by the special agent &quot;[http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/welcome_message.py Welcome new contributor]&quot;:<br /> <br /> * [https://review.openstack.org/#/q/reviewer:%22Welcome%252C+new+contributor!%22+status:open,p,00312ead0001b310 open reviews]<br /> * [https://review.openstack.org/#/q/reviewer:%22Welcome%252C+new+contributor!%22+status:abandoned,p,00312ead0001b310 abandoned reviews]<br /> <br /> [[Category: Internship]]</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Institute&diff=77927 2015-04-21T15:02:37Z

<p>Fdot: </p> <hr /> <div>&lt;languages /&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:1--&gt;<br /> With over 1000 developers from 130 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.<br /> <br /> &lt;!--T:2--&gt;<br /> 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. <br /> <br /> &lt;!--T:3--&gt;<br /> [[OpenStack_Upstream_Training/Info|More details]]<br /> <br /> = When &amp; Where to get OpenStack Upstream Training = &lt;!--T:4--&gt;<br /> <br /> &lt;!--T:5--&gt;<br /> Next session of the [http://www.eventbrite.com/e/openstack-upstream-training-vancouver-tickets-15649117933 OpenStack Upstream Training will be in Vancouver], before the OpenStack Summit. <br /> <br /> &lt;!--T:6--&gt;<br /> Meeting Room 10, 11 &amp; 12, VANCOUVER CONVENTION CENTRE, 1055 Canada Place, Vancouver, Canada, BC V6C 0C3<br /> <br /> &lt;!--T:7--&gt;<br /> Saturday, May 16, 2015 at 9:30 AM to 5:00 PM - Sunday, May 17, 2015 at 9:30 AM to 5:00 PM (PDT)<br /> <br /> &lt;!--T:8--&gt;<br /> Bring a laptop with wifi + 4GB RAM Ubuntu virtual machine<br /> <br /> = How to prepare = &lt;!--T:9--&gt;<br /> <br /> &lt;!--T:10--&gt;<br /> * Make sure you have a wifi enabled laptop with you.<br /> * Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.<br /> * Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.<br /> * Get in touch with Loic Dachary &lt;loic@dachary.org&gt; to pick a contribution to work on.<br /> &lt;/translate&gt;<br /> <br /> = Staff =<br /> <br /> Stefano Maffulli, Chris Ricker, Tim Freund and Sylvain Bauza will lead the next training in Vancouver, in English. Add yourself to the list of [[mentors]], too. Tools and processes for mentors and staff are kept on the [[OpenStack_Upstream_Training/Admin| admin]] page.<br /> <br /> * Tim Freund &lt;tim@freunds.net&gt; (training, assistant, english)<br /> * Chris Ricker &lt;chris.ricker@gmail.com&gt; (training, mentoring, assistant, english)<br /> * Sylvain Bauza &lt;sbauza@redhat.com&gt; (assistant, mentoring, training, french, english)<br /> * Lana Brindley (assistant, mentoring, English)<br /> * Rossella Sblendido (assistant, Italian, English)<br /> * Victoria Martínez de la Cruz &lt;victoria@vmartinezdelacruz.com&gt; (assistant, english)<br /> * Takashi Torii &lt;t-torii@ce.jp.nec.com&gt; (assistant, japanese)<br /> * KATO Tomoyuki &lt;kato.tomoyuki@jp.fujitsu.com&gt; (assistant, Japanese)<br /> * macJack &lt;macjacktw@hotmail.com&gt; (assistant, English, Chinese)<br /> * François Bureau &lt;francois.bureau@cloudwatt&gt; (assistant, french, english) - irc : Fdot</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=77913 2015-04-21T10:14:08Z

<p>Fdot: /* Terminologie */</p> <hr /> <div>[[Category:I18n]]<br /> <br /> = Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Kilo - Horizon Java Script Translations<br /> # Kilo - Horizon Translations<br /> # Kilo - OpenStack Dashboard Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : Rw5xHz58LfEzByCZ<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> <br /> == Petit dictionnaire Français ==<br /> <br /> L'objectif de ce petit dictionnaire est de créer une base de mot à réutiliser lors des traductions.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; French:Français<br /> ;aggregate: Aggrégat<br /> ;availability zone: zone de disponibilité<br /> ;backend: Backend =&gt; D'autres propositions ?<br /> ;backup: Sauvegarde<br /> ;cache: cache<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute: Compute<br /> ;container: Conteneur <br /> ;Data Processing: Traitement des données<br /> ;disk: disque<br /> ;domain:Domaine<br /> ;domain group: groupe de domaine<br /> ;Ephemeral Disk: Disque éphémere<br /> ;Ephemeral Drive: Lecteur ephémere<br /> ;flavor: Gabarit<br /> ;floating ip: IP flottante<br /> ;gateway: Passerelle<br /> ;health Monitor: Supervision du statut des services<br /> ;host: Host<br /> ;Host Aggregate: Agrégat de machines<br /> ;hypervisor: Hyperviseur<br /> ;image: Image<br /> ;interface: Interface<br /> ;job: tâche<br /> ;load balancer: Load balancer<br /> ;meter: métriques<br /> ;node: Node<br /> ;over commit: mise à jour<br /> ;plugin: Extension<br /> ;policy: stratégie<br /> ;quota: Quota<br /> ;router: Routeur<br /> ;Security Group: Groupe de sécurité<br /> ;server: Serveur<br /> ;snapshot: Instantané<br /> ;stack: Stack<br /> ;storage: Stockage<br /> ;subnet: Sous-réseau<br /> ;Swap-Disk: disque swap =&gt; D'autres propositions ?<br /> ;tag: tag<br /> ;template: modèle =&gt; D'autres propositions ?<br /> ;Tenant: Tenant<br /> ;token: Token<br /> ;usage: usage<br /> ;volume:Volume</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=77912 2015-04-21T10:13:29Z

<p>Fdot: </p> <hr /> <div>[[Category:I18n]]<br /> <br /> = Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Kilo - Horizon Java Script Translations<br /> # Kilo - Horizon Translations<br /> # Kilo - OpenStack Dashboard Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : Rw5xHz58LfEzByCZ<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> <br /> == Petit dictionnaire Français ==<br /> <br /> L'objectif de ce petit dictionnaire est de créer une base de mot à réutiliser lors des traductions.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; French:Français<br /> ;aggregate: Aggrégat<br /> ;availability zone: zone de disponibilité<br /> ;backend: Backend =&gt; D'autres propositions ?<br /> ;backup: Sauvegarde<br /> ;cache: cache<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute: Compute<br /> ;container: Conteneur <br /> ;Data Processing: Traitement des données<br /> ;disk: disque<br /> ;domain:Domaine<br /> ;domain group: groupe de domaine<br /> ;Ephemeral Disk: Disque éphémere<br /> ;Ephemeral Drive: Lecteur ephémere<br /> ;flavor: Gabarit<br /> ;floating ip: IP flottante<br /> ;gateway: Passerelle<br /> ;health Monitor: Supervision du statut des services<br /> ;host: Host<br /> ;Host Aggregate: Agrégat de machines<br /> ;hypervisor: Hyperviseur<br /> ;image: Image<br /> ;interface: Interface<br /> ;job: tâche<br /> ;load balancer: Load balancer<br /> ;meter: Mesurer =&gt; D'autres propositions ?<br /> ;node: Node<br /> ;over commit: mise à jour<br /> ;plugin: Extension<br /> ;policy: stratégie<br /> ;quota: Quota<br /> ;router: Routeur<br /> ;Security Group: Groupe de sécurité<br /> ;server: Serveur<br /> ;snapshot: Instantané<br /> ;stack: Stack<br /> ;storage: Stockage<br /> ;subnet: Sous-réseau<br /> ;Swap-Disk: disque swap =&gt; D'autres propositions ?<br /> ;tag: tag<br /> ;template: modèle =&gt; D'autres propositions ?<br /> ;Tenant: Tenant<br /> ;token: Token<br /> ;usage: usage<br /> ;volume:Volume</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=77601 2015-04-16T08:53:05Z

<p>Fdot: </p> <hr /> <div>= Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Kilo - Horizon Java Script Translations<br /> # Kilo - Horizon Translations<br /> # Kilo - OpenStack Dashboard Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : Rw5xHz58LfEzByCZ<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> <br /> == Petit dictionnaire Français ==<br /> <br /> L'objectif de ce petit dictionnaire est de créer une base de mot à réutiliser lors des traductions.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; French:Français<br /> ;aggregate: Aggrégat<br /> ;availability zone: zone de disponibilité<br /> ;backend: Backend =&gt; D'autres propositions ?<br /> ;backup: Sauvegarde<br /> ;cache: cache<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute Services: Services Compute<br /> ;container: Conteneur <br /> ;Data Processing: Traitement des données<br /> ;disk: disque<br /> ;domain:Domaine<br /> ;domain group: groupe de domaine<br /> ;Ephemeral Disk: Disque éphémere<br /> ;Ephemeral Drive: Lecteur ephémere<br /> ;flavor: Variante<br /> ;floating ip: IP flottante<br /> ;gateway: Passerelle<br /> ;health Monitor: Supervision du statut des services<br /> ;host: Host<br /> ;Host Aggregate: Agrégat de machines<br /> ;hypervisor: Hyperviseur<br /> ;image: Image<br /> ;interface: Interface<br /> ;job: tâche<br /> ;load balancer: Load balancer<br /> ;meter: Mesurer =&gt; D'autres propositions ?<br /> ;node: Node<br /> ;over commit: mise à jour<br /> ;plugin: Extension<br /> ;quota: Quota<br /> ;router: Routeur<br /> ;Security Group: Groupe de sécurité<br /> ;server: Serveur<br /> ;snapshot: Instantané<br /> ;stack: Stack<br /> ;storage: Stockage<br /> ;subnet: Sous-réseau<br /> ;Swap-Disk: disque swap =&gt; D'autres propositions ?<br /> ;tag: tag<br /> ;template: modèle =&gt; D'autres propositions ?<br /> ;Tenant: Tenant<br /> ;token: Token<br /> ;usage: usage<br /> ;volume:Volume</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=76103 2015-03-23T16:29:35Z

<p>Fdot: </p> <hr /> <div>= Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Kilo - Horizon Java Script Translations<br /> # Kilo - Horizon Translations<br /> # Kilo - OpenStack Dashboard Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : i18n-juno<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> <br /> == Petit dictionnaire Français ==<br /> <br /> L'objectif de ce petit dictionnaire est de créer une base de mot à réutiliser lors des traductions.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; French:Français<br /> ;aggregate: Aggrégat<br /> ;availability zone: zone de disponibilité<br /> ;backend: Backend =&gt; D'autres propositions ?<br /> ;backup: Sauvegarde<br /> ;cache: cache<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute Services: Services Compute<br /> ;container: Conteneur <br /> ;Data Processing: Traitement des données<br /> ;disk: disque<br /> ;domain:Domaine<br /> ;domain group: groupe de domaine<br /> ;Ephemeral Disk: Disque éphémere<br /> ;Ephemeral Drive: Lecteur ephémere<br /> ;flavor: Variante<br /> ;floating ip: IP flottante<br /> ;gateway: Passerelle<br /> ;health Monitor: Supervision du statut des services<br /> ;host: Host<br /> ;Host Aggregate: Agrégat de machines<br /> ;hypervisor: Hyperviseur<br /> ;image: Image<br /> ;interface: Interface<br /> ;job: tâche<br /> ;load balancer: Load balancer<br /> ;meter: Mesurer =&gt; D'autres propositions ?<br /> ;node: Node<br /> ;over commit: mise à jour<br /> ;plugin: Extension<br /> ;quota: Quota<br /> ;router: Routeur<br /> ;Security Group: Groupe de sécurité<br /> ;server: Serveur<br /> ;snapshot: Instantané<br /> ;stack: Stack<br /> ;storage: Stockage<br /> ;subnet: Sous-réseau<br /> ;Swap-Disk: disque swap =&gt; D'autres propositions ?<br /> ;tag: tag<br /> ;template: modèle =&gt; D'autres propositions ?<br /> ;Tenant: Tenant<br /> ;token: Token<br /> ;usage: usage<br /> ;volume:Volume</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=75918 2015-03-19T09:30:03Z

<p>Fdot: </p> <hr /> <div>= Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Juno - Openstack Dashboard Translations<br /> # Juno - Horizon Translations<br /> # Juno - Horizon JavaScript Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : i18n-juno<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> <br /> == Petit dictionnaire Français ==<br /> <br /> L'objectif de ce petit dictionnaire est de créer une base de mot à réutiliser lors des traductions.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; French:Français<br /> ;aggregate: Aggrégat<br /> ;availability zone: zone de disponibilité<br /> ;backend: Backend =&gt; D'autres propositions ?<br /> ;backup: Sauvegarde<br /> ;cache: cache<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute Services: Services Compute<br /> ;container: Conteneur <br /> ;Data Processing: Traitement des données<br /> ;disk: disque<br /> ;domain:Domaine<br /> ;domain group: groupe de domaine<br /> ;Ephemeral Disk: Disque éphémere<br /> ;Ephemeral Drive: Lecteur ephémere<br /> ;flavor: Variante<br /> ;floating ip: IP flottante<br /> ;gateway: Passerelle<br /> ;health Monitor: Supervision du statut des services<br /> ;host: Host<br /> ;Host Aggregate: Agrégat de machines<br /> ;hypervisor: Hyperviseur<br /> ;image: Image<br /> ;interface: Interface<br /> ;job: tâche<br /> ;load balancer: Load balancer<br /> ;meter: Mesurer =&gt; D'autres propositions ?<br /> ;node: Node<br /> ;over commit: mise à jour<br /> ;plugin: Extension<br /> ;quota: Quota<br /> ;router: Routeur<br /> ;Security Group: Groupe de sécurité<br /> ;server: Serveur<br /> ;snapshot: Instantané<br /> ;stack: Stack<br /> ;storage: Stockage<br /> ;subnet: Sous-réseau<br /> ;Swap-Disk: disque swap =&gt; D'autres propositions ?<br /> ;tag: tag<br /> ;template: modèle =&gt; D'autres propositions ?<br /> ;Tenant: Tenant<br /> ;token: Token<br /> ;usage: usage<br /> ;volume:Volume</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=69558 2014-12-04T08:35:45Z

<p>Fdot: </p> <hr /> <div>[[Category:I18n]]<br /> <br /> === Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable sortable centre&quot; style=&quot;text-align: center;&quot;<br /> |- <br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 3 - Low || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 3 - Low || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73557 || 2 - Medium || Config tables will be moved out of common into config-reference. Content is used by other books, especially translate preface and support appendix (ch_preface.xml and app_support.xml)!<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 62743 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 16796 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 6919 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || hot-reference || Documentation || End users || ??? || 9579 || 1 - High || <br /> |-<br /> | OpenStack Manuals || glossary || Documentation || Common || Stable || 13645 || 1 - High || 08/21/2014 - Waiting for a feedback from the doc team about the content of the Glossary<br /> |-<br /> | OpenStack Manuals || openstack-ops || Documentation || End users || Becoming Stable || 59790 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || admin-guide-cloud || Documentation || Admin || Unstable || 40561 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || config-reference || Documentation || Admin || Unstable || 38507 || 3 - Low || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || image-guide || Documentation || End users || Becoming Stable || 9879 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || security-guide || Documentation || Admin || Becoming Stable || 39820 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || upgrade-guide || Documentation || Admin || ??? || 57 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || arch-design || Documentation || Admin || Unstable || 59049 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || networking-guide || Documentation || Admin || Unstable - draft || Growing fast || 4 - Do not translate yet || <br /> |-<br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=68867 2014-11-25T17:39:12Z

<p>Fdot: </p> <hr /> <div>= Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Juno - Openstack Dashboard Translations<br /> # Juno - Horizon Translations<br /> # Juno - Horizon JavaScript Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : i18n-juno<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> <br /> == Petit dictionnaire Français ==<br /> <br /> The following list of English words and their German preferred translation has been established while translating Horizon to German for the Icehouse release.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; Englisch:Français<br /> ;aggregate:Aggregat<br /> ;availability zone:Verfügbarkeitszone<br /> ;backend: Backend<br /> ;backup: Sicherung, Sicherungskopie<br /> ;cache: Zwischenspeicher<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute Services: Compute Dienste<br /> ;container: Container<br /> ;Data Processing: Datenverarbeitung<br /> ;disk: Festplatte<br /> ;domain:Domäne<br /> ;domain group: Domänengruppe<br /> ;Ephemeral Disk: Flüchtige Platte<br /> ;Ephemeral Drive: Flüchtiges Laufwerk<br /> ;flavor: Variante<br /> ;floating ip: Floating IP<br /> ;gateway: Gateway<br /> ;health Monitor: Gesundheitsmonitor<br /> ;host: Host<br /> ;Host Aggregate: Hostaggregat<br /> ;hypervisor: Hypervisor, pl. Hypervisoren<br /> ;image: Abbild<br /> ;interface: Schnittstelle<br /> ;job: Aufgabe<br /> ;load balancer: Loadbalancer<br /> ;meter: Zähler<br /> ;node: Node<br /> ;over commit: überladen, Überladung<br /> ;plugin: Plugin<br /> ;quota: Kontingent<br /> ;router: Router<br /> ;Security Group: Sicherheitsgruppe<br /> ;server: Server<br /> ;snapshot: Schattenkopie<br /> ;stack: Stack<br /> ;storage: Storage<br /> ;subnet: Subnetz<br /> ;Swap-Disk: Auslagerungsplatte<br /> ;tag: Schlagwort, pl. Schlagwörter<br /> ;template: Vorlage, pl. Vorlagen<br /> ;Tenant: Mandant (vorher: &quot;Mieter&quot;; übernommen im &quot;api-quick-start&quot; durch CarstenD)<br /> ;token: Token<br /> ;usage: Verwendung<br /> ;volume:Datenträger</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=68866 2014-11-25T17:38:49Z

<p>Fdot: </p> <hr /> <div>= Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Juno - Openstack Dashboard Translations<br /> # Juno - Horizon Translations<br /> # Juno - Horizon JavaScript Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : i18n-juno<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.<br /> <br /> == Petit dictionnaire Français ==<br /> <br /> The following list of English words and their German preferred translation has been established while translating Horizon to German for the Icehouse release.<br /> <br /> If you add a new item and in particular if you propose a change to an existing one, please '''''always mark the change in some way''''' to allow post-correction of probably already reviewed terms in the Transifex source.<br /> <br /> === Terminologie ===<br /> <br /> ; Englisch:Français<br /> ;aggregate:Aggregat<br /> ;availability zone:Verfügbarkeitszone<br /> ;backend: Backend<br /> ;backup: Sicherung, Sicherungskopie<br /> ;cache: Zwischenspeicher<br /> ;client: Client<br /> ;cluster: Cluster<br /> ;Compute Services: Compute Dienste<br /> ;container: Container<br /> ;Data Processing: Datenverarbeitung<br /> ;disk: Festplatte<br /> ;domain:Domäne<br /> ;domain group: Domänengruppe<br /> ;Ephemeral Disk: Flüchtige Platte<br /> ;Ephemeral Drive: Flüchtiges Laufwerk<br /> ;flavor: Variante<br /> ;floating ip: Floating IP<br /> ;gateway: Gateway<br /> ;health Monitor: Gesundheitsmonitor<br /> ;host: Host<br /> ;Host Aggregate: Hostaggregat<br /> ;hypervisor: Hypervisor, pl. Hypervisoren<br /> ;image: Abbild<br /> ;interface: Schnittstelle<br /> ;job: Aufgabe<br /> ;load balancer: Loadbalancer<br /> ;meter: Zähler<br /> ;node: Node<br /> ;over commit: überladen, Überladung<br /> ;plugin: Plugin<br /> ;quota: Kontingent<br /> ;router: Router<br /> ;Security Group: Sicherheitsgruppe<br /> ;server: Server<br /> ;snapshot: Schattenkopie<br /> ;stack: Stack<br /> ;storage: Storage<br /> ;subnet: Subnetz<br /> ;Swap-Disk: Auslagerungsplatte<br /> ;tag: Schlagwort, pl. Schlagwörter<br /> ;template: Vorlage, pl. Vorlagen<br /> ;Tenant: Mandant (vorher: &quot;Mieter&quot;; übernommen im &quot;api-quick-start&quot; durch CarstenD)<br /> ;token: Token<br /> ;usage: Verwendung<br /> ;volume:Datenträger</div>

Fdot https://wiki.openstack.org/w/index.php?title=OpenStack_Upstream_Institute&diff=65044 2014-10-15T13:03:03Z

<p>Fdot: </p> <hr /> <div>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.<br /> <br /> 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. <br /> <br /> [[OpenStack_Upstream_Training/Info|More details]]<br /> <br /> = When &amp; Where to get OpenStack Upstream Training =<br /> <br /> Next installation of the OpenStack Upstream Training will be in Paris, before the OpenStack Summit. Stay tuned !<br /> <br /> = How to prepare =<br /> <br /> * Make sure you have a wifi enabled laptop with you.<br /> * Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.<br /> * Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.<br /> * Get in touch with Loic Dachary &lt;loic@dachary.org&gt; to pick a contribution to work on.<br /> <br /> = Staff =<br /> * Stefano Maffulli &lt;stefano@openstack.org&gt; (training, mentoring, assistant, english) (2014/05)<br /> * Loic Dachary &lt;loic@dachary.org&gt; (training, mentoring, assistant, french, english) (2014/05, 2014/11)<br /> * Chris Ricker &lt;chris.ricker@gmail.com&gt; (training, mentoring, assistant, english) (2014/05, 2014/11)<br /> * Xavier Antoviaque &lt;xavier@antoviaque.org&gt; (training, mentoring, assistant, french, english)<br /> * Rodolphe Quiedeville &lt;rodolphe@quiedeville.org&gt; (training, mentoring, assistant, french) (2014/11)<br /> * Edouard THULEAU &lt;edouard.thuleau@cloudwatt.com&gt; (assistant, french, english) (2014/05, 2014/11)<br /> * François Bureau &lt;francois.bureau@cloudwatt.com&gt; (assistant, french, english) (2014/11)<br /> * Sahid Ferdjaoui &lt;sahid.ferdjaoui@redhat.com&gt; (assistant, french, english) (2014/05, 2014/11)<br /> * Christophe Sauthier &lt;christophe.sauthier@objectif-libre.com&gt; (training, mentoring, french) + (assistant, french, english) (2014/11)<br /> * Sylvain Bauza &lt;sbauza@redhat.com&gt; (assistant, mentoring, training, french, english) (2014/11)<br /> * Julie Pichon &lt;jpichon@redhat.com&gt; (training, mentoring, assistant, english) (2014/11)<br /> * Adrien Cunin &lt;adrien.cunin@osones.com&gt; (mentoring, assistant, french, english) (2014/11)<br /> * Tim Freund &lt;tim@freunds.net&gt; (assistant, english) (2014/11)<br /> * Syed Armani &lt;syed.armani@hastexo.com&gt; (training, mentoring, assistant, english) (2014/11)<br /> * Victoria Martínez de la Cruz &lt;victoria@vmartinezdelacruz.com&gt; (assistant, english) (2014/11)<br /> * Cindy Pallares &lt;cpallares@redhat.com&gt; (assistant, english) (2014/11)<br /> * Irena Berezovsky &lt;irena.berezovsky@gmail.com&gt; (assistant, mentor, english) (2014/11)<br /> * Haikel Guemar &lt;haikel.guemar@gmail.com&gt; (assistant, mentor, french, english) (2014/11)</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=63120 2014-09-19T07:34:46Z

<p>Fdot: </p> <hr /> <div>= Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Juno - Openstack Dashboard Translations<br /> # Juno - Horizon Translations<br /> # Juno - Horizon JavaScript Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].<br /> <br /> <br /> == Comment tester la traduction sur horizon ? ==<br /> Pour tester la traduction sur Horizon vous pouvez utiliser la plateforme de test :<br /> <br /> * Url : [http://157.7.133.23:13580/ http://157.7.133.23:13580/]<br /> * Identifiant : demo ou admin<br /> * Mot de passe : i18n-juno<br /> <br /> <br /> La plateforme est mise à jour à la 24ème minutes de chaque heure.</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=61044 2014-08-21T09:06:38Z

<p>Fdot: </p> <hr /> <div>= Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto:stephane.eveillard@gmail.com Stephane Eveillard]<br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Juno - Openstack Dashboard Translations<br /> # Juno - Horizon Translations<br /> # Juno - Horizon JavaScript Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/team/fr&diff=61043 2014-08-21T09:05:22Z

<p>Fdot: Created page with &quot;= Traduction française = Bienvenue sur l'espace dédié à la localisation en français. == Point de contact == Les points de contact de la communauté française de trad...&quot;</p> <hr /> <div>= Traduction française =<br /> <br /> Bienvenue sur l'espace dédié à la localisation en français. <br /> <br /> == Point de contact ==<br /> Les points de contact de la communauté française de traduction sont :<br /> * [mailto:francois.bureau@cloudwatt.com François Bureau]<br /> * [mailto: Stephane Eveillard]<br /> <br /> == Comment nous rejoindre ? ==<br /> Pour nous rejoindre, vous devez créer un compte sur [http://www.transifex.com Transifex] puis vous rendre dans le Projet Openstack. Choisissez la langue dans laquelle vous souhaitez contribuer puis cliquez sur le bouton : &quot;Rejoindre l’équipe&quot;.<br /> <br /> Une fois votre inscription terminée envoyez un e-mail aux points de contact avec une petite introduction.<br /> <br /> == Que traduire ? ==<br /> <br /> La priorité est donnée aux interfaces utilisateur, puis aux documentations dédiées aux utilisateurs finaux.<br /> <br /> Ainsi par ordre de priorité :<br /> # Juno - Openstack Dashboard Translations<br /> # Juno - Horizon Translations<br /> # Juno - Horizon JavaScript Translations<br /> <br /> &lt;br /&gt;<br /> Si vous préférez travailler sur la documentation, les priorités sont fixées sur la [https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize page de catégorisation des documentations].</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam&diff=61041 2014-08-21T08:34:05Z

<p>Fdot: </p> <hr /> <div>__NOTOC__<br /> [[Category:I18n]]<br /> = The I18n Team =<br /> [[File:Translation.svg|right|150px]]<br /> Internationalization is essential to make OpenStack ubiquitous. The mission of OpenStack I18N team is to make OpenStack ubiquitously accessible to people of all language backgrounds, by enhancing OpenStack software internationalization, providing translation, maintaining a translation platform and managing translation process for high quality translations.<br /> <br /> ''&quot;Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text.&quot;'' - from wikipedia.<br /> <br /> The OpenStack I18N team will take responsible for the I18n and L10n of OpenStack. Our work will include:<br /> * Translation of documentations, messages, websites, and etc.<br /> * Translation platform maintenance and enhancements<br /> * I18n test<br /> <br /> = Contributing =<br /> I18n team welcome any kinds of contribution.<br /> <br /> == Contribute to translations ==<br /> If you want to help the translations, you can join a [[I18nTeam#Local_Translation_Teams|local translation team]]. You can find the translation jobs in this local team and contact with the coordinators.<br /> <br /> If you cannot find your local team, you can request to [[I18nTeam/CreateLocalTeam|create a local translation team]].<br /> <br /> If you want to report translation errors, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad and report bugs. Mark bugs with a tag &quot;'''translation'''&quot;.<br /> <br /> There are three different roles in a translation team.<br /> * [[I18nTeam/Management|Coordinator]]: a privileged member in a translation team who can help in team management tasks, such as approving new members and reviewing contributions to that language. We also have task coordinators for specific tasks.<br /> * [[Documentation/Translation#Contribute_as_a_translator|Member (Translator)]] : a person who can submit translations.<br /> * [[Documentation/Translation#Contribute_as_a_reviewer|Reviewer]]: a person who can proofread translations and mark them as reviewed.<br /> <br /> == Contribute to translation tools ==<br /> Go to this page [[I18n/Tools|tools]] to understand the tools/scripts which are support our translation platform. If you want to help to report bugs, add more wishlists, and improve them, you can report bugs and fix bugs [https://bugs.launchpad.net/openstack-i18n here]. Mark bugs with a tag &quot;'''tools'''&quot;.<br /> <br /> == Fix I18n bugs ==<br /> If you want to help to report or fix I18n bugs of OpenStack, go to [https://bugs.launchpad.net/openstack-i18n openstack-i18n] in Launchpad. Mark bugs with a tag &quot;'''i18n'''&quot;.<br /> <br /> = Getting in touch =<br /> <br /> We use [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n openstack-i18n@lists.openstack.org] as the mailing list. We all hang out on #openstack-translation.<br /> The I18n team meets bi-weekly on Thursdays at alternating times, please see [[Meetings/I18nTeamMeeting]]<br /> <br /> = Local Translation Teams =<br /> Lead: Ying Chun &quot;Daisy&quot; Guo (Daisy on IRC)<br /> <br /> *[[I18nTeam/pt_BR|Portuguese (Brazil)]]<br /> *[[I18nTeam/ca|Catalan]]<br /> *[[I18n/team/zh_cn |Chinese (China)]]<br /> *Chinese (Taiwan) <br /> *Czech<br /> *Dutch (Netherlands)<br /> *[[I18nTeam/en_au|English (Australia)]]<br /> *[[I18nTeam/fr|French]]<br /> *German<br /> *[[I18nTeam/hi|Hindi]]<br /> *[[I18nTeam/ja|Japanese]]<br /> *[[I18nTeam/ko_KR|Korean]]<br /> *[[I18nTeam/pl|Polish]]<br /> *[[I18nTeam/pa_IN|Punjabi]]<br /> *Russian<br /> *[[I18nTeam/es|Spanish]]<br /> *Vietnamese<br /> *[[I18nTeam/id|Bahasa Indonesia]]<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! scope=&quot;col&quot;| Language<br /> ! scope=&quot;col&quot;| Coordinators ID<br /> ! scope=&quot;col&quot;| Translators ID<br /> |- <br /> ! scope=&quot;row&quot; | Brazilian Portuguese<br /> | [https://www.transifex.com/accounts/profile/gabrielcw gabrielcw], [https://www.transifex.com/accounts/profile/mdieder mdieder]<br /> | <br /> |-<br /> |- <br /> ! scope=&quot;row&quot; | Catalan<br /> | [https://www.transifex.com/accounts/profile/gabrielhurley gabrielhurley], [https://www.transifex.com/accounts/profile/Mireia_Sangalo Mireia_Sangalo], [https://www.transifex.com/accounts/profile/yrobla yrobla]<br /> | [https://www.transifex.com/accounts/profile/edubarcelo edubarcelo], [https://www.transifex.com/accounts/profile/lynxman lynxman], [https://www.transifex.com/accounts/profile/yrobla yrobla]<br /> |- <br /> ! scope=&quot;row&quot; | Chinese (China)<br /> | [https://www.transifex.com/accounts/profile/daisy.ycguo daisy.ycguo]<br /> | [https://www.transifex.com/accounts/profile/yuanpu yuanpu], [https://www.transifex.com/accounts/profile/fifieldt fifieldt]<br /> |- <br /> ! scope=&quot;row&quot; | English (Australia)<br /> | [https://www.transifex.com/accounts/profile/fifieldt fifieldt]<br /> | <br /> |-<br /> ! scope=&quot;row&quot; | French<br /> | [https://www.transifex.com/accounts/profile/steff00 Steff00], [https://www.transifex.com/accounts/profile/fbureau/ Fdot]<br /> | <br /> |- <br /> ! scope=&quot;row&quot; | German<br /> | [https://www.transifex.com/accounts/profile/alecsoft/ alexsoft], [https://www.transifex.com/accounts/profile/saschpe/ saschpe]<br /> | [https://www.transifex.com/accounts/profile/jaegerandi/ jaegerandi], [https://www.transifex.com/accounts/profile/llaera/ llaera], [https://www.transifex.com/accounts/profile/RedRider/ RedRider]<br /> |- <br /> ! scope=&quot;row&quot; | Hindi<br /> | <br /> | <br /> |-<br /> ! scope=&quot;row&quot; | Japanese <br /> | [https://www.transifex.com/accounts/profile/ritchey98/ ritchey98] (amotoki on IRC) [https://www.transifex.com/accounts/profile/katomo katomo],<br /> | [https://www.transifex.com/projects/p/openstack/language/ja/members/ Full Member List on Transifex]<br /> |- <br /> ! scope=&quot;row&quot; | Korean <br /> | [https://www.transifex.com/accounts/profile/ujuckr/ ujuckr] (ujuc on IRC)<br /> | [https://www.transifex.com/accounts/profile/Yeonki/ Yeonki], [https://www.transifex.com/accounts/profile/naleejang/ Nalee Jang], [https://www.transifex.com/accounts/profile/rumfox/ SangHyoung], [https://www.transifex.com/accounts/profile/JayLee/ Jay Lee], [https://www.transifex.com/accounts/profile/funfunyoo/ FunFun Yoo], [https://www.transifex.com/accounts/profile/MKJung/ Man-Ki Jung], [https://www.transifex.com/accounts/profile/bluejay.kr/ James Ahn], [https://www.transifex.com/accounts/profile/cdecide/ Shin Seung Ho], [https://www.transifex.com/accounts/profile/hyunsun/ Hyunsun Moon], [https://www.transifex.com/accounts/profile/ikhwan/ Ikhwan Koo], [https://www.transifex.com/accounts/profile/jaeyeun97/ Jaeyeun Charlie Yoon], [https://www.transifex.com/accounts/profile/yisukwon/ Yi Su Kwon], [https://www.transifex.com/accounts/profile/%EC%A0%95%EC%9D%B4%EC%8A%AC/ Leeseul Jung]<br /> |-<br /> ! scope=&quot;row&quot; | Polish<br /> | [https://www.transifex.com/accounts/profile/deejay1/ DeeJay1]<br /> |<br /> |-<br /> ! scope=&quot;row&quot; | Punjabi <br /> | [https://www.transifex.com/accounts/profile/jimidar/ Amandeep Singh Saini] (jimidar on IRC) <br /> | [https://www.transifex.com/accounts/profile/aalam/ Aman Alam] (alam on IRC), [https://www.transifex.com/accounts/profile/Ravinder/ Ravinder Singh], [https://www.transifex.com/accounts/profile/Savitojs/ Savitoj Singh] (savitoj on IRC), [https://www.transifex.com/accounts/profile/dhingra007/ Vipen Dhingra], [https://www.transifex.com/accounts/profile/navpreet.kaur210/ Navpreet Kaur]<br /> |- <br /> ! scope=&quot;row&quot; | Russian<br /> | [https://www.transifex.com/accounts/profile/adiantum/ adiantum]<br /> | [https://www.transifex.com/accounts/profile/eshumakher eshumakher]<br /> |- <br /> ! scope=&quot;row&quot; | Spanish<br /> | [https://www.transifex.com/accounts/profile/mariantb/ mariantb]<br /> | [https://www.transifex.com/accounts/profile/ladquin/ ladquin], [https://www.transifex.com/accounts/profile/vkmc/ vkmc], [https://www.transifex.com/accounts/profile/alberto.molina/ alberto.molina], [https://www.transifex.com/accounts/profile/aloga/ aloga], [https://www.transifex.com/accounts/profile/rodrigoauditore/ rodrigoauditore], [https://www.transifex.com/accounts/profile/rvegagom/ rvegagom], [https://www.transifex.com/accounts/profile/smarturo/ smarturo], [https://www.transifex.com/accounts/profile/vicdiaz/ vicdiaz], [https://www.transifex.com/accounts/profile/Makika/ Makika], [https://www.transifex.com/accounts/profile/toote/ toote], [https://www.transifex.com/accounts/profile/electrocucaracha/ electrocucaracha], [https://www.transifex.com/accounts/profile/heleno.jimenez/ heleno.jimenez], [https://www.transifex.com/accounts/profile/aburaschi/ aburaschi], [https://www.transifex.com/accounts/profile/amejia/ amejia], [https://www.transifex.com/accounts/profile/crodgut/ crodgut], [https://www.transifex.com/accounts/profile/dareste/ dareste], [https://www.transifex.com/accounts/profile/itxaka/ itxaka], [https://www.transifex.com/accounts/profile/izaesa/ izaesa], [https://www.transifex.com/accounts/profile/jose.ramirez.rk/ jose.ramirez.rk], [https://www.transifex.com/accounts/profile/josephmartz/ josephmartz], [https://www.transifex.com/accounts/profile/pnavarro/ pnavarro], [https://www.transifex.com/accounts/profile/rferrer/ rferrer], [https://www.transifex.com/accounts/profile/sebasmagri/ sebasmagri], [https://www.transifex.com/accounts/profile/ElDeivid/ ElDeivid], [https://www.transifex.com/accounts/profile/Jacobodonosor/ Jacobodonosor], [https://www.transifex.com/accounts/profile/quiqueruizna/ quiqueruizna], [https://www.transifex.com/accounts/profile/kalegape/ kalegape], [https://www.transifex.com/accounts/profile/kkoci/ kkoci], [https://www.transifex.com/accounts/profile/gvgo/ gvgo], [https://www.transifex.com/accounts/profile/raf8150/ raf8150], [https://www.transifex.com/accounts/profile/martinproject/ martinproject]<br /> |-<br /> ! scope=&quot;row&quot; | Vietnamese <br /> | [https://www.transifex.com/accounts/profile/DTT/ Hang Tran],[https://www.transifex.com/accounts/profile/ppanhh/ Anh Phan], [https://www.transifex.com/accounts/profile/NguyenTien/ Tien Nguyen], [https://www.transifex.com/accounts/profile/giangdt/ Giang Duong]<br /> | [https://www.transifex.com/accounts/profile/HoangNguyen/ Hoang Nguyen], [https://www.transifex.com/accounts/profile/HaMai/ Mai Thuy Ha], [https://www.transifex.com/accounts/profile/bvqbao/ Bui Vo Quoc Bao], [https://www.transifex.com/accounts/profile/chienbinhIT/ Nguyen Ba Cat], [https://www.transifex.com/accounts/profile/dontung/ Don Tung], [https://www.transifex.com/accounts/profile/ducito/ Nguyen Ngoc Duc], [https://www.transifex.com/accounts/profile/hoangvudtu/ Hoang Vu], [https://www.transifex.com/accounts/profile/huteduvn/ Tong Manh Cuong], [https://www.transifex.com/accounts/profile/lehoainam/ Le Hoai Nam], [https://www.transifex.com/accounts/profile/ninhhv/ Ha Van Ninh], [https://www.transifex.com/accounts/profile/quang.tran/ Tran Viet Quang], [https://www.transifex.com/accounts/profile/oss/ Pham Tuan Anh], [https://www.transifex.com/accounts/profile/quangnn/ Quang Nguyen], [https://www.transifex.com/accounts/profile/sujarot/ Nguyen Thanh Vinh], [https://www.transifex.com/accounts/profile/trandung11/ Tran Dung], [https://www.transifex.com/accounts/profile/trungdungdtu/ Trung Dung], [https://www.transifex.com/accounts/profile/vina007/ Tam]<br /> |-<br /> ! scope=&quot;row&quot; | Bahasa Indonesia / Indonesian<br /> | [https://www.transifex.com/accounts/profile/fthamura/ Frans Thamura]<br /> | [https://www.transifex.com/accounts/profile/fthamura/ Frans Thamura]<br /> <br /> |-<br /> |}</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=61040 2014-08-21T08:28:56Z

<p>Fdot: /* Document categorize */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable sortable centre&quot; style=&quot;text-align: center;&quot;<br /> |- <br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || Admin || Archived || 1264 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 3 - Low || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 3 - Low || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-install || Documentation || Admin || Archived || 17101 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-compute-admin || Documentation || Admin || Archived || 38990 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73557 || 2 - Medium || Config tables will be moved out of common into config-reference. Content is used by other books, especially translate preface and support appendix (ch_preface.xml and app_support.xml)!<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || z-old-cli-guide || Documentation || Admin || Archived || 2861 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 62743 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 16796 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-ha || Documentation || Admin || Archived || 4021 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 6919 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || glossary || Documentation || Common || Stable || 13645 || 1 - High || 08/21/2014 - Waiting for a feedback from the doc team about the content of the Glossary<br /> |-<br /> | OpenStack Manuals || z-old-openstack-network-connectivity-admin || Documentation || Admin || Archived || 18712 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-object-storage-admin || Documentation || Admin || Archived || 15733 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || openstack-ops || Documentation || End users || Becoming Stable || 59790 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || admin-guide-cloud || Documentation || Admin || Unstable || 40561 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || config-reference || Documentation || Admin || Unstable || 38507 || 3 - Low || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || z-old-openstack-block-storage-admin || Documentation || Admin || Archived || 9627 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || image-guide || Documentation || End users || Becoming Stable || 9879 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || security-guide || Documentation || Admin || Becoming Stable || 39820 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || arch-design || Documentation || Admin || Unstable || 59049 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || networking-guide || Documentation || Admin || Unstable - draft || Growing fast || 4 - Do not translate yet || <br /> |-<br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=61039 2014-08-21T08:28:35Z

<p>Fdot: /* Document categorize */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable sortable centre&quot; style=&quot;text-align: center;&quot;<br /> |- <br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || Admin || Archived || 1264 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 3 - Low || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 3 - Low || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-install || Documentation || Admin || Archived || 17101 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-compute-admin || Documentation || Admin || Archived || 38990 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73557 || 2 - Medium || Config tables will be moved out of common into config-reference. Content is used by other books, especially translate preface and support appendix (ch_preface.xml and app_support.xml)!<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || z-old-cli-guide || Documentation || Admin || Archived || 2861 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 62743 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 16796 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-ha || Documentation || Admin || Archived || 4021 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 6919 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || glossary || Documentation || Common || Stable || 13645 || 1 - High || 08/21/2014 Waiting for a feedback from the doc team about the content of the Glossary<br /> |-<br /> | OpenStack Manuals || z-old-openstack-network-connectivity-admin || Documentation || Admin || Archived || 18712 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-object-storage-admin || Documentation || Admin || Archived || 15733 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || openstack-ops || Documentation || End users || Becoming Stable || 59790 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || admin-guide-cloud || Documentation || Admin || Unstable || 40561 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || config-reference || Documentation || Admin || Unstable || 38507 || 3 - Low || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || z-old-openstack-block-storage-admin || Documentation || Admin || Archived || 9627 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || image-guide || Documentation || End users || Becoming Stable || 9879 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || security-guide || Documentation || Admin || Becoming Stable || 39820 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || arch-design || Documentation || Admin || Unstable || 59049 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || networking-guide || Documentation || Admin || Unstable - draft || Growing fast || 4 - Do not translate yet || <br /> |-<br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=User:Fdot&diff=59894 2014-08-07T12:14:32Z

<p>Fdot: </p> <hr /> <div>== François Bureau ==<br /> <br /> '''@ Cloudwatt''' &lt;br /&gt;<br /> Location: Paris, France<br /> <br /> === Interest ===<br /> * OpenStack french community <br /> * OpenStack french translation<br /> <br /> === Contact ===<br /> IRC: fdot &lt;br /&gt;<br /> Transifex : fbureau<br /> <br /> === Links ===<br /> Cloudwatt: http://www.cloudwatt.com &lt;br /&gt;<br /> Cloudwatt Techblog: http://dev.cloudwatt.com/en/authors/francois/index.html &lt;br /&gt;<br /> Linkedin: http://fr.linkedin.com/in/francoisbureau/ &lt;br /&gt;<br /> Transifex : https://www.transifex.com/accounts/profile/fbureau/ &lt;br /&gt;<br /> Launchpad : https://launchpad.net/~bureaufrancois &lt;br /&gt;<br /> Upstream University : http://upstream-university.org/ &lt;br /&gt;<br /> <br /> <br /> ----<br /> [[Category:Homepage]]</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59893 2014-08-07T10:11:02Z

<p>Fdot: /* Document categorize */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable sortable centre&quot; style=&quot;text-align: center;&quot;<br /> |- <br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || Admin || Archived || 1264 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-install || Documentation || Admin || Archived || 17101 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-compute-admin || Documentation || Admin || Archived || 38990 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73557 || 2 - Medium || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || z-old-cli-guide || Documentation || Admin || Archived || 2861 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 62743 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 16796 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-ha || Documentation || Admin || Archived || 4021 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 6919 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || glossary || Documentation || Common || Stable || 13645 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-network-connectivity-admin || Documentation || Admin || Archived || 18712 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-object-storage-admin || Documentation || Admin || Archived || 15733 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || openstack-ops || Documentation || End users || Becoming Stable || 59790 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || admin-guide-cloud || Documentation || Admin || Unstable || 40561 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || config-reference || Documentation || Admin || Unstable || 38507 || 3 - Low || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || z-old-openstack-block-storage-admin || Documentation || Admin || Archived || 9627 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || image-guide || Documentation || End users || Becoming Stable || 9879 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || security-guide || Documentation || Admin || Becoming Stable || 39820 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || arch-design || Documentation || Admin || Unstable || 59049 || 3 - Low || <br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59892 2014-08-07T09:59:28Z

<p>Fdot: </p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;sortable centre&quot; cellpadding=&quot;10&quot; cellspacing=&quot;0&quot; border=&quot;1&quot;<br /> |- <br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || Admin || Archived || 1264 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-install || Documentation || Admin || Archived || 17101 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-compute-admin || Documentation || Admin || Archived || 38990 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73557 || 2 - Medium || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || z-old-cli-guide || Documentation || Admin || Archived || 2861 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 62743 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 16796 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-ha || Documentation || Admin || Archived || 4021 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 6919 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || glossary || Documentation || Common || Stable || 13645 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-network-connectivity-admin || Documentation || Admin || Archived || 18712 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-object-storage-admin || Documentation || Admin || Archived || 15733 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || openstack-ops || Documentation || End users || Becoming Stable || 59790 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || admin-guide-cloud || Documentation || Admin || Unstable || 40561 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || config-reference || Documentation || Admin || Unstable || 38507 || 3 - Low || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || z-old-openstack-block-storage-admin || Documentation || Admin || Archived || 9627 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || image-guide || Documentation || End users || Becoming Stable || 9879 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || security-guide || Documentation || Admin || Becoming Stable || 39820 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || arch-design || Documentation || Admin || Unstable || 59049 || 3 - Low || <br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59891 2014-08-07T09:59:00Z

<p>Fdot: /* Alternative suggestion of categorization */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Changes !! End users !! Admins !! Developers<br /> |-<br /> | Frequently changed || || || <br /> |-<br /> | Changed a few || || || <br /> |-<br /> | Stable || || || API Quick Start (1,077words)<br /> |}<br /> <br /> === Alternative suggestion of categorization ===<br /> <br /> Here is a small example :<br /> <br /> {| class=&quot;sortable centre&quot; cellpadding=&quot;10&quot; cellspacing=&quot;0&quot; border=&quot;1&quot;<br /> |- <br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || Admin || Archived || 1264 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-install || Documentation || Admin || Archived || 17101 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-compute-admin || Documentation || Admin || Archived || 38990 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73557 || 2 - Medium || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || z-old-cli-guide || Documentation || Admin || Archived || 2861 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 62743 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 16796 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-ha || Documentation || Admin || Archived || 4021 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 6919 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || glossary || Documentation || Common || Stable || 13645 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-network-connectivity-admin || Documentation || Admin || Archived || 18712 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-object-storage-admin || Documentation || Admin || Archived || 15733 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || openstack-ops || Documentation || End users || Becoming Stable || 59790 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || admin-guide-cloud || Documentation || Admin || Unstable || 40561 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || config-reference || Documentation || Admin || Unstable || 38507 || 3 - Low || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || z-old-openstack-block-storage-admin || Documentation || Admin || Archived || 9627 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || image-guide || Documentation || End users || Becoming Stable || 9879 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || security-guide || Documentation || Admin || Becoming Stable || 39820 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || arch-design || Documentation || Admin || Unstable || 59049 || 3 - Low || <br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59889 2014-08-07T09:43:38Z

<p>Fdot: /* Alternative suggestion of categorization */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Changes !! End users !! Admins !! Developers<br /> |-<br /> | Frequently changed || || || <br /> |-<br /> | Changed a few || || || <br /> |-<br /> | Stable || || || API Quick Start (1,077words)<br /> |}<br /> <br /> === Alternative suggestion of categorization ===<br /> <br /> Here is a small example :<br /> <br /> {| class=&quot;wikitable sortable centre&quot; cellpadding=&quot;20&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | Horizon || Juno - Horizon Translations || UI || End users || || || 1 - High || <br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || n/a || Archived || 1264 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-install || Documentation || Admin || Archived || 17101 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-compute-admin || Documentation || Admin || Archived || 38990 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73557 || 2 - Medium || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || z-old-cli-guide || Documentation || Admin || Archived || 2861 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 62743 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 16796 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-ha || Documentation || Admin || Archived || 4021 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 6919 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59888 2014-08-07T09:40:22Z

<p>Fdot: /* Alternative suggestion of categorization */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Changes !! End users !! Admins !! Developers<br /> |-<br /> | Frequently changed || || || <br /> |-<br /> | Changed a few || || || <br /> |-<br /> | Stable || || || API Quick Start (1,077words)<br /> |}<br /> <br /> === Alternative suggestion of categorization ===<br /> <br /> Here is a small example :<br /> <br /> {| class=&quot;wikitable sortable centre&quot;<br /> |-<br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | Horizon || Juno - Horizon Translations || UI || End users || || || 1 - High || <br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || n/a || Archived || 1264 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-install || Documentation || Admin || Archived || 17101 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-compute-admin || Documentation || Admin || Archived || 38990 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73557 || 2 - Medium || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || z-old-cli-guide || Documentation || Admin || Archived || 2861 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || training-guides || Documentation || End users || Do not translate || 62743 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || cli-reference || Documentation || Developers || Unstable || 16796 || 2 - Medium || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-ha || Documentation || Admin || Archived || 4021 || 5 - To be deleted || <br /> |-<br /> | OpenStack Manuals || high-availability-guide || Documentation || Admin || Do not translate || 6919 || 4 - To be rewrite || Needs a complete rewrite in the future<br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59887 2014-08-07T09:27:41Z

<p>Fdot: /* Alternative suggestion of categorization */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Changes !! End users !! Admins !! Developers<br /> |-<br /> | Frequently changed || || || <br /> |-<br /> | Changed a few || || || <br /> |-<br /> | Stable || || || API Quick Start (1,077words)<br /> |}<br /> <br /> === Alternative suggestion of categorization ===<br /> <br /> Here is a small example :<br /> <br /> {| class=&quot;wikitable sortable centre&quot;<br /> |-<br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | Horizon || Juno - Horizon Translations || UI || End users || || || 1 - High || <br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1 077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || n/a || Archived || 1 264 || 4 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || Stable || 103 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || Developers || Stable || 4 151 || 1 - High || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-install || Documentation || Admin || Archived || 17 101 || 4 - To be deleted || <br /> |-<br /> | OpenStack Manuals || z-old-openstack-compute-admin || Documentation || Admin || Archived || 38 990 || 4 - To be deleted || <br /> |-<br /> | OpenStack Manuals || user-guide-admin || Documentation || Admin || Unstable || 7 480 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || Common || Documentation || Common || Unstable || 73 557 || 2 - Medium || Config tables will be moved out of common into config-reference<br /> |-<br /> | OpenStack Manuals || install-guide || Documentation || Admin || Stablises ~1 week after release || 20 190 || 2 - Medium || Stablises ~1 week after release, then about 1 month after that becomes unstable again<br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |-<br /> | OpenStack Manuals || user-guide || Documentation || End users || Unstable || 12 339 || 3 - Low || <br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59886 2014-08-07T08:57:51Z

<p>Fdot: /* Alternative suggestion of categorization */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Changes !! End users !! Admins !! Developers<br /> |-<br /> | Frequently changed || || || <br /> |-<br /> | Changed a few || || || <br /> |-<br /> | Stable || || || API Quick Start (1,077words)<br /> |}<br /> <br /> === Alternative suggestion of categorization ===<br /> <br /> Here is a small example :<br /> <br /> {| class=&quot;wikitable sortable centre&quot;<br /> |-<br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> ! scope=&quot;col&quot; | Comments<br /> |-<br /> | Horizon || Juno - Horizon Translations || UI || End users || || || 1 - High || <br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || Stable || 1,077 || 1 - High || <br /> |-<br /> | OpenStack Manuals || z-old-basic-install || Documentation || n/a || Archived || 1,264 || 4 - To be deleted || <br /> |-<br /> | OpenStack Manuals || api-guide || Documentation || Developers || || 103 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref-guides || Documentation || Developers || Stable || 211 || 1 - High || Contains WADLS we can't translate at the moment<br /> |-<br /> | OpenStack Manuals || api-ref || Documentation || n/a || Archived || 1,264 || 4 - To be deleted || <br /> <br /> |}<br /> <br /> ===Discussion===<br /> * Attempt at categorising documents: https://etherpad.openstack.org/p/i18n-manuals-classification</div>

Fdot https://wiki.openstack.org/w/index.php?title=Meetings/I18nTeamMeeting&diff=59884 2014-08-07T07:38:00Z

<p>Fdot: /* Agenda for next meeting */</p> <hr /> <div>[[Category:I18n]]<br /> <br /> = Weekly I18n team meeting =<br /> If you're interested in [[I18nTeam|internationalisation]], we hold bi-weekly public meetings on Thursdays in &lt;code&gt;&lt;nowiki&gt;#openstack-meeting&lt;/nowiki&gt;&lt;/code&gt;, alternating between two different times:<br /> <br /> * Week 1 (Europe/India Friendly): 0800 UTC<br /> ** Beijing 1600<br /> ** Tokyo 1700<br /> ** Melbourne 1800<br /> ** San Francisco 0100<br /> ** Guayaquil 0300<br /> ** New York 0500<br /> ** Sao Paulo 0500<br /> ** Paris 1000<br /> ** Bangalore 1330<br /> <br /> * Week 3 (North/South America Friendly): 0000 UTC<br /> ** Beijing 0800<br /> ** Tokyo 0900<br /> ** Melbourne 1000<br /> ** San Francisco 1700<br /> ** Guayaquil 1900<br /> ** New York 2000<br /> ** Sao Paulo 2100<br /> ** Paris 0200<br /> ** Bangalore 0530<br /> <br /> * Week 5 (if any): no meeting<br /> <br /> == Agenda for next meeting ==<br /> Next Meeting: Thursday, 7th August at 0800 UTC<br /> * The second meeting time discussion<br /> * Documents’ categorization <br /> * Open discussions<br /> <br /> == Previous meetings ==<br /> Previous meetings, with their notes and logs, can be found in under [[I18N/MeetingLogs]]</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59883 2014-08-07T07:32:33Z

<p>Fdot: /* Alternative suggestion of categorization */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Changes !! End users !! Admins !! Developers<br /> |-<br /> | Frequently changed || || || <br /> |-<br /> | Changed a few || || || <br /> |-<br /> | Stable || || || API Quick Start (1,077words)<br /> |}<br /> <br /> === Alternative suggestion of categorization ===<br /> <br /> Here is a small example :<br /> <br /> {| class=&quot;wikitable sortable centre&quot;<br /> |-<br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> |-<br /> | Horizon || Juno - Horizon Translations || UI || End users || || || 1 - High<br /> |-<br /> | Heat || heat-log-critical-translations || Log || Admin || || || 3 - Low<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || || || 1 - High<br /> |}</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59882 2014-08-07T07:31:58Z

<p>Fdot: /* Alternative suggestion of categorization */</p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Changes !! End users !! Admins !! Developers<br /> |-<br /> | Frequently changed || || || <br /> |-<br /> | Changed a few || || || <br /> |-<br /> | Stable || || || API Quick Start (1,077words)<br /> |}<br /> <br /> === Alternative suggestion of categorization ===<br /> <br /> Here is a small example :<br /> <br /> {| class=&quot;wikitable sortable centre&quot;<br /> |-<br /> ! scope=&quot;col&quot; | Projects<br /> ! scope=&quot;col&quot; | Ressources<br /> ! scope=&quot;col&quot; | Type <br /> ! scope=&quot;col&quot; | Target <br /> ! scope=&quot;col&quot; | Frequently changed <br /> ! scope=&quot;col&quot; | Size <br /> ! scope=&quot;col&quot; | Priority<br /> |-<br /> | Horizon || Juno - Horizon Translations || UI || End users || || || High<br /> |-<br /> | Heat || heat-log-critical-translations || Log || Admin || || || Low<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || || || High<br /> |}</div>

Fdot https://wiki.openstack.org/w/index.php?title=I18nTeam/docs-translation&diff=59881 2014-08-07T07:27:43Z

<p>Fdot: </p> <hr /> <div>=== Document categorize ===<br /> Translation team use this page to track the status of documents and decide the priorities of translation.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Changes !! End users !! Admins !! Developers<br /> |-<br /> | Frequently changed || || || <br /> |-<br /> | Changed a few || || || <br /> |-<br /> | Stable || || || API Quick Start (1,077words)<br /> |}<br /> <br /> === Alternative suggestion of categorization ===<br /> <br /> Here is a small example :<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Projects !! Ressources !! Type !! Target !! Frequently changed !! Size !! Priority<br /> |-<br /> | Horizon || Juno - Horizon Translations || UI || End users || || || High<br /> |-<br /> | Heat || heat-log-critical-translations || Log || Admin || || || Low<br /> |-<br /> | OpenStack Manuals || api-quick-start || Documentation || Developers || || || High<br /> |}</div>

Fdot https://wiki.openstack.org/w/index.php?title=User:Fdot&diff=29468 2013-09-05T10:40:05Z

<p>Fdot: /* François Bureau */</p> <hr /> <div>== François Bureau ==<br /> <br /> '''Contact Center Manager @ Cloudwatt''' &lt;br /&gt;<br /> Location: Paris, France<br /> <br /> === Interest ===<br /> * OpenStack french community <br /> * OpenStack french translation<br /> <br /> === Contact ===<br /> IRC: fdot &lt;br /&gt;<br /> Transifex : fbureau<br /> <br /> === Links ===<br /> Cloudwatt: http://www.cloudwatt.com &lt;br /&gt;<br /> Linkedin: http://fr.linkedin.com/in/francoisbureau/ &lt;br /&gt;<br /> Transifex : https://www.transifex.com/accounts/profile/fbureau/ &lt;br /&gt;<br /> Launchpad : https://launchpad.net/~bureaufrancois &lt;br /&gt;<br /> Upstream University : http://upstream-university.org/ &lt;br /&gt;<br /> <br /> <br /> ----<br /> [[Category:Homepage]]</div>

Fdot https://wiki.openstack.org/w/index.php?title=User:Fdot&diff=29467 2013-09-05T10:37:01Z

<p>Fdot: /* François Bureau */</p> <hr /> <div>== François Bureau ==<br /> <br /> '''Contact Center Manager @ Cloudwatt''' &lt;br /&gt;<br /> Location: Paris, France<br /> <br /> === Interest ===<br /> * OpenStack french community <br /> * OpenStack french translation<br /> <br /> === Contact ===<br /> IRC: fdot &lt;br /&gt;<br /> Transifex : fbureau<br /> <br /> === Links ===<br /> Cloudwatt: http://www.cloudwatt.com &lt;br /&gt;<br /> Linkedin: http://fr.linkedin.com/in/francoisbureau/ &lt;br /&gt;<br /> Transifex : https://www.transifex.com/accounts/profile/fbureau/ &lt;br /&gt;<br /> Launchpad : https://launchpad.net/~bureaufrancois &lt;br /&gt;<br /> <br /> <br /> ----<br /> [[Category:Homepage]]</div>

Fdot