openstack/governance
Code Issues Proposed changes

Revises technical debt wording and fix typos in goals document

Browse Source 
Change-Id: I84eae419b2e15ecba49fcce0298af7380c3c90e3
This commit is contained in:
Anne Gentle 2016-08-16 18:04:36 -05:00
parent a47b61806c
commit f95733cde3
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
goals/index.rst
View File

@ -8,24 +8,24 @@ The pages in this part of the governance documentation describe
OpenStack-wide goals for each release series. OpenStack-wide goals for each release series.
We use these OpenStack-wide goals to achieve visible common changes, We use these OpenStack-wide goals to achieve visible common changes,
push for basic levels of consistency and user experience, and push for basic levels of consistency and user experience, and efficiently
efficiently repay the most obvious technical debt -- across all improve certain areas where technical debt payments have become too high
OpenStack projects. From a contributor perspective, they help bring -- across all OpenStack projects. From a contributor perspective, the goals
together the whole community behind some shared goals. We know this help unify the community's work as a whole, with some shared objectives. We
work is worthwhile, because these goals are how we achive the know this work is worthwhile, because these goals are how we achieve the
OpenStack mission together. We will build these goals based on our OpenStack mission together. We will build these goals based on our shared
shared values. values.
We know this process is working when We know this process is working when:
* Users and operators see OpenStack working well as a platform, rather * Users and operators see OpenStack working well as a platform, rather
than a collection of loosely related different projects. than a collection of loosely-related, different projects.
* We make progress on solving long-standing issues that would * We make progress on solving long-standing issues that would
otherwise have lingered indefinitely at different stages of otherwise have lingered indefinitely at different stages of
implementation in various projects. implementation in various projects.
* All contributors and projects know they are valued members of the * All contributors and projects know they are valued members of the
successful and thriving OpenStack community. successful and thriving OpenStack community.
* Marketing communication around release time is facilitated due to * We facilitate marketing communication around release time due to
successful completion of community-wide goals during the cycle. successful completion of community-wide goals during the cycle.
Process Details Process Details
@ -36,7 +36,7 @@ Identifying Goals
The goal process enables the community of OpenStack projects to The goal process enables the community of OpenStack projects to
surface common concerns and work out specific technical strategies for surface common concerns and work out specific technical strategies for
addressing these concerns. This community input will enable the TC to addressing these concerns. This community input enables the TC to
select specific community-wide goals for all projects to achieve select specific community-wide goals for all projects to achieve
during a development cycle. We need to consider the timing, cycle during a development cycle. We need to consider the timing, cycle
length, priority, and feasibility of the goals selected. length, priority, and feasibility of the goals selected.