Thierry Carrez 38081eed9a Make governance.o.o a neutral governance website
The governance.openstack.org website was initially created
to publish Technical Committee governance documents. However
since then it is also used to publish User committee documents
(under /uc) and election details (under /election). Those are
not very discoverable and the layout makes the UC look like a
second-class governance citizen.

This change proposes to put the Technical Committee documents
under /tc, to mimic what is done with the other sections. The
index page for governance.openstack.org would become a neutral
page generally explaining governance and pointing to the various
subsites. Proper redirects would be put in place to avoid breaking
existing links.

Change-Id: I9b542f94c42ad5dcf23cefae828e5a4b5fa698ec
2016-10-05 16:19:24 +02:00
2014-06-10 16:25:32 -07:00
2014-05-20 16:36:13 +00:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2015-11-16 16:37:06 +00:00
2014-09-10 16:04:35 -04:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00

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.

Description
OpenStack Infrastructure Blueprint Repository
Readme 4.4 MiB
Languages
Python 100%