openstack
/
keystone-specs
Code Issues Proposed changes

Merge "Clarify backlog instructions and add ideas dir"

This commit is contained in:
Zuul 2017-10-20 17:58:51 +00:00 committed by Gerrit Code Review
parent 0aa11d2c64 b96e763c0a
commit 5080b79c5d
3 changed files with 30 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/index.rst
View File

@ -39,6 +39,14 @@ Ongoing:
specs/keystone/ongoing/*
Ideas:
.. toctree::
:glob:
:maxdepth: 1
specs/keystone/ideas/*
keystoneauth
============

21
specs/keystone/backlog/README.rst
View File

@ -2,15 +2,18 @@
Backlog Instructions
====================
This directory is for specifications that have been approved but not yet
implemented. If you are interested in implementing one of these specifications
submit a review request moving it to the appropriate release.
implemented. Specifications should only be accepted to backlog if they are
fully detailed and ready to be implemented. The only thing preventing a
backlogged specification from being targetted to a release is the absence of an
owner.
Picking up backlogged work
==========================
The updated review should reflect the new primary assignee. Please maintain
all previous assignees in the list of Other Contributors.
If a specification has been partially implemented, the document in the backlog
will contain information of what has been completed.
If you are interested in implementing a backlogged specification, submit a
review request moving it to the appropriate release. The updated review should
reflect the new primary assignee. Please maintain all previous assignees in the
list of Other Contributors. If a specification has been partially implemented,
the document in the backlog will contain information of what has been
completed.

10
specs/keystone/ideas/README.rst Normal file
View File

@ -0,0 +1,10 @@
========
Idea Log
========
This directory should be used to document interesting ideas that still need
some thought. Ideas proposed here do not require all semantics to be completely
thoughtout, like specifications do. Ideas accepted here are not guaranteed to a
release. Ideas that are generally accepted should progress to full
specifications and be targeted to a release. Ideas that are no longer
relevant, or end up losing steam, should be pruned from the directory.