openstack/governance
Code Issues Proposed changes

Clarify TC goal-setting role

Browse Source 
Current language did not make it clear enough that it is
part of the TC's role to paint desirable, achievable goals
for our community as a whole, beyond just per-cycle release
goals.

Change-Id: Ib50f4978db8057d05255bbcf144ac5adee0c1fef
This commit is contained in:
Thierry Carrez 2019-02-14 13:50:07 +01:00
parent dcd705b172
commit da5556c526
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
reference/role-of-the-tc.rst
View File

@ -71,20 +71,20 @@ designating sections of code which are required to be present in an
OpenStack installation in order for it to be eligible to use the "OpenStack OpenStack installation in order for it to be eligible to use the "OpenStack
Powered" trademark. Powered" trademark.
Encouraging a unified OpenStack experience Defining global technical goals
========================================== ===============================
While most technical details are handled at the project team level, you While most technical details are handled at the project team level, you
still need a body caring about the "OpenStack" experience, beyond each still need a body caring about the "OpenStack" experience, beyond each
component user experience. It is part of the TC role to take that step component user experience. It is part of the TC role to take that step
back and consider OpenStack as "one platform" that users and operators back, consider OpenStack as "one platform" that users and operators
choose to leverage. This includes looking at gaps between established choose to leverage, and define reasonable technical goals for the
project teams, driving a common user experience (common operational OpenStack community as a whole. This includes looking at gaps between
behavior, limited dependencies, base quality levels, minimum feature established project teams, driving a common user experience (common
set...), pushing cross-project initiatives and influencing its general operational behavior, limited dependencies, base quality levels, minimum
direction. One way to achieve that is through the definition of OpenStack feature set...), pushing cross-project initiatives and influencing its
:doc:`release goals <../goals/index>`. general direction. One way to achieve that is through the definition of
OpenStack :doc:`release goals <../goals/index>`.
Ensuring a healthy, open collaboration Ensuring a healthy, open collaboration
====================================== ======================================