Group capabilities consistently

Bug #1579162 reported by Mark T. Voelker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
defcore
Low
Chris Hoge

Bug Description

There's been an ongoing discussion about how to group related capabilties in the Guideline files. For example, in some cases we group CRUD capabilities together [1][2][3][4] and in other cases we list them separately [4][5][6][7]. It would be nice to be more consistent about this, but there are pro's and cons of doing it one way or the other. For example, some tests today are written such that they test CRUD capabilities together (because in order to delete a thing, you must first have created it, and you probably verified that it was created by reading it). However it can also be unclear what CRUD operations encompass without breaking them into separate capabilities (for example: does the "R" in CRUD include getting a list of things, getting information about one particular thing, or both?).

We should pick a direction on this and work to make our Guidelines as consistent as possible.

[1] http://git.openstack.org/cgit/openstack/defcore/tree/next.json#n61
[2] http://git.openstack.org/cgit/openstack/defcore/tree/next.json#n62
[3] http://git.openstack.org/cgit/openstack/defcore/tree/next.json#n79
[4] http://git.openstack.org/cgit/openstack/defcore/tree/next.json#n104
[5] http://git.openstack.org/cgit/openstack/defcore/tree/next.json#n106
[6] http://git.openstack.org/cgit/openstack/defcore/tree/next.json#n107
[7] http://git.openstack.org/cgit/openstack/defcore/tree/next.json#n105

Changed in defcore:
status: New → Triaged
Chris Hoge (hoge)
Changed in defcore:
assignee: nobody → Chris Hoge (hoge)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers