From f87eb20dada7384813bf92064a06a2aea8685365 Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Thu, 7 Jan 2016 15:57:39 +0100 Subject: [PATCH] Document bug handling of vendor drivers Document how to handle bug reports for vendor drivers. Change-Id: I2f62d97d28a31e220b9ca27653e483067a431630 --- doc/contributor-guide/source/doc-bugs.rst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/doc/contributor-guide/source/doc-bugs.rst b/doc/contributor-guide/source/doc-bugs.rst index 84b16ebfea..6eb39cc4fc 100644 --- a/doc/contributor-guide/source/doc-bugs.rst +++ b/doc/contributor-guide/source/doc-bugs.rst @@ -125,6 +125,25 @@ Depending on the area a bug affects, it has one or more tags. For example: * **doc-builds** for documentation bugs that are in the documentation build tool chain, such as the Sphinx theme, openstackdocstheme. +Bugs for third-party drivers +---------------------------- + +Bugs to update tables for the configuration references use the tag +**autogenerate-config-docs**. + +For updates of specific sections or adding of new drivers, follow the +specification `Proprietary driver docs in openstack-manuals +`_ +and assign the bug to the contact person that is mentioned on the +`Vendor driver page +`_. If +this is a new driver with no documentation yet, assign the bug to the +committer of the change that triggered the bug report, mark it as +**Wishlist** and ask the committer to read and follow the +specification and handle it since the documentation team will not +document third-party drivers. + + Doc bug categories ------------------