<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 15, 2016 at 12:04 PM, Sean McGinnis <span dir="ltr"><<a href="mailto:sean.mcginnis@gmx.com" target="_blank">sean.mcginnis@gmx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class="">On Fri, Apr 15, 2016 at 11:17:40AM -0500, Anne Gentle wrote:<br>
> Sean and I are collaborating on a cross project spec to talk about at the Summit. Can you talk about concerns or cons to this approach so we can put it in the spec?<br>
><br>
> Thanks,<br>
> Anne<br>
<br>
</span>Thanks Anne. No concerns at the moment. I was just afraid I had missed<br>
something from the discussions.<br></blockquote><div><br></div><div>Okay, good. My sense is that this project ownership of API docs is a great direction.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Thanks for the clarification. I will watch for the cross project<br>
session.<br></blockquote><div><br></div><div>Here's the one you want. </div><div><br></div><div><a href="https://www.openstack.org/summit/austin-2016/summit-schedule/events/9479">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9479</a><br></div><div><br></div><div>Thanks -</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Thanks!<br>
<span class=""><font color="#888888">Sean<br>
</font></span><div class=""><div class="h5"><br>
><br>
><br>
> > On Apr 15, 2016, at 11:02 AM, Sean McGinnis <<a href="mailto:sean.mcginnis@gmx.com">sean.mcginnis@gmx.com</a>> wrote:<br>
> ><br>
> >> On Fri, Apr 15, 2016 at 09:38:20AM +0200, Andreas Jaeger wrote:<br>
> >>> On 04/15/2016 08:14 AM, Masahito MUROI wrote:<br>
> >>> Hi Doc team folks,<br>
> >>><br>
> >>> Congress team plans to add API reference into [1] instead of [2] to<br>
> >>> follow official documentation project. But I found the design session<br>
> >>> about a API docs style[3].<br>
> >>><br>
> >>> For now, is it ok to add API reference [1], or should we wait the<br>
> >>> decision about style of API reference repository?<br>
> >>><br>
> >>> 1. <a href="http://developer.openstack.org/api-ref.html" rel="noreferrer" target="_blank">http://developer.openstack.org/api-ref.html</a><br>
> >>> 2. <a href="http://docs.openstack.org/developer/congress/" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/congress/</a><br>
> >>> 3.<br>
> >>> <a href="https://www.openstack.org/summit/austin-2016/summit-schedule/events/9479?goback=1" rel="noreferrer" target="_blank">https://www.openstack.org/summit/austin-2016/summit-schedule/events/9479?goback=1</a><br>
> >><br>
> >><br>
> >> See the work that is done by Sean Dague and Anne Gentle for nova and<br>
> >> follow this setup:<br>
> >> <a href="http://lists.openstack.org/pipermail/openstack-dev/2016-April/092234.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2016-April/092234.html</a><br>
> ><br>
> > I thought I followed all of the emails on moving to Swagger then RST.<br>
> > Moving the api docs in tree with the projects is something I wasn't<br>
> > aware of.<br>
> ><br>
> > Was there a cross-project spec for this or something detailing the long<br>
> > term goal and direction each team should take for doing this? I see the<br>
> > work Nova has done (looks great) but is that something that team has<br>
> > decided to explore or is this something all of us should be involved in?<br>
> ><br>
> > Sorry, just caught a little off guard here and trying to figure out what<br>
> > I've missed.<br>
> ><br>
> > Sean<br>
> ><br>
> >><br>
> >> There have been a couple more emails in the last months on this topic<br>
> >><br>
> >> Also, there's a spec:<br>
> >> <a href="http://specs.openstack.org/openstack/docs-specs/specs/mitaka/app-guides-mitaka-vision.html" rel="noreferrer" target="_blank">http://specs.openstack.org/openstack/docs-specs/specs/mitaka/app-guides-mitaka-vision.html</a><br>
> >><br>
> >> so, you should do this in your own repository, set up proper jobs -<br>
> >> and then publish to <a href="http://developer.openstack.org" rel="noreferrer" target="_blank">developer.openstack.org</a><br>
> ><br>
> > That spec doesn't say anything about moving to each project's<br>
> > repository. Is there something else with more detail?<br>
> ><br>
> >><br>
> >> Andreas<br>
> >> --<br>
> >> Andreas Jaeger aj@{<a href="http://suse.com" rel="noreferrer" target="_blank">suse.com</a>,<a href="http://opensuse.org" rel="noreferrer" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
> >> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> >> GF: Felix Imendörffer, Jane Smithard, Graham Norton,<br>
> >> HRB 21284 (AG Nürnberg)<br>
> >> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
> >><br>
> >><br>
> >> __________________________________________________________________________<br>
> >> OpenStack Development Mailing List (not for usage questions)<br>
> >> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
> > __________________________________________________________________________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Anne Gentle</div><div><a href="http://www.justwriteclick.com" style="font-size:12.8px" target="_blank">www.justwriteclick.com</a><br></div></div></div></div></div>
</div></div>