The pages in this part of the governance documentation describe OpenStack-wide goals for each release series.
We use these OpenStack-wide goals to achieve visible common changes, push for basic levels of consistency and user experience, and efficiently improve certain areas where technical debt payments have become too high – across all OpenStack projects. From a contributor perspective, the goals help unify the community’s work as a whole, with some shared objectives. We know this work is worthwhile, because these goals are how we achieve the OpenStack mission together. We will build these goals based on our shared values.
We know this process is working when:
The goal process enables the community of OpenStack projects to surface common concerns and work out specific technical strategies for addressing these concerns. This community input enables the TC to select specific community-wide goals for all projects to achieve during a development cycle. We need to consider the timing, cycle length, priority, and feasibility of the goals selected.
We will brainstorm goals before and at each summit, using feedback received from deployers, users, contributors, and PTLs. Those goals will be discussed on the mailing list to collect feedback about whether each goal is achievable and described completely. The TC will use that input to come to consensus and make the final decisions for OpenStack-wide goals for each cycle in time to allow planning and other discussion at the PTG event at the start of the cycle.
Goals are defined here in the governance documentation to ensure that we establish a common understanding of the expectations being set. Goal definitions should use the provided template so they are all formatted consistently. The goal definition does not take the place of any blueprints, spec documents, or other planning tools used within a project to track its work, but can be referenced from those documents.
To define goals for a release cycle, a TC member should set up the series directory in one patch, and then in follow-up patches TC members can propose specific goals. This separates the discussion for each goal onto its own review.
The actual goals shouldn’t be completely new proposals (things no one else in the community has seen before) because there will have been discussion in the course of reaching consensus.
After a goal is approved, each PTL is responsible for adding their planning artifact links to the goal document before the first milestone deadline. The planning artifact is likely to be a link to a spec or bug, and the completion artifact is likely to be a link to one or more committed patches.
This step is also the indication that a project team is signing up as agreeing to the goal and committing to do the work to complete the goal, within their project. That commitment may mean doing it themselves or may mean simply prioritizing reviews submitted by others. Either way, the commitment is to have the goal completed, and all teams are expected to commit the necessary resources to ensure that it is finished.
All project teams are expected to prioritize these goals above other work.
If the goal does not apply to a project or the project has already met the goal, the PTL should explain why that is the case, instead of linking to planning artifacts.
After a goal is completed, each PTL is responsible for ensuring that their completion artifacts are added to the goal document before the final release date for the cycle.
If a goal is not completed, that information should be added, along with any references needed to track when that work will be completed.