Go to file

Jeremy Stanley 194655bf51 PTG Bot

We will host a production instance of the PTG event scheduling bot.

Change-Id: I96f7bcf05f2185cd590c9ef97c4ce7312dd244e8
Story: #2001067
Task: #4677

2017-06-13 18:47:39 +00:00

doc/source

PTG Bot

2017-06-13 18:47:39 +00:00

specs

PTG Bot

2017-06-13 18:47:39 +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

Block sphinx 1.6.1

2017-05-23 08:46:10 -07: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

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

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

Once a specification is approved...

Update story, copy summary text of specification to there.
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.