openstack/openstack-manuals
Code Issues Proposed changes

[Contributor] Update Launchpad info for doc-tools

Browse Source 
Tools and theme bugs are now being tracked in
the openstack-doc-tools project on Launchpad.

Change-Id: I80a36d87b48cef397a882f0c275c881bfb3ebaed
This commit is contained in:
Brian Moss 2017-02-17 10:17:46 +10:00
parent 76b9a55034
commit 144587cca4
4 changed files with 20 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
doc/contributor-guide/source/doc-bugs.rst
View File

@ -67,21 +67,22 @@ information, see `Documentation/DocImpact
Launchpad projects and repositories
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Documentation team uses two projects for tracking documentation bugs
across OpenStack:
The Documentation team uses the following projects for tracking documentation
bugs across OpenStack:
* Launchpad bug area `openstack-manuals
<https://bugs.launchpad.net/openstack-manuals>`_ is the default one for
doc bugs and should be used for docs sourced from these repositories:
* `openstack-manuals <https://bugs.launchpad.net/openstack-manuals>`_ is the
default area for doc bugs in the openstack-manuals repository.
* openstackdocstheme
* openstack-doc-tools
* openstack-manuals
* security-doc
* `OpenStack Security Guide Documentation
<https://launchpad.net/ossp-security-documentation>`_ is used for the
security-doc repository.
* `openstack-api-site <https://bugs.launchpad.net/openstack-api-site>`_ is used
for the api-site API repository.
* `openstack-doc-tools <https://bugs.launchpad.net/openstack-doc-tools>`_ is
used for the doc-tools and openstackdocstheme repositories.
* Launchpad bug area `openstack-api-site
<https://bugs.launchpad.net/openstack-api-site>`_ is used for
the api-site API repository.
.. _doc_bugs_triaging:
@ -143,8 +144,8 @@ Depending on the area a bug affects, it has one or more tags. For example:
* **sec guide**, **install guide**, **ops-guide**, and other for specific
guides.
* **doc-builds** for documentation bugs that are in the documentation build
tool chain, such as the Sphinx theme, openstackdocstheme.
* **infra**, **theme** for documentation bugs that are in the documentation
build tool chain.
Bugs for third-party drivers
----------------------------

6
doc/contributor-guide/source/doc-tools/contributing.rst
View File

@ -40,6 +40,6 @@ File a bug against the tools
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you experience an issue while using the tools,
file a bug on Launchpad in the `openstack-manuals project
<https://bugs.launchpad.net/openstack-manuals>`_ and apply the ``doc-tools``
tag. Do not file issues on GitHub.
file a bug on Launchpad in the `openstack-doc-tools project
<https://bugs.launchpad.net/openstack-doc-tools>`_. Do not file issues on
GitHub.

2
doc/contributor-guide/source/docs-review.rst
View File

@ -21,7 +21,7 @@ the review process, see `Code Review
Repositories and core team
~~~~~~~~~~~~~~~~~~~~~~~~~~
The OpenStack Documentation team is core for api-site, openstack-manuals,
The OpenStack Documentation team is core for the api-site, openstack-manuals,
openstackdocstheme, and openstack-doc-tools projects.
For the following repositories that are part of the Documentation program,

2
doc/contributor-guide/source/team-structure.rst
View File

@ -48,7 +48,7 @@ The current list of docs cores for openstack-manuals, openstackdocstheme,
and openstack-doc-tools repositories can be found at
https://review.openstack.org/#/admin/groups/30,members.
The docs-specs, security-doc, training-guides, and training-labs
repositories have a separate core team respectively.
repositories have separate core teams.
The cross-project liaisons (CPLs) assist with subject matter questions,
reviews, doc bug triaging, and patching docs.