Merge "[upstream] Reduce/update content for official-projects"

doc/upstream-training/source/slides/howitsmade-official-projects.rst

@@ -18,14 +18,21 @@ Official OpenStack projects
  - Testable on its own
  - Dashboard (horizon) and DevStack provide plugin interface for easy
    integration
+ - Projects are tracked in the
+   `Project Navigator <https://www.openstack.org/software/project-navigator>`_
 
 - Big Tent is a code name for the official OpenStack projects
 
+ .. note::
+
+  - Project Navigator doesn't include all OpenStack Projects at this time.
+    Currently limited to core projects and more mature Big Tent projects.
+
 Benefits of being an Official OpenStack project
 ===============================================
 - Contributors get to vote in the Technical Committee election
 - Can publish to docs.openstack.org and developer.openstack.org
-- The teams get space on OpenStack Summits and Project Team Gatherings (PTG)
+- The teams get space at OpenStack Summits and Project Team Gatherings (PTG)
 - Get marketing from the OpenStack Foundation
 - Can participate in common programs, like mentoring and internship to help
   with on boarding
@@ -42,39 +49,6 @@ Benefits of being an Official OpenStack project
   - Official OpenStack projects can participate by offering topics and mentors
     for the interns who sign up for this program.
 
-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
@@ -83,9 +57,9 @@ Core and Optional Services
   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
+
+ - Full list of Official OpenStack Project Teams:
+   https://governance.openstack.org/tc/reference/projects/index.html
 
 Core and Optional Services
 ==========================
@@ -93,43 +67,27 @@ 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?
+- Find the requirements that must be met to be an official OpenStack project
+
+- Tags can be associated with projects.  Find out what tags are and find the
+  current list of available tags.
+
+.. note::
+ - https://governance.openstack.org/tc/reference/new-projects-requirements.html
+ - An official project is aligned with the OpenStack Mission if it
+
+  - has a clear and defined scope
+  - provides a cloud infrastructure service or directly builds on an
+    existing OpenStack cloud infrastructure service
+  - Follows/observes the four opens: Source, Community, Development, Design
+
+ - http://governance.openstack.org/reference/tags/index.html
+
+  - Describe the artifacts created by an OpenStack community team
+  - Processes followed, release management, etc.
+
 
-Write it on Etherpad.