opendev/infra-specs
Code Issues Proposed changes
5a29a334d7
infra-specs/doc/source
History
Jeremy Stanley 59f796aef0 Add a help-wanted section 
To make it easier to find specs which have nobody driving them,
create a separate "Help Wanted" section where approved specs which
are neither implemented nor abandoned but lack assignees (and
possibly other details) are listed together.

Change-Id: Id2ffcc41a6d35b67b0d29dc75256052aebf86792
2017-06-06 14:31:43 +00:00
..
conf.py Use the current date for the copyright statement 2014-09-10 16:04:37 -04:00
contributing.rst Initial commit 2014-06-10 16:25:32 -07:00
index.rst Add a help-wanted section 2017-06-06 14:31:43 +00:00
readme.rst Initial commit 2014-06-10 16:25:32 -07:00
specs Initial commit 2014-06-10 16:25:32 -07:00
template.rst Initial commit 2014-06-10 16:25:32 -07:00

readme.rst

Infra Specs Repository

This is a git repository for doing design review on enhancements to the OpenStack Project Infrastructure. This provides an ability to ensure that everyone has signed off on the approach to solving a problem early on.

Expected Work Flow

  1. Create a story in StoryBoard with a task affecting the infra-specs project.
  2. Propose a change to infra-specs repository (ensure Story:<story number> is in the commit message).
  3. Leave a comment on the story with the Gerrit URL of the specification.
  4. Review happens on proposal by infra-core members and others.
  5. When ready for final approval, bring forward the proposed item to the infra meeting.

Once a specification is approved...

  1. Update story, copy summary text of specification to there.
  2. Leave a comment to the git address of the specification.

Revisiting Specifications

We don't always get everything right the first time. If we realize we need to revisit a specification because something changed, either we now know more, or a new idea came in which we should embrace, we'll manage this by proposing an update to the specification in question.