openstack
/
oslo-specs
Code Issues Proposed changes

Expand instructions in "alternatives" section 

Ask a couple of specific questions about how a new feature relates to
existing Oslo or third-party libraries.

Change-Id: Id86be3f45a6163a8d980661e0484ff9cbc33c36a
This commit is contained in:
Doug Hellmann 2014-10-14 16:10:52 -04:00
parent 50bb32b95c
commit 036c4c7f5d
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
specs/template.rst
View File

@ -64,6 +64,12 @@ What other ways could we do this thing? Why aren't we using those? This doesn't
have to be a full literature review, but it should demonstrate that thought has have to be a full literature review, but it should demonstrate that thought has
been put into why the proposed solution is an appropriate one. been put into why the proposed solution is an appropriate one.
If this is a new module or library, what other similar libraries were
considered why were they rejected as unsuitable?
If this is a new feature, why does it belong in an Oslo module or
library instead of an existing third-party library?
Impact on Existing APIs Impact on Existing APIs
----------------------- -----------------------