[openstack-dev] [all][api] POST /api-sig/news
gdubreui at redhat.com
Fri Dec 1 04:51:41 UTC 2017
Thank you for those precious details.
I just added https://review.openstack.org/#/c/524467/ to augment the
existing guidelines  and to get started with the API Schema
It would be great if that topic could be added to the agenda, can you
On 01/12/17 04:17, Chris Dent wrote:
> Greetings OpenStack community,
> With this week, the API-SIG had its first real meeting since before
> the summit in Sydney. Travel and US holidays have meant not enough
> people were around to make a meeting worth having.
> This week there were. First order of business was to officially make
> Dmitry Tantsur "core". In the context of the API-SIG that means he has
> the power to freeze and merge guidelines, run the meetings, and write
> this newsletter. For many months he's been providing excellent reviews
> on the guidelines that the SIG produces, and excellent and regular
> input in the discussions we have during the meetings. Welcome Dmitry!
> This week's excellent discussion  was centered around effective
> ways of dealing with versions in client code. One of the things that
> was remarkable about the conversation is that many things that a few
> years ago were often subject to debate are now fairly commonly
> accepted as good behavior: service discovery, version discovery,
> microversions, microversioning per-request (rather than per-session).
> As the SIG expands into working with SDK developers, being able to
> talk about and demonstrate these behaviors as "normal" will be very
> There has not, of late, been much progress on new (or improved)
> guidelines, but there are plenty of opportunities. Those of us who are
> regulars are full of good intentions but in recent months have had too
> many other obligations. If you are interested in helping out there are
> three entry points:
> * The list of bugs  indicates several missing or incomplete
> * The existing guidelines  always need refreshing to account for
> changes over time. If you find something that's not quite right,
> submit a patch  to fix it.
> * Have you done something for which you think guidance would have made
> things easier but couldn't find any? Submit a patch and help others .
> # Newly Published Guidelines
> None this week.
> # API Guidelines Proposed for Freeze
> Guidelines that are ready for wider review by the whole community.
> None this week
> # Guidelines Currently Under Review 
> * A (shrinking) suite of several documents about doing version and
> service discovery
> Start at https://review.openstack.org/#/c/459405/
> * WIP: microversion architecture archival doc (very early; not yet
> ready for review)
> # Highlighting your API impacting issues
> If you seek further review and insight from the API SIG about APIs
> that you are developing or changing, please address your concerns in
> an email to the OpenStack developer mailing list 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 SIG mission and the work we do, see our
> wiki page  and guidelines .
> Thanks for reading and see you next week!
> # References
>  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>  http://specs.openstack.org/openstack/api-wg/
>  https://wiki.openstack.org/wiki/API_SIG
>  https://bugs.launchpad.net/openstack-api-wg
>  https://git.openstack.org/cgit/openstack/api-wg
> Meeting Agenda
> Past Meeting Records
> Open Bugs
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Senior Software Engineer, Openstack DFG Integration
Mobile: +61 400 894 219
Email: gilles at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev