From 209e0ae262a04b4632e819693735f8e3cc0db28c Mon Sep 17 00:00:00 2001 From: Evgeniy L Date: Tue, 19 Jan 2016 12:39:52 +0300 Subject: [PATCH] Fix rendering of specs by sphinx Create symlink which is linked to directory in the root of the repository. Change-Id: I35880d9f1a8c41c55477bad25b1be972cc48bb63 Closes-bug: #1535605 --- doc/source/specs | 1 + doc/source/template.rst | 86 ----------------------------------------- 2 files changed, 1 insertion(+), 86 deletions(-) create mode 120000 doc/source/specs delete mode 100644 doc/source/template.rst diff --git a/doc/source/specs b/doc/source/specs new file mode 120000 index 0000000..87a4030 --- /dev/null +++ b/doc/source/specs @@ -0,0 +1 @@ +../../specs \ No newline at end of file diff --git a/doc/source/template.rst b/doc/source/template.rst deleted file mode 100644 index 5f3c29a..0000000 --- a/doc/source/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/bareon/+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 bareon 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: - - -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 bareon, 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?