Go to file

Ryan S. Brown 764862cbb2 Change template to match our historic usage

The template had the assumption that each guideline would get its own
file. The downside of this is that it would make our table of contents
hard to navigate. I propose that each file should be a collection of
related guidelines and each guideline should be a subheader within the
file.

It's still easy to link to specific guidelines with anchor links to
subheaders.

Change-Id: I6ac1587fe28cbc815dffb8d0e1dcc14f006107fa

2015-06-02 08:48:56 -04:00

doc/source

Change template to match our historic usage

2015-06-02 08:48:56 -04:00

guidelines

Merge "Adding guideline for evaluating api changes"

2015-05-20 17:37:37 +00:00

tests

Allow JSON files for JSON Schemas and JSON examples

2015-03-25 21:07:25 -05:00

.gitignore

Moves from markdown to rst

2014-10-22 16:24:41 +10:30

.gitreview

Moves from markdown to rst

2014-10-22 16:24:41 +10:30

.testr.conf

Moves from markdown to rst

2014-10-22 16:24:41 +10:30

LICENSE

Moves from markdown to rst

2014-10-22 16:24:41 +10:30

README.rst

Workflow documentation is now in infra-manual

2014-12-05 03:30:35 +00:00

requirements.txt

Add RSS feed

2014-12-12 09:22:02 +01:00

setup.cfg

Moves from markdown to rst

2014-10-22 16:24:41 +10:30

setup.py

Moves from markdown to rst

2014-10-22 16:24:41 +10:30

tox.ini

Moves from markdown to rst

2014-10-22 16:24:41 +10:30

README.rst

README

Openstack API Working Group documents

This repository contains documents from the OpenStack API working group, including guidelines and proposed rules concerning API consistency, naming conventions, and best practice recommendations.

Interested in contributing to the API conversations? Simply clone this repository and follow the [OpenStack code and review submission processes](http://docs.openstack.org/infra/manual/developers.html).