Migration to Storyboard

Sahara projects migrated to storyboard.openstack.org.
Replace the references to Launchpad, including the usage of
blueprints (apart from historical references).
Fix the bug link in the openstackdocstheme configuration.

Change-Id: Ib7060f888bc2a28690c4f9498f2925909ad75bc2

CONTRIBUTING.rst

@@ -15,6 +15,6 @@ the workflow documented at:
 
 Pull requests submitted through GitHub will be ignored.
 
-Bugs should be filed on Launchpad, not GitHub:
+Bugs should be filed on Storyboard, not GitHub:
 
-   https://bugs.launchpad.net/sahara
+   https://storyboard.openstack.org/#!/project/939

README.rst

@@ -52,10 +52,8 @@ list.
 Specifications are proposed for a given release by adding them to the
 ``specs/<release>`` directory and posting it for review. Not all approved
 blueprints will get fully implemented. The implementation status of a
-blueprint for a given release can be found by looking at the blueprint in
-launchpad::
-
-  http://blueprints.launchpad.net/sahara/<blueprint-name>
+blueprint for a given release can be found by looking at the tasks associated
+to the corresponding story in Storyboard.
 
 Incomplete specifications have to be re-proposed for every release. The review
 may be quick, but even if something was previously approved, it should be
@@ -67,8 +65,8 @@ completed entirely through Launchpad blueprints::
 
   http://blueprints.launchpad.net/sahara
 
-Please note, Launchpad blueprints are still used for tracking the
-current status of blueprints. For more information, see::
+Launchpad blueprints are no more used for tracking the
+current status of blueprints. For historical information, see::
 
   https://wiki.openstack.org/wiki/Blueprints
 

doc/source/conf.py

@@ -104,7 +104,7 @@ man_pages = []
 html_theme = 'openstackdocs'
 
 repository_name = 'openstack/sahara-specs'
-bug_project = 'sahara'
+bug_project = '939'
 bug_tag = 'spec'
 
 # Theme options are theme-specific and customize the look and feel of a theme

specs/template.rst

@@ -8,10 +8,6 @@
 Example Spec - The title of your blueprint
 ==========================================
 
-Include the URL of your launchpad blueprint:
-
-https://blueprints.launchpad.net/sahara/+spec/example
-
 Introduction paragraph -- why are we doing anything? A single paragraph of
 prose that operators can understand. The title and this first paragraph
 should be used as the subject line and body of the commit message
@@ -23,10 +19,6 @@ Some notes about using this template:
 
 * Please wrap text at 79 columns.
 
-* The filename in the git repository should match the launchpad URL, for
-  example a URL of: https://blueprints.launchpad.net/sahara/+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
 
@@ -200,10 +192,10 @@ If more than one person is working on the implementation, please designate the
 primary author and contact.
 
 Primary assignee:
-  <launchpad-id or None>
+  <openstack-id or None>
 
 Other contributors:
-  <launchpad-id or None>
+  <openstack-id or None>
 
 Work Items
 ----------