openstack
/
nova-specs
Code Issues Proposed changes

Clarify the purpose of the spec backlog 

Change-Id: I46e9e07bf89852540c5394e82c92f709a397e596
This commit is contained in:
Dan Smith 2015-07-23 13:27:58 -07:00
parent 41bf5302e7
commit 525af38a5c
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/specs/backlog/index.rst
View File

@ -2,16 +2,18 @@
Nova Backlog Specifications Nova Backlog Specifications
=========================== ===========================
If you have a problem that needs solving, but you are not currently planning The Nova spec backlog is a place for the team to record decisions
on implementing it, this is the place we can store your ideas. about technical problems and proposed solutions. A backlog spec should
contain at least a clear problem description, as well as a general
description of the proposed or desired solution. This serves as a
marker to record the team's acceptance of a problem as in-scope for
the project, as well as a reasonable direction for solving the problem.
These specifications have the problem description completed, but all other A spec that exists here is something that either needs a driver or
sections are optional. implementor, or something that can't be done currently. If you would
like to implement one of these specifications, fill out the missing
If you are looking for a blueprint to work on, here is a list of specifications sections and follow the standard process of submitting it to a release
that are looking for owners. If you would like to implement one of these (See :doc:`../../readme`).
specifications, fill out the missing sections and follow the standard process
of submitting it to a release (See :doc:`../../readme`).
Template: Template: