||7 months ago|
|doc/source||7 months ago|
|specs||7 months ago|
|.coveragerc||7 years ago|
|.gitignore||3 years ago|
|.gitreview||3 years ago|
|.mailmap||8 years ago|
|.testr.conf||8 years ago|
|CONTRIBUTING.rst||8 years ago|
|LICENSE||8 years ago|
|MANIFEST.in||8 years ago|
|README.rst||3 years ago|
|requirements.txt||2 years ago|
|setup.cfg||5 years ago|
|setup.py||5 years ago|
|template.rst||7 months ago|
|test-requirements.txt||5 years ago|
|tox.ini||3 years ago|
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
- Create a story in StoryBoard with a task affecting the opendev/infra-specs project
- 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.rstfor relevant documentation links). This change should also add an entry for the proposed spec document in the
Approved Design Specificationssection of the
- 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.
- When ready for final approval, request addition of a call for votes to the weekly infra meeting agenda.
- 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...
- Update the story, copying summary text of specification to there.
- Leave a comment linking to the published URL of the specification on the specs site.
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.