When this template was created, the intention behind this section was to
know the got-to people for specific specs. Questions like: Who should I
ping if I need more Glance insights? Who should I ping to actually get
reviews? etc
Unfortunately, The reviewers section has turned to a field mostly used
to highlight people interested in a specific feature. More often than
not, the revieweres listed in this section are not the ones reviewing
the patches for the spec.
In addition to the above, this section currently separates core
reviewers from non-cores. This separation brings no value to this
section nor the spec itself.
Regardless the size of the team, this section is not bringing any value
to the process as reviewers not in this list can as well review the
patches as much as the reviewers listed there can also not review the
patches.
Change-Id: I973d97e82f4561de8d4ac33672494eae0fc15925
Goal is to maintain API specs in the specs repo for each project
and to eliminate the image-api repo.
Splits up original v2 API document into multiple files.
Change-Id: I7b6fbb1ee4a9a2e04395a7aa942d9ebdb011cc85
This patch adds "Reviewers" subsection under the "Implementation"
section in the template. Thus, all the specs following this commit
would need to suffice the Reviewers requirement for the approval.
Email [0] sent to the ML, corresponding to this requirement.
[0] http://lists.openstack.org/pipermail/openstack-dev/2014-October/048918.html
Change-Id: I396b7fad247a2e115bf9c7b7634240c15355ab20
These 3 folders didn't have an index file. This patch adds one so it can
contain a TOC for the accepted specs.
Change-Id: Ib674688ba51765d70b555fa51bcc5d35a9b6bcad
Flavio Percoco