openstack-helm/doc/source/specs/COPYME
Jean-Philippe Evrard 630ca71e3c Cleanup specs folder
Specs are not ordered currently, and every rst file inside the
specs folder is included in the TOC tree, but manually.

This is a problem as:
- the current readability of the specs was reduced due to inclusion
  of non-specs files
- the process of writing a spec was more tedious, due to the
  update of the specs/index.rst.

This fixes it by removing the extra files included by mistake in
the middle of the specs (the template for spec writing, and
the specs purpose/process), and automatically load all the
remaining files using a glob.

The content of the files removed is not lost: The template was
simply renamed COPYME to clearly state a spec writer should
copy the file (and will understand it needs to be named .rst)
with the other files present. The specs process/purpose is
now part of the main page of specs, which therefore doesn't need
extra including.

Change-Id: I8aa15c8a8f2d8b3ffb764c3fb2411eb27477d0b6
2019-03-04 15:13:28 +01:00

72 lines
1.2 KiB
Plaintext

..
This work is licensed under a Creative Commons Attribution 3.0 Unported
License.
http://creativecommons.org/licenses/by/3.0/legalcode
..
===============
Blueprint Title
===============
Include the URL of your Storyboard RFE:
https://storyboard.openstack.org/#!/story/1234567
Problem Description
===================
A detailed description of the problem.
Use cases
---------
1. TODO
Proposed Change
===============
How do you propose to solve this problem, and what's the scope?
Security Impact
---------------
How does this feature impact the securtiy of OpenStack-Helm?
Performance Impact
------------------
Does this feature impact the performance of OpenStack-Helm?
Alternatives
------------
Why is the proposed approach the best approach?
Implementation
==============
Assignee(s)
-----------
Who is leading the implementation?
Designate the primary author and contact.
Primary assignee:
<Gerrit Id or None>
Work Items
----------
Work items or tasks. These can be worked on by multiple contributors.
Testing
=======
What tests will verify this change is functional?
Documentation Impact
====================
What documentation needs must be considered with this change?
References
==========
Place any external references here.