Open Stack

Folks-

The response to this has been mostly, "meh, if you like." Since I'm now
the guy who gets to track the paperwork, I would like to give it a try
for a cycle. If it doesn't work, or imposes too much process, or if
people otherwise hate it, we can trash it, no harm no foul.

To that end, I have proposed a patch [1] with some tooling and
documentation. If you do nothing else, please read the (updated) section
on "Backlog specifications" [2] and the (new) section on "Abandoning a
specification" [3].

I have also eaten my own dogfood and proposed patches to abandon the
four existing backlog specs [4]. I added those specs' original authors
and assignees as reviewers (fwiw; some are surely inactive at this point).

One of those had a Train spec that sounds eerily similar [5] so I
suggested "move-spec" there.

There's also a Train spec the author told me was intended for "future"
[6] so I suggested that be moved to the backlog directory.

I ask for help from nova-core to review and merge the tooling (including
Mel's blueprint counting utility [7] which has been ready for a while)
and the scrub patches.

Moving forward, hopefully we can make it a recurring agenda item at PTGs
to review backlog specs and promote, defer, or abandon them as appropriate.

Thanks,
efried

[1] https://review.openstack.org/#/c/648800/
[2]
http://logs.openstack.org/00/648800/3/check/openstack-tox-docs/e601952/html/readme.html#backlog-specifications
[3]
http://logs.openstack.org/00/648800/3/check/openstack-tox-docs/e601952/html/readme.html#abandoning-a-specification
[4]
https://review.openstack.org/#/q/topic:scrub-backlog-specs+(status:open+OR+status:merged)
[5] https://review.openstack.org/#/c/635408/
[6] https://review.openstack.org/#/c/648665/
[7] https://review.openstack.org/#/c/581914/