opendev/infra-specs
Code Issues Proposed changes
OpenStack Infrastructure Blueprint Repository
206 Commits 1 Branch 0 Tags 4.4 MiB
Python 100%
47b447456e
Go to file
Jeremy Stanley 47b447456e Prioritize Docs Publishing via AFS 
Since the hosting situation with docs.openstack.org is starting to
come into question, this effort is more urgent. We should make it an
official team priority.

Change-Id: I050facef66140312ee37d0407de924b1e883596f
2016-09-06 19:20:48 +00:00
doc/source Prioritize Docs Publishing via AFS 2016-09-06 19:20:48 +00:00
specs Prioritize Docs Publishing via AFS 2016-09-06 19:20:48 +00:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:23:23 +00:00
.gitignore Initial commit 2014-06-10 16:25:32 -07:00
.gitreview Added .gitreview 2014-05-20 16:36:13 +00:00
.mailmap Initial commit 2014-06-10 16:25:32 -07:00
.testr.conf Initial commit 2014-06-10 16:25:32 -07:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 11:56:28 -08:00
LICENSE Initial commit 2014-06-10 16:25:32 -07:00
MANIFEST.in Initial commit 2014-06-10 16:25:32 -07:00
README.rst add storyboard link to instructions 2015-11-16 16:37:06 +00:00
requirements.txt Add RSS feed 2014-09-10 16:04:35 -04:00
setup.cfg Initial commit 2014-06-10 16:25:32 -07:00
setup.py Initial commit 2014-06-10 16:25:32 -07:00
template.rst Add Gerrit Topic to the spec template 2015-03-03 11:18:10 -08:00
test-requirements.txt Initial commit 2014-06-10 16:25:32 -07:00
tox.ini 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.