diff --git a/doc/upstream-training/index.rst b/doc/upstream-training/index.rst index 92f03fd4..b7bec4c6 100644 --- a/doc/upstream-training/index.rst +++ b/doc/upstream-training/index.rst @@ -95,7 +95,7 @@ How OpenStack is made * `Release cycle <01-release-cycle.html>`_ * `Relevant actors <02-relevant-actors.html>`_ * `OpenStack Governance <03-technical-committee.html>`_ -* `OpenStack "Big Tent" and tags <04-program-ecosystem.html>`_ +* `Official OpenStack projects <04-official-openstack-projects.html>`_ * `OpenStack Design Summit <05-design-summit.html>`_ * `IRC meetings <06-irc-meetings.html>`_ diff --git a/doc/upstream-training/source/04-official-openstack-projects.rst b/doc/upstream-training/source/04-official-openstack-projects.rst new file mode 100644 index 00000000..b4e171a7 --- /dev/null +++ b/doc/upstream-training/source/04-official-openstack-projects.rst @@ -0,0 +1,140 @@ +=========================== +Official OpenStack projects +=========================== + +.. image:: ./_assets/os_background.png + :class: fill + :width: 100% + +OpenStack Project Teams +======================= +- The building blocks to achieve OpenStack's mission +- Using the same tools (code repository, bug tracker, etc) and coordinated + processes to produce a number of deliverables +- Teams in OpenStack can be freely created as they are needed +- Teams of official projects are under the authority of the Technical Commitee + +Official OpenStack projects +=========================== +- Official OpenStack projects have to fullfill the requirements of official + OpenStack projects +- Projects are evolving themselves and also sustain for one collaborative + framework, OpenStack + + - Projects APIs are documented within the project + - Testable on its own + - Dashboard (horizon) and DevStack provide plugin interface for easy + integration + +- Big Tent is a code name for the official OpenStack projects + +Benefits of being an Official OpenStack project +=============================================== + - Contributors of an OpenStack project + + - Get to vote in the Technical Commitee election + - Can publish to docs.openstack.org and developer.openstack.org + - Get space on OpenStack Summits and Project Team Gatherings (PTG) + + .. note:: + + - PTG: https://www.openstack.org/ptg/ + +Benefits of being an Official OpenStack project +=============================================== + - Contributors of an OpenStack project + + - Get marketing from the OpenStack Foundation + - Get access to Foundation programs, like mentoring and internship to help + with on boarding + - Get guidance from community members and leaders + +Requirements of Official OpenStack projects +=========================================== + - Align with the OpenStack Mission and follow the OpenStack way, the four + opens + - Ensure basic interoperability with the rest of OpenStack + - Have an active team of one or more contributors + - Participate in any goals specified by the TC, as defined by OpenStack-wide + Goals + - Meet any policies that the TC requires from all projects + - Submit to the TC oversight + - It is the projects decision to follow the OpenStack release + +.. note:: + + - Requirements + (http://governance.openstack.org/reference/new-projects-requirements.html) + - Mission (https://wiki.openstack.org/wiki/Main_Page) + - Goals (http://governance.openstack.org/goals/index.html#release-cycle-goals) + + - A project is aligned with the OpenStack Mission if + + - have a clear and defined scope. + - provides a cloud infrastructure service or should directly build on an + existing OpenStack cloud infrastructure service + + - The four opens + + - http://governance.openstack.org/reference/opens.html + - http://governance.openstack.org/reference/new-projects-requirements.html + + - ensures basic interoperability with the rest of OpenStack: User-facing API + services should support Keystone for discovery and authentication + +Core and Optional Services +========================== +- Core services are OpenStack projects and essential in every OpenStack-powered + IaaS cloud or product +- Optional services are also OpenStack projects but not necessarily need to + operate OpenStack depending on use cases + +.. note:: + - Full list of Official OpenStack projects: + http://governance.openstack.org/reference/tags/type_service.html#tag-type-service + - All projects: http://governance.openstack.org/reference/projects/index.html + +Core and Optional Services +========================== + +.. image:: ./_assets/big-tent-and-core-services.png + :scale: 90 % + +Tags describing OpenStack Projects +================================== +- Describe the output produced by the OpenStack community teams + + - About software, documentation, release management etc + - How projects are released + - Team diversity + - ... + +- Tags can be proposed by anyone + + - List of approved tags + - http://governance.openstack.org/reference/tags/index.html + +DefCore (or what cloud can be labeled as OpenStack) +=================================================== +.. image:: ./_assets/04-02-defcore.png + :align: center + +- "Guiding principles" used by the Foundation Board to determine how commercial + implementations of OpenStack can be granted use of the trademark + +.. note:: + + - Implementations that are Core can use OpenStack trademark + (OpenStack™) + - The Implementation is a subset of the whole project + - Claiming OpenStack requiring use of designated upstream code + - The Implementation must have an open reference implementation + - Vendors may substitute alternate implementations + - Tests can be remotely or self-administered + - A subset of tests are chosen by the Foundation as "must-pass" + - Being OpenStack Core Implementation means passing all "must-pass" tests + +Exercise +======== + +What kind of project do you want to contribute to? diff --git a/doc/upstream-training/source/04-program-ecosystem.rst b/doc/upstream-training/source/04-program-ecosystem.rst deleted file mode 100644 index f64d155c..00000000 --- a/doc/upstream-training/source/04-program-ecosystem.rst +++ /dev/null @@ -1,87 +0,0 @@ -============================= -OpenStack "Big Tent" and tags -============================= - -.. image:: ./_assets/os_background.png - :class: fill - :width: 100% - -OpenStack Project Teams -======================= - -- The building blocks to achieve OpenStack's mission -- Teams of people using tools (code repository, bug tracker, etc) and - coordinated processes to produce a number of deliverables -- The Technical Committee reviews Working Groups interested in - becoming official OpenStack Project Teams - -How to form new Project Team -============================ - -- Start from groups of people working in the same area -- As these grow naturally they can apply to become Official -- TC will check: - - - Alignment with OpenStack mission - - Interoperability with other projects - - Active and diverse team of contributors - - Group can follow the four *Open* - - - Open Source - - Open Community - - Open Design - - Open Development - -Tags describing OpenStack Projects -================================== - -- Describe the output produced by the OpenStack community teams - - - Software, documentation, release management etc - - http://governance.openstack.org/reference/projects/index.html - -- Current tags describe how projects are released and team diversity -- Other tags can be proposed by anyone - - - List of approved tags - - http://governance.openstack.org/reference/tags/index.html - -Core (or What is OpenStack) -=========================== - -.. image:: ./_assets/04-02-defcore.png - -- DefCore initiative: - - - guiding principles" used by the Foundation Board to determine how - commercial implementations of OpenStack can be granted use of the - trademark - -DefCore principles -================== - -- Implementations that are Core can use OpenStack trademark - (OpenStack™) -- Core is a subset of the whole project -- Claiming OpenStack requiring use of designated upstream code -- Projects must have an open reference implementation -- Vendors may substitute alternate implementations -- Tests can be remotely or self-administered -- A subset of tests are chosen by the Foundation as "must-pass" -- OpenStack Core means passing all "must-pass" tests - - -Stackforge -========== - -.. image:: ./_assets/04-05-stackforge.png - :width: 100% - -- Stackforge was used for new unofficial projects, but retired on Aug 2015 -- Replaced by Big Tent initiative -- Used the same processes and tools as the main OpenStack projects - -Exercise -======== - -What kind of project do you want to contribute to? diff --git a/doc/upstream-training/source/_assets/big-tent-and-core-services.png b/doc/upstream-training/source/_assets/big-tent-and-core-services.png new file mode 100644 index 00000000..19fc6361 Binary files /dev/null and b/doc/upstream-training/source/_assets/big-tent-and-core-services.png differ