opendev
/
infra-specs
Code Issues Proposed changes
OpenStack Infrastructure Blueprint Repository
328 Commits 1 Branch 0 Tags 4.4 MiB
Python 100%
Go to file
James E. Blair ae010afc6f Add Matrix spec 
The Zuul project has agreed that it would like to move from OFTC to
a native Matrix room.  OpenDev can help facilitate that by providing
some services that keep our communities together.  This spec is a
description of how we can proceed.

Change-Id: I14233f8a35c470aa126dba2aa64d525fee30ed9a
 		2021-07-05 15:22:12 -07:00
doc/source Add Matrix spec 2021-07-05 15:22:12 -07:00
specs Add Matrix spec 2021-07-05 15:22:12 -07:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:23:23 +00:00
.gitignore Move from oslosphinx to openstackdocstheme 2019-05-15 08:14:34 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:26:02 +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 Update site URL 2019-05-30 21:00:18 +02:00
requirements.txt Bump blockdiag dep so that we build on newer python3 2020-02-21 12:43:28 -08:00
setup.cfg Update requirements for Sphinx 1.5 2017-03-02 19:11:26 +01:00
setup.py Update requirements for Sphinx 1.5 2017-03-02 19:11:26 +01:00
template.rst Add Gerrit Topic to the spec template 2015-03-03 11:18:10 -08:00
test-requirements.txt Update requirements for Sphinx 1.5 2017-03-02 19:11:26 +01:00
tox.ini Move from oslosphinx to openstackdocstheme 2019-05-15 08:14:34 -05: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 opendev/infra-specs project
  2. Propose a change to this repository and make sure Task: #<taskid> for the corresponding story's initial task is included as a footer in the commit message (see CONTRIBUTING.rst for relevant documentation links). This change should also add an entry for the proposed spec document in the Approved Design Specifications section of the doc/source/index.rst file.
  3. Once proposed, members of the community provide feedback through code review, and the specification should be revised until there seems to be some reasonable consensus as to its fitness.
  4. When ready for final approval, request addition of a call for votes to the weekly infra meeting agenda.
  5. If agreed by the meeting attendees, the chair will announce an approval deadline before which members of the Infrastructure Council are asked to cast their roll call votes on the proposal under review.

Once a specification is approved...

  1. Update the story, copying summary text of specification to there.
  2. Leave a comment linking to the published URL of the specification on the specs site.

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.