<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 20/03/18 08:26, Michael McCune
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADE+ktQJK2i4Z76optSOg98R9d5z=59i8hVt+mHoBqTSxBtBtA@mail.gmail.com">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Mar 16, 2018 at 4:55 AM,
Chris Dent <span dir="ltr"><<a
href="mailto:cdent+os@anticdent.org" target="_blank"
moz-do-not-send="true">cdent+os@anticdent.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><snip><br>
<div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
So summarize and clarify, we are talking about SDK
being able to build their interface to Openstack APIs
in an automated way but statically from API Schema
generated by every project. Such API Schema is already
built in memory during API reference documentation
generation and could be saved in JSON format (for
instance) (see [5]).<br>
</blockquote>
<br>
What do you see as the current roadblocks preventing
this work from<br>
continuing to make progress?
<div class="HOEnZb">
<div class="h5"><br>
<br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Gilles, i'm very curious about how we can help as well.<br>
<br>
</div>
<div>i am keenly interested in the api-schema work that is
happening and i am coming up to speed with the work that
Graham has done, and which previously existed, on
os-api-ref. although i don't have a *ton* of spare free
time, i would like to help as much as i can.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Hi Michael, <br>
<br>
Thank you very much for jumping in. Your interest shows the demand
for such feature, which is what we need the most at the moment. The
more people the better the momentum and likelihood of getting more
help. Let's blow the horn!<br>
<br>
As you probably already know, the real work is Graham's PR [1] where
the magic is going to happen and where you can help.<br>
Graham who has been involved and working with the Sphinx library
offered to 'dump' the API schema which is already in memory, what I
call the de-facto API Schema, which is needed to generate the API
Reference guides. So instead of asking developers of each project to
change their habits and write an API schema up front, it seemed
easier to just use the current work flow in place with the
documentation (API Ref) and generate the API schema which can be
stored in every project Git.<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/528801">https://review.openstack.org/#/c/528801</a><br>
<br>
Cheers,<br>
Gilles<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CADE+ktQJK2i4Z76optSOg98R9d5z=59i8hVt+mHoBqTSxBtBtA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>thanks for bringing this up again,<br>
<br>
</div>
<div>peace o/ <br>
</div>
</div>
<br>
</div>
</div>
<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>
</body>
</html>