openstack/zaqar-specs
Code Issues Proposed changes

Rename marconi to zaqar

Browse Source 
Rename everywhere, sync template.rst with version in specs.

Adjust publishing URL, specs will show up on specs.openstack.org.

Create link to specs directory so that building works - like it's done
in other specs repositories.

Implements blueprint: project-rename
Change-Id: Ife866fafb9e1d94935bd0c02949e1cd9d5a9c281
This commit is contained in:
Andreas Jaeger 2014-08-17 06:34:02 +02:00
parent 287bfff75a
commit a277ed550b
12 changed files with 58 additions and 62 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.coveragerc
View File

@ -1,7 +1,7 @@
[run] [run]
branch = True branch = True
source = marconi-specs source = zaqar-specs
omit = marconi-specs/tests/*,marconi-specs/openstack/* omit = zaqar-specs/tests/*,zaqar-specs/openstack/*
[report] [report]
ignore-errors = True ignore-errors = True

4
CONTRIBUTING.rst
View File

@ -1,5 +1,5 @@
============================================= =============================================
Contributing to: marconi-specs Contributing to: zaqar-specs
============================================= =============================================
If you would like to contribute to the development of OpenStack, If you would like to contribute to the development of OpenStack,
@ -18,4 +18,4 @@ Pull requests submitted through GitHub will be ignored.
Bugs should be filed on Launchpad, not GitHub: Bugs should be filed on Launchpad, not GitHub:
https://bugs.launchpad.net/marconi https://bugs.launchpad.net/zaqar

6
README.rst
View File

@ -1,11 +1,11 @@
=============================== ===============================
marconi-specs zaqar-specs
=============================== ===============================
Queuing Service (Marconi) Specifications Queuing Service (Zaqar) Specifications
* Free software: Apache license * Free software: Apache license
* Documentation: http://docs.openstack.org/developer/marconi-specs * Documentation: http://specs.openstack.org/openstack/zaqar-specs
Features Features
-------- --------

4
doc/source/conf.py
View File

@ -45,8 +45,8 @@ source_suffix = '.rst'
master_doc = 'index' master_doc = 'index'
# General information about the project. # General information about the project.
project = u'marconi-specs' project = u'zaqar-specs'
copyright = u'2013, OpenStack Foundation' copyright = u'2014, OpenStack Foundation'
# If true, '()' will be appended to :func: etc. cross-reference text. # If true, '()' will be appended to :func: etc. cross-reference text.
add_function_parentheses = True add_function_parentheses = True

4
doc/source/contributing.rst
View File

@ -1,5 +1,5 @@
============================================= =============================================
Contributing to: marconi-specs Contributing to: zaqar-specs
============================================= =============================================
If you would like to contribute to the development of OpenStack, If you would like to contribute to the development of OpenStack,
@ -18,4 +18,4 @@ Pull requests submitted through GitHub will be ignored.
Bugs should be filed on Launchpad, not GitHub: Bugs should be filed on Launchpad, not GitHub:
https://bugs.launchpad.net/marconi https://bugs.launchpad.net/zaqar

11
doc/source/index.rst
View File

@ -1,19 +1,14 @@
.. marconi-specs documentation master file, created by zaqar-specs Design Specifications
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.
marconi-specs Design Specifications
================================================== ==================================================
.. toctree:: .. toctree::
:glob: :glob:
:maxdepth: 2 :maxdepth: 2
../../specs/* specs/*
marconi-specs Repository Information zaqar-specs Repository Information
=================================================== ===================================================
.. toctree:: .. toctree::

6
doc/source/readme.rst
View File

@ -1,11 +1,11 @@
=============================== ===============================
marconi-specs zaqar-specs
=============================== ===============================
Queuing Service (Marconi) Specifications Queuing Service (Zaqar) Specifications
* Free software: Apache license * Free software: Apache license
* Documentation: http://docs.openstack.org/developer/marconi-specs * Documentation: http://specs.openstack.org/openstack/zaqar-specs
Features Features
-------- --------

1
doc/source/specs Symbolic link
View File

@ -0,0 +1 @@
../../specs

32
doc/source/template.rst
View File

@ -1,14 +1,12 @@
::
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 This template should be in ReSTructured text. The filename in the git
repository should match the launchpad URL, for example a URL of repository should match the launchpad URL, for example a URL of
https://blueprints.launchpad.net/marconi/+spec/awesome-thing should be named https://blueprints.launchpad.net/zaqar/+spec/awesome-thing should be named
awesome-thing.rst . Please do not delete any of the sections in this 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 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 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 To test out your formatting, see http://www.tele3.cz/jbar/rest/rest.html
@ -18,7 +16,7 @@ http://creativecommons.org/licenses/by/3.0/legalcode
Include the URL of your launchpad blueprint: Include the URL of your launchpad blueprint:
https://blueprints.launchpad.net//+spec/example https://blueprints.launchpad.net/zaqar/+spec/example
Introduction paragraph -- why are we doing anything? Introduction paragraph -- why are we doing anything?
@ -36,8 +34,6 @@ propose to solve this problem?
If this is one part of a larger effort make it clear where this piece ends. In 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? other words, what's the scope of this effort?
Include where in the marconi tree hierarchy this will reside.
Alternatives Alternatives
------------ ------------
@ -59,14 +55,14 @@ primary author and contact.
Primary assignee: Primary assignee:
<launchpad-id or None> <launchpad-id or None>
Can optionally can list additional ids if they intend on doing Can list additional ids if they intend on doing substantial implementation work
substantial implementation work on this blueprint. on this blueprint.
Milestones Milestones
---------- ----------
Target Milestone for completion: Target Milestone for completion:
Juno-1 Juno-2
Work Items Work Items
---------- ----------
@ -79,8 +75,12 @@ but we're mostly trying to understand the timeline for implementation.
Dependencies Dependencies
============ ============
- Include specific references to specs and/or blueprints in marconi, or in other - Include specific references to specs and/or blueprints in zaqar, or in other
projects, that this one either depends on or is related to. projects, that this one either depends on or is related to.
- Does this feature require any new library dependencies or code otherwise not .. note::
included in OpenStack? Or does it depend on a specific version of library?
This work is licensed under a Creative Commons Attribution 3.0
Unported License.
http://creativecommons.org/licenses/by/3.0/legalcode

4
setup.cfg
View File

@ -1,6 +1,6 @@
[metadata] [metadata]
name = marconi-specs name = zaqar-specs
summary = Queuing Service (Marconi) Specifications summary = Queuing Service (Zaqar) Specifications
description-file = description-file =
README.rst README.rst
author = OpenStack author = OpenStack

6
specs/template.rst
View File

@ -1,7 +1,7 @@
.. ..
This template should be in ReSTructured text. The filename in the git This template should be in ReSTructured text. The filename in the git
repository should match the launchpad URL, for example a URL of repository should match the launchpad URL, for example a URL of
https://blueprints.launchpad.net/marconi/+spec/awesome-thing should be named https://blueprints.launchpad.net/zaqar/+spec/awesome-thing should be named
awesome-thing.rst. awesome-thing.rst.
Please do not delete any of the sections in this Please do not delete any of the sections in this
@ -16,7 +16,7 @@
Include the URL of your launchpad blueprint: Include the URL of your launchpad blueprint:
https://blueprints.launchpad.net/marconi/+spec/example https://blueprints.launchpad.net/zaqar/+spec/example
Introduction paragraph -- why are we doing anything? Introduction paragraph -- why are we doing anything?
@ -75,7 +75,7 @@ but we're mostly trying to understand the timeline for implementation.
Dependencies Dependencies
============ ============
- Include specific references to specs and/or blueprints in marconi, or in other - Include specific references to specs and/or blueprints in zaqar, or in other
projects, that this one either depends on or is related to. projects, that this one either depends on or is related to.
.. note:: .. note::

32
template.rst
View File

@ -1,14 +1,12 @@
::
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 This template should be in ReSTructured text. The filename in the git
repository should match the launchpad URL, for example a URL of repository should match the launchpad URL, for example a URL of
https://blueprints.launchpad.net/marconi/+spec/awesome-thing should be named https://blueprints.launchpad.net/zaqar/+spec/awesome-thing should be named
awesome-thing.rst . Please do not delete any of the sections in this 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 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 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 To test out your formatting, see http://www.tele3.cz/jbar/rest/rest.html
@ -18,7 +16,7 @@ http://creativecommons.org/licenses/by/3.0/legalcode
Include the URL of your launchpad blueprint: Include the URL of your launchpad blueprint:
https://blueprints.launchpad.net//+spec/example https://blueprints.launchpad.net/zaqar/+spec/example
Introduction paragraph -- why are we doing anything? Introduction paragraph -- why are we doing anything?
@ -36,8 +34,6 @@ propose to solve this problem?
If this is one part of a larger effort make it clear where this piece ends. In 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? other words, what's the scope of this effort?
Include where in the marconi tree hierarchy this will reside.
Alternatives Alternatives
------------ ------------
@ -59,14 +55,14 @@ primary author and contact.
Primary assignee: Primary assignee:
<launchpad-id or None> <launchpad-id or None>
Can optionally can list additional ids if they intend on doing Can list additional ids if they intend on doing substantial implementation work
substantial implementation work on this blueprint. on this blueprint.
Milestones Milestones
---------- ----------
Target Milestone for completion: Target Milestone for completion:
Juno-1 Juno-2
Work Items Work Items
---------- ----------
@ -79,8 +75,12 @@ but we're mostly trying to understand the timeline for implementation.
Dependencies Dependencies
============ ============
- Include specific references to specs and/or blueprints in marconi, or in other - Include specific references to specs and/or blueprints in zaqar, or in other
projects, that this one either depends on or is related to. projects, that this one either depends on or is related to.
- Does this feature require any new library dependencies or code otherwise not .. note::
included in OpenStack? Or does it depend on a specific version of library?
This work is licensed under a Creative Commons Attribution 3.0
Unported License.
http://creativecommons.org/licenses/by/3.0/legalcode