Meetings/API-SIG
Contents
Weekly API Working Group Meeting
This is a weekly meeting to discuss the OpenStack API.
Our mission is to improve the developer experience of API users by converging the OpenStack API to a consistent and pragmatic RESTful design. The working group creates guidelines that all OpenStack projects should follow for new development, and promotes convergence of new APIs and future versions of existing APIs.
Meetings
- Meeting Time: Weekly, Thursday at 16:00UTC
- IRC channel:
#openstack-meeting-3
- MeetBot Manual http://meetbot.debian.net/Manual.html
- Chaired by: Any API WG Member
Next Meeting
Check the Calendar
Subscribe to the ICS Calendar Feed
Agenda
- #startmeeting api wg
- #chair cdent elmiko etoews
- #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
- #topic previous meeting action items
- #topic open mic
- summit update (cdent)
- error knowledge base proposal: https://docs.google.com/document/d/1fdRuPsIenaulxjXGgEK35UeWORiwOPpdX7OxL6E-ICw/edit (ediardo)
- should we put API porcelain in our domain?
- #topic guidelines
- #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
- null/special case in time intervals: https://review.openstack.org/#/c/383862/
- What's ready to freeze? Or what's not, what's missing?
- What's ready to merge?
- json warning maybe: https://review.openstack.org/#/c/364460/
- GET with request body vs. querystring vs. POST (edleafe)
- came up in https://review.openstack.org/#/c/300178/
- spec: https://review.openstack.org/#/c/385618/1/specs/ocata/approved/resource-providers-get-by-request.rst
- see cdent's comments in there about the challenge presented by projects deciding to not follow the right way to do things
- obso: http://stackoverflow.com/questions/978061/http-get-with-request-body
- #topic APIImpact
- #topic bug review
- #topic weekly newsletter
- #endmeeting