[openstack-dev] Subject: [all][api] POST /api-wg/news
Ed Leafe
ed at leafe.com
Thu Jan 19 17:25:43 UTC 2017
Greetings OpenStack community,
Today's meeting [0] was a relatively quiet one; I attribute it to cdent's absence. :)
Most of the meeting was concerned with reviews of existing issues, and those didn't generate much discussion. There was some discussion of cdent's response to the OpenStack Technical Committee's discussion on "Updating stability/compatibility guidelines". Chris created a patch "[WIP] Refactor and re-validate api change guidelines" at https://review.openstack.org/#/c/421846, and posted an email describing his take on the issue: http://lists.openstack.org/pipermail/openstack-dev/2017-January/110384.html. All are encouraged to comment on the review. In Chris's words: "I wanted to be sure that the guideline got a rewrite to express that goal zero is to make users happy and that trumps everything"
Lots of other guidelines in progress and awaiting your feedback if you have time to give it (see below).
# Newly Published Guidelines
* Accurate status code vs. Backwards compatibility
https://review.openstack.org/#/c/422264/
* fix no sample file in browser
https://review.openstack.org/#/c/421084/
# API Guidelines Proposed for Freeze
Guidelines that are ready for wider review by the whole community.
* Add guidelines on usage of state vs. status
https://review.openstack.org/#/c/411528/
* Clarify the status values in versions
https://review.openstack.org/#/c/411849/
* Add guideline for invalid query parameters
https://review.openstack.org/417441
# Guidelines Currently Under Review [3]
* Add guidelines for boolean names
https://review.openstack.org/#/c/411529/
* Define pagination guidelines
https://review.openstack.org/#/c/390973/
* Add API capabilities discovery guideline
https://review.openstack.org/#/c/386555/
# Highlighting your API impacting issues
If you seek further review and insight from the API WG, please address your concerns in an email to the OpenStack developer mailing list[1] with the tag "[api]" in the subject. In your email, you should include any relevant reviews, links, and comments to help guide the discussion of the specific challenge you are facing.
To learn more about the API WG mission and the work we do, see OpenStack API Working Group [2].
Thanks for reading and see you next week!
# References
[0] http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-01-19-16.00.log.html
[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[2] http://specs.openstack.org/openstack/api-wg/
[3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
More information about the OpenStack-dev
mailing list