diff --git a/doc/upstream-training/source/slides/howitsmade-governance.rst b/doc/upstream-training/source/slides/howitsmade-governance.rst new file mode 100644 index 00000000..b43e2fc8 --- /dev/null +++ b/doc/upstream-training/source/slides/howitsmade-governance.rst @@ -0,0 +1,118 @@ +==================== +OpenStack Governance +==================== + +.. image:: ./_assets/os_background.png + :class: fill + :width: 100% + +OpenStack Foundation +==================== + +- Nonprofit foundation created to "develop, support, protect, and promote" + OpenStack + + - Individual members: all of us + - Institutional members: Platinum and Gold sponsors + - Further supporting companies and organisations + +- Multi-layer group of leadership + + - Board of directors + - Technical Committee + - User Committee + +Board of Directors +================== + +- Startegic and financial oversight +- Representatives are elected from + + - Platinum member companies + - Gold member companies + - Individual Foundation members + +Technical Committee ("TC") +========================== + +- Provides + + - Oversight over the OpenStack projects + - Technical leadership + +- Enforces OpenStack ideals + + - Openness + - Transparency + - Commonality + - Integration + - Quality + +- Handles cross-project related topics and issues + +.. note:: + + - https://www.openstack.org/foundation/tech-committee/ + +User Committe ("UC") +==================== + +- Represents OpenStack users +- Gathers feedback and consolidates requirements +- Further details are in a later session + +Exercise +======== + +- Find the current members of the Board of Directors, TC and UC + +OpenStack Project Teams +======================= + +- Teams of people who + + - Produce *deliverables* to achieve a clearly stated *objective* + - Using the common tools (code repository, bug tracker, CI system, etc.) + - Work towards OpenStack's mission + +- Teams in OpenStack can be freely created as they are needed +- Teams of official projects are under the authority of the TC +- The official list of projects: + + - http://governance.openstack.org/reference/projects/ + +.. note:: + + - Source file is hosted in the `governance repository `_ + +Active Technical Contributor (ATC) +================================== + +- Subset of the Foundation Individual Members +- Committed a change over the last two 6-month release cycles + + - Code or documentation contribution to any of the official project + repositories + - Apply for ATC role + + - Bug triagers + - Technical documentation writers + +- TC seats are elected from and by the group of ATC's + +Active Project Contributor (APC) +================================ + +- Actively contributing to one or more OpenStack projects + + - Also ATC + - Attends project meetings + - Participates in project related mail threads on the mailing lists + +Project Team Leads (PTLs) +========================= + +- Manage day-to-day operations +- Drive the program goals +- Resolve technical disputes +- Elected from and by the group of APC's diff --git a/doc/upstream-training/source/slides/howitsmade-technical-committee.rst b/doc/upstream-training/source/slides/howitsmade-technical-committee.rst deleted file mode 100644 index eced62cc..00000000 --- a/doc/upstream-training/source/slides/howitsmade-technical-committee.rst +++ /dev/null @@ -1,127 +0,0 @@ -==================== -OpenStack Governance -==================== - -.. image:: ./_assets/os_background.png - :class: fill - :width: 100% - -OpenStack Foundation -==================== - -- Nonprofit foundation created to "develop, support, protect, and promote" - OpenStack - - - Individual members: all of us - - Institutional members: Platinum and Gold sponsors - - Led by a board of directors - - Creates other committees for day-to-day leadership - - - Technical Committee - - User Committee - -The role of the Technical Committee -=================================== - -The Technical Committee ("TC") is tasked with providing technical leadership -over all the OpenStack projects. It enforces OpenStack ideals (Openness, -Transparency, Commonality, Integration, Quality), decides on issues affecting -multiple programs, forms an ultimate appeals board for technical decisions, -and generally has oversight over the OpenStack project entirely. - -- https://www.openstack.org/foundation/tech-committee/ - -Technical Committee Members -=========================== - -.. rst-class:: colleft - -.. image:: ./_assets/03-01-TC1.png - -.. rst-class:: colright - -.. image:: ./_assets/03-01-TC2.png - -The role of the User Committee -============================== - -- Consolidate user requirements and present these to the management - board and technical committee -- Provide guidance for the development teams where user feedback is requested -- Track OpenStack deployments and usage, helping to share user stories - and experiences -- Work with the user groups worldwide to keep the OpenStack community vibrant - and informed -- https://www.openstack.org/foundation/user-committee/ - -OpenStack Project Teams -======================= - -Project Teams are teams of *people* using *tools* (code repository, -bug tracker, etc) and coordinated *processes* to produce a number of -*deliverables*, in order to achieve a clearly stated *objective* according to -OpenStack's mission. - -- Teams in OpenStack can be freely created as they are needed -- Teams of official projects are under the authority of the Technical Committee -- The official list of projects: - - - http://governance.openstack.org/reference/projects/ - -.. note:: - - - Source file is hosted in the `governance repository `_ - -Meetings -======== - -- Governance/TechnicalCommittee#Meeting - - - https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting - -- Agenda -- Motions - -.. image:: ./_assets/03-02-IRCmeeting.png - :width: 100% - -Exercise -======== - -- Exercise - - - read tc.2014-04-01-20.03.log.html and briefly comment on keystone document - -Active Technical Contributor (ATC) -====================================== - -The TC seats are elected by the Active Technical Contributors ("ATC"), which -are a subset of the Foundation Individual Members. Individual Members who -committed a change to a repository under any of the official OpenStack -programs (as defined above) over the last two 6-month release cycles are -automatically considered an ATC. - -- TC seats are elected by ATC -- Same as APC -- Bug triagers, technical documentation writers, etc can exceptionally apply - for ATC - -Active Project Contributor (APC) -================================= - -- Voters for a given program PTL -- Subset of the Foundation Individual Member -- Committed a change over the last two 6-month release cycles -- Candidacy for the corresponding program PTL election - -Project Team Leads (PTLs) -========================= - -- Manage day-to-day operations -- Drive the program goals -- Resolve technical disputes - -Exercise -======== - -`Each APC/ATC in the class should add a URL to the etherpad proving it` diff --git a/doc/upstream-training/source/slides/slide-index.rst b/doc/upstream-training/source/slides/slide-index.rst index 4eb9fdd5..0c6db1ae 100644 --- a/doc/upstream-training/source/slides/slide-index.rst +++ b/doc/upstream-training/source/slides/slide-index.rst @@ -27,7 +27,7 @@ How OpenStack is Made howitsmade-metrics.rst howitsmade-events.rst howitsmade-release-cycle.rst - howitsmade-technical-committee.rst + howitsmade-governance.rst howitsmade-communication.rst branching-model.rst diff --git a/doc/upstream-training/source/website/index.rst b/doc/upstream-training/source/website/index.rst index 745c8c5d..7392a7ad 100644 --- a/doc/upstream-training/source/website/index.rst +++ b/doc/upstream-training/source/website/index.rst @@ -109,7 +109,7 @@ How OpenStack is Made * `OpenStack Events `_ * `Metrics `_ * `Release cycle `_ -* `OpenStack Governance `_ +* `OpenStack Governance `_ * `Communication `_ Workflow and Tools for Participation