<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Chris,</p>
<p>Thank you for those precious details.</p>
<p>I just added <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/524467/">https://review.openstack.org/#/c/524467/</a> to augment
the existing guidelines [2] and to get started with the API Schema
(consumption) topic.<br>
<br>
It would be great if that topic could be added to the agenda, can
you please help?</p>
<p>Cheers,<br>
Gilles<br>
</p>
<br>
<div class="moz-cite-prefix">On 01/12/17 04:17, Chris Dent wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.1711301716300.79071@cdent-m01.vmware.com">
<br>
Greetings OpenStack community,
<br>
<br>
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.
<br>
<br>
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!
<br>
<br>
This week's excellent discussion [5] 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 useful.
<br>
<br>
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:
<br>
<br>
* The list of bugs [6] indicates several missing or incomplete
guidelines.
<br>
* The existing guidelines [2] always need refreshing to account
for changes over time. If you find something that's not quite
right, submit a patch [7] to fix it.
<br>
* 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 [7].
<br>
<br>
# Newly Published Guidelines
<br>
<br>
None this week.
<br>
<br>
# API Guidelines Proposed for Freeze
<br>
<br>
Guidelines that are ready for wider review by the whole community.
<br>
<br>
None this week
<br>
<br>
# Guidelines Currently Under Review [3]
<br>
<br>
* A (shrinking) suite of several documents about doing version and
service discovery
<br>
Start at <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/459405/">https://review.openstack.org/#/c/459405/</a>
<br>
<br>
* WIP: microversion architecture archival doc (very early; not yet
ready for review)
<br>
<a class="moz-txt-link-freetext" href="https://review.openstack.org/444892">https://review.openstack.org/444892</a>
<br>
<br>
# Highlighting your API impacting issues
<br>
<br>
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[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.
<br>
<br>
To learn more about the API SIG mission and the work we do, see
our wiki page [4] and guidelines [2].
<br>
<br>
Thanks for reading and see you next week!
<br>
<br>
# References
<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br>
[2] <a class="moz-txt-link-freetext" href="http://specs.openstack.org/openstack/api-wg/">http://specs.openstack.org/openstack/api-wg/</a>
<br>
[3]
<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z">https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z</a><br>
[4] <a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/API_SIG">https://wiki.openstack.org/wiki/API_SIG</a>
<br>
[5]
<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-11-30-16.01.log.html#l-71">http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-11-30-16.01.log.html#l-71</a><br>
[6] <a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/openstack-api-wg">https://bugs.launchpad.net/openstack-api-wg</a>
<br>
[7] <a class="moz-txt-link-freetext" href="https://git.openstack.org/cgit/openstack/api-wg">https://git.openstack.org/cgit/openstack/api-wg</a>
<br>
<br>
Meeting Agenda
<br>
<a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda">https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda</a>
<br>
Past Meeting Records
<br>
<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/meetings/api_sig/">http://eavesdrop.openstack.org/meetings/api_sig/</a>
<br>
Open Bugs
<br>
<a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/openstack-api-wg">https://bugs.launchpad.net/openstack-api-wg</a>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Gilles Dubreuil
Senior Software Engineer, Openstack DFG Integration
Mobile: +61 400 894 219
Email: <a class="moz-txt-link-abbreviated" href="mailto:gilles@redhat.com">gilles@redhat.com</a>
GitHub/IRC: gildub
</pre>
</body>
</html>