openstack/governance
Code Issues Proposed changes

provide more detail about the expectations we place on goal champions

Browse Source 
At least one of our goal champions was under the mistaken impression
that they were responsible for writing all of the patches for teams
that did not complete the goal themselves. This patch adds more detail
about what responsibility a champion has, and what things are not
their responsibility.

Story: #2001706
Task: #8699
Change-Id: Ie00f793378ed2ec870210ffd480f29a510a427d5
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann
2018-04-24 16:40:21 -04:00
parent 0125251681
commit 0ccf91c2c7
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
goals/index.rst
View File

@@ -114,6 +114,24 @@ artifacts, 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.
Goal Champion Responsibilities
------------------------------
The "goal champion" is responsible for guiding teams to implement a
goal, but is not responsible for doing the work themselves.
The champion is typically somewhat familiar with the technical issues
involved in a goal, at least enough to help teams find the information
they need. The champion does not need to be an expert with the tools
or libraries used for the goal, but some experience does help.
The champion is responsible for configuring StoryBoard to track
progress on their goal, and then ensuring that it is kept up to date
as work progresses.
The champion should check in with project teams regularly to ensure
they are able to make progress on the work and have not become stuck.
Release Cycles
==============