<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 16, 2016 at 8:04 AM, Atsushi SAKAI <span dir="ltr"><<a href="mailto:sakaia@jp.fujitsu.com" target="_blank">sakaia@jp.fujitsu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Anne<br>
<br>
I move and clean up api-site issues as far as I can do.<br>
But it still remain 36 open bugs.<br>
mainly WADL, INCOMPLETE status, FIX COMMITED status,<br>
and too many project issue (like 1390528, 1390523 etc)<br>
Would you check it?<br>
<br></blockquote><div><br></div><div>Thanks! I'm going through a clean up round myself, some are openstack-doc-tools. Some I'd consider "Fix Released" so I'm commenting when I change the status. </div><div><br></div><div>Thank you so much for going through these. Great work -- and great numbers. Now the bugs in openstack-api-site are either for API Quick Start or the First App on OpenStack content.</div><div><br></div><div>Anne</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks<br>
Atsushi SAKAI<br>
<br>
On Wed, 11 May 2016 10:04:06 -0500<br>
<div class="HOEnZb"><div class="h5">Anne Gentle <<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>> wrote:<br>
<br>
> On Wed, May 11, 2016 at 8:12 AM, Atsushi SAKAI <<a href="mailto:sakaia@jp.fujitsu.com">sakaia@jp.fujitsu.com</a>><br>
> wrote:<br>
><br>
> > Anne<br>
> > Augustina<br>
> ><br>
> > Thank you for description and help.<br>
> ><br>
> > I will clean up launchpad api-site within this week at first.<br>
> > Since just around 150 issues and many issues are tagged it already.<br>
> > I can manually move most of the issues.<br>
> > Does any problem exist for this method?<br>
> ><br>
> ><br>
> Sounds good to me. I hadn't found a script, so a manual move is fine, and<br>
> if you're able then please go for it. :)<br>
><br>
><br>
> > Then I will do it for remaining api-ref migration issues.<br>
> ><br>
><br>
> Sounds good. For any tooling issues, use the<br>
> <a href="https://bugs.launchpad.net/openstack-doc-tools" rel="noreferrer" target="_blank">https://bugs.launchpad.net/openstack-doc-tools</a> tracker.<br>
><br>
> Thanks!<br>
> Anne<br>
><br>
><br>
> ><br>
> > Thanks<br>
> > Atsushi SAKAI<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Tue, 10 May 2016 07:53:19 -0500<br>
> > Anne Gentle <<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>> wrote:<br>
> ><br>
> > > Great questions, so I'm copying the -docs and -dev lists to make sure<br>
> > > people know the answers.<br>
> > ><br>
> > > On Tue, May 10, 2016 at 5:14 AM, Atsushi SAKAI <<a href="mailto:sakaia@jp.fujitsu.com">sakaia@jp.fujitsu.com</a>><br>
> > > wrote:<br>
> > ><br>
> > > > Hello Anne<br>
> > > ><br>
> > > > I have several question when I am reading through etherpad's (in<br>
> > > > progress).<br>
> > > > It would be appreciated to answer these questions.<br>
> > > ><br>
> > > > 1)Should api-ref launchpad **bugs** be moved to each modules<br>
> > > > (like keystone, nova etc)?<br>
> > > > Also, this should be applied to moved one's only or all components?<br>
> > > > (compute, baremetal Ref.2)<br>
> > > ><br>
> > > > Ref.<br>
> > > > <a href="https://etherpad.openstack.org/p/austin-docs-newtonplan" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/austin-docs-newtonplan</a><br>
> > > > API site bug list cleanup: move specific service API ref bugs to<br>
> > > > project's Launchpad<br>
> > > ><br>
> > > > Ref.2<br>
> > > > <a href="http://developer.openstack.org/api-ref/compute/" rel="noreferrer" target="_blank">http://developer.openstack.org/api-ref/compute/</a><br>
> > > > <a href="http://developer.openstack.org/api-ref/baremetal/" rel="noreferrer" target="_blank">http://developer.openstack.org/api-ref/baremetal/</a><br>
> > ><br>
> > ><br>
> > > Yes! I definitely got agreement from nova team that they want them. Does<br>
> > > anyone have a Launchpad script that could help with the bulk<br>
> > filter/export?<br>
> > > Also, are any teams concerned about taking on their API reference bugs?<br>
> > > Let's chat.<br>
> > ><br>
> > ><br>
> > > ><br>
> > > ><br>
> > > > 2)Status of API-Ref<br>
> > > > a)Why keystone and senlin are no person at this moment?<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > Keystone -- after the Summit, keystone had someone sign up [1], but<br>
> > sounds<br>
> > > like we need someone else. Brant, can you help us find someone?<br>
> > ><br>
> > > Senlin -- Qiming Teng had asked a lot of questions earlier in the process<br>
> > > and tested the instructions. Qiming had good concerns about personal<br>
> > > bandwidth limits following along with all the changes. Now that it's<br>
> > > settled, I'll follow up (and hoping the senlin team is reading the list).<br>
> > ><br>
> > ><br>
> > > > b)What is your plan for sahara and ceilometer?<br>
> > > > (It seems already exist the document.)<br>
> > > ><br>
> > ><br>
> > > Yes, these are two I had seen already have RST, but they do not use the<br>
> > > helpful Sphinx extensions.<br>
> > ><br>
> > > Sahara -- Mike McCune, we should chat about the plans. Are you okay with<br>
> > > moving towards the common framework and editing the current RST files to<br>
> > > use the rest_method and rest_parameters Sphinx directives?<br>
> > ><br>
> > > Ceilometer -- sorry, Julien, I hadn't reached out individually to you.<br>
> > > Could you let me know your plans for the RST API reference docs?<br>
> > ><br>
> > ><br>
> > > > c)When is the table's status changed to "Done"?<br>
> > > > nova (compute) and ironic (baremetal) seems first patch merged<br>
> > > > and see the document already.<br>
> > > ><br>
> > ><br>
> > > I'll change those two to Done.<br>
> > ><br>
> > > Thanks for asking -<br>
> > > Anne<br>
> > ><br>
> > ><br>
> > > ><br>
> > > ><br>
> > > > Ref.<br>
> > > > [1]<br>
> > > ><br>
> > <a href="https://wiki.openstack.org/wiki/Documentation/Migrate#API_Reference_Plan" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Documentation/Migrate#API_Reference_Plan</a><br>
> > > ><br>
> > > ><br>
> > > > Thanks<br>
> > > ><br>
> > > > Atsushi SAKAI<br>
> > > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > > Anne Gentle<br>
> > > <a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">www.justwriteclick.com</a><br>
> ><br>
> ><br>
> > --<br>
> > Atsushi SAKAI <<a href="mailto:sakaia@jp.fujitsu.com">sakaia@jp.fujitsu.com</a>><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Anne Gentle<br>
> <a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">www.justwriteclick.com</a><br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Atsushi SAKAI <<a href="mailto:sakaia@jp.fujitsu.com">sakaia@jp.fujitsu.com</a>><br>
</font></span></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>