training-guides/doc/upstream-training/04-program-ecosystem.rst
Stefano Maffulli 5d1ac2c236 Adding slides #4, Program Ecosystem
Change-Id: If164b2471121029276414eac18b16c2d7bc3e6f9
2014-08-26 21:41:45 -05:00

99 lines
1.5 KiB
ReStructuredText

OpenStack Technical Committee
=============================
OpenStack Program Ecosystem
---------------------------
<teacher name>
<date>
----
Lifecycle of a new Program
==========================
.. image:: ./_assets/04-01-lifecycle1.png
----
External
========
.. image:: ./_assets/04-02-lifecycle.png
- Idea
- Gather a community
- Alternate implementations
- Stackforge
- File an OpenStack incubation request
----
Incubated
=========
.. image:: ./_assets/04-03-lifecycle.png
- Fill the gap with graduation requirements
- Align with the OpenStack way
- Two development milestones
- Migrate to the openstack/* namespace
- Graduation review
----
Integrated
==========
.. image:: ./_assets/04-04-lifecycle.png
- Cannot graduate in the middle of a cycle
- Follow a full cycle as an integrated project
----
Core (or What is OpenStack)
===========================
- DefCore initiative, sponsored by the Board of Directors
- TODO
----
Stackforge
==========
.. image:: ./_assets/04-05-stackforge.png
- Gerrit code review
- Jenkins continuous integration
- Git repository
- IRC bots, pypi uploads...
----
What is Stackforge for
======================
.. image:: ./_assets/04-06-stackforge.png
- Maintain related unofficial projects
- Same tools and procedures used by the main projects
----
How to add a project to Stackforge
==================================
.. image:: ./_assets/04-07-stackforge.png
----
Exercise
========
What kind of program do you want to contribute to?