From 0ce8d353a420620ac9544ae5e36dcca55212819b Mon Sep 17 00:00:00 2001
From: Denis Makogon <dmakogon@mirantis.com>
Date: Wed, 24 Sep 2014 17:11:50 +0300
Subject: [PATCH] Fix Table of Contents and add Kilo spec location

Added a kilo directory for specs for Kilo. Also fixed the
Table of contents.

Co-Authored-By: Nikhil Manchanda <SlickNik@gmail.com>
Change-Id: I7cc337c4f290eec68baad73b730bc05af48c7423
---
 README.rst                 |  5 ---
 doc/source/index.rst       | 29 ++++++++-----
 doc/source/template.rst    | 87 --------------------------------------
 specs/kilo/.gitignore      |  0
 specs/kilo/placeholder.rst |  3 ++
 template.rst               | 86 -------------------------------------
 6 files changed, 21 insertions(+), 189 deletions(-)
 delete mode 100644 doc/source/template.rst
 create mode 100644 specs/kilo/.gitignore
 create mode 100644 specs/kilo/placeholder.rst
 delete mode 100644 template.rst

diff --git a/README.rst b/README.rst
index a202ff9..264edc6 100644
--- a/README.rst
+++ b/README.rst
@@ -6,8 +6,3 @@ OpenStack Database Service (Trove) Specifications
 
 * Free software: Apache license
 * Documentation: http://docs.openstack.org/developer/trove-specs
-
-Features
---------
-
-* TODO
\ No newline at end of file
diff --git a/doc/source/index.rst b/doc/source/index.rst
index 07f413e..5cf2203 100644
--- a/doc/source/index.rst
+++ b/doc/source/index.rst
@@ -1,29 +1,36 @@
-.. trove-specs documentation master file, created by
-   sphinx-quickstart on Tue Jul  9 22:26:36 2013.
-   You can adapt this file completely to your liking, but it should at least
-   contain the root `toctree` directive.
+.. trove-specs documentation master file
 
-trove-specs Design Specifications
-==================================================
+============================
+Trove Project Specifications
+============================
+
+Contents:
 
 .. toctree::
    :glob:
-   :maxdepth: 2
+   :maxdepth: 1
 
    specs/*
 
+Kilo approved specs:
 
-trove-specs Repository Information
-===================================================
+.. toctree::
+   :glob:
+   :maxdepth: 1
+
+   specs/kilo/*
+
+======================
+Repository Information
+======================
 
 .. toctree::
    :maxdepth: 2
 
    README <readme>
    contributing
-   Sample Template <template>
-
 
+==================
 Indices and tables
 ==================
 
diff --git a/doc/source/template.rst b/doc/source/template.rst
deleted file mode 100644
index c89b8cb..0000000
--- a/doc/source/template.rst
+++ /dev/null
@@ -1,87 +0,0 @@
-..
- This work is licensed under a Creative Commons Attribution 3.0 Unported
- License.
-
- http://creativecommons.org/licenses/by/3.0/legalcode
-..
-
-  This template should be in ReSTructured text. The filename in the git
-  repository should match the launchpad URL, for example a URL of
-  https://blueprints.launchpad.net/trove/+spec/awesome-thing should be named
-  awesome-thing.rst .  Please do not delete any of the sections in this
-  template.  If you have nothing to say for a whole section, just write: None
-  For help with syntax, see http://sphinx-doc.org/rest.html
-  To test out your formatting, see http://www.tele3.cz/jbar/rest/rest.html
-
-=============================
- The title of your blueprint
-=============================
-
-Include the URL of your launchpad blueprint:
-
-https://blueprints.launchpad.net//+spec/example
-
-Introduction paragraph -- why are we doing anything?
-
-Problem description
-===================
-
-A detailed description of the problem.
-
-Proposed change
-===============
-
-Here is where you cover the change you propose to make in detail. How do you
-propose to solve this problem?
-
-If this is one part of a larger effort make it clear where this piece ends. In
-other words, what's the scope of this effort?
-
-Include where in the trove tree hierarchy this will reside.
-
-Alternatives
-------------
-
-This is an optional section, where it does apply we'd just like a demonstration
-that some thought has been put into why the proposed approach is the best one.
-
-Implementation
-==============
-
-Assignee(s)
------------
-
-Who is leading the writing of the code? Or is this a blueprint where you're
-throwing it out there to see who picks it up?
-
-If more than one person is working on the implementation, please designate the
-primary author and contact.
-
-Primary assignee:
-  <launchpad-id or None>
-
-Can optionally can list additional ids if they intend on doing
-substantial implementation work on this blueprint.
-
-Milestones
-----------
-
-Target Milestone for completion:
-  Juno-1
-
-Work Items
-----------
-
-Work items or tasks -- break the feature up into the things that need to be
-done to implement it. Those parts might end up being done by different people,
-but we're mostly trying to understand the timeline for implementation.
-
-
-Dependencies
-============
-
-- Include specific references to specs and/or blueprints in trove, or in other
-  projects, that this one either depends on or is related to.
-
-- Does this feature require any new library dependencies or code otherwise not
-  included in OpenStack? Or does it depend on a specific version of library?
diff --git a/specs/kilo/.gitignore b/specs/kilo/.gitignore
new file mode 100644
index 0000000..e69de29
diff --git a/specs/kilo/placeholder.rst b/specs/kilo/placeholder.rst
new file mode 100644
index 0000000..b6a349a
--- /dev/null
+++ b/specs/kilo/placeholder.rst
@@ -0,0 +1,3 @@
+======================
+Placeholder Kilo Specs
+======================
diff --git a/template.rst b/template.rst
deleted file mode 100644
index 2f3567b..0000000
--- a/template.rst
+++ /dev/null
@@ -1,86 +0,0 @@
-::
-
-This work is licensed under a Creative Commons Attribution 3.0 Unported License.
-http://creativecommons.org/licenses/by/3.0/legalcode
-
-..
-  This template should be in ReSTructured text. The filename in the git
-  repository should match the launchpad URL, for example a URL of
-  https://blueprints.launchpad.net/trove/+spec/awesome-thing should be named
-  awesome-thing.rst .  Please do not delete any of the sections in this
-  template.  If you have nothing to say for a whole section, just write: None
-  For help with syntax, see http://sphinx-doc.org/rest.html
-  To test out your formatting, see http://www.tele3.cz/jbar/rest/rest.html
-
-=============================
- The title of your blueprint
-=============================
-
-Include the URL of your launchpad blueprint:
-
-https://blueprints.launchpad.net//+spec/example
-
-Introduction paragraph -- why are we doing anything?
-
-Problem description
-===================
-
-A detailed description of the problem.
-
-Proposed change
-===============
-
-Here is where you cover the change you propose to make in detail. How do you
-propose to solve this problem?
-
-If this is one part of a larger effort make it clear where this piece ends. In
-other words, what's the scope of this effort?
-
-Include where in the trove tree hierarchy this will reside.
-
-Alternatives
-------------
-
-This is an optional section, where it does apply we'd just like a demonstration
-that some thought has been put into why the proposed approach is the best one.
-
-Implementation
-==============
-
-Assignee(s)
------------
-
-Who is leading the writing of the code? Or is this a blueprint where you're
-throwing it out there to see who picks it up?
-
-If more than one person is working on the implementation, please designate the
-primary author and contact.
-
-Primary assignee:
-  <launchpad-id or None>
-
-Can optionally can list additional ids if they intend on doing
-substantial implementation work on this blueprint.
-
-Milestones
-----------
-
-Target Milestone for completion:
-  Juno-1
-
-Work Items
-----------
-
-Work items or tasks -- break the feature up into the things that need to be
-done to implement it. Those parts might end up being done by different people,
-but we're mostly trying to understand the timeline for implementation.
-
-
-Dependencies
-============
-
-- Include specific references to specs and/or blueprints in trove, or in other
-  projects, that this one either depends on or is related to.
-
-- Does this feature require any new library dependencies or code otherwise not
-  included in OpenStack? Or does it depend on a specific version of library?
\ No newline at end of file