Anne
Augustina
Note.
Sorry for duplicate posting for openstack-docs.
Since I failed to post to openstack-dev.
Thank you for description and help.
I will clean up launchpad api-site within this week at first.
Since just around 150 issues and many issues are tagged it already.
I can manually move most of the issues.
Does any problem exist for this method?
Then I will do it for remaining api-ref migration issues.
Thanks
Atsushi SAKAI
On Tue, 10 May 2016 07:53:19 -0500
Anne Gentle <annegen...@justwriteclick.com> wrote:
> Great questions, so I'm copying the -docs and -dev lists to make sure
> people know the answers.
>
> On Tue, May 10, 2016 at 5:14 AM, Atsushi SAKAI <sak...@jp.fujitsu.com>
> wrote:
>
> > Hello Anne
> >
> > I have several question when I am reading through etherpad's (in
> > progress).
> > It would be appreciated to answer these questions.
> >
> > 1)Should api-ref launchpad **bugs** be moved to each modules
> > (like keystone, nova etc)?
> > Also, this should be applied to moved one's only or all components?
> > (compute, baremetal Ref.2)
> >
> > Ref.
> > https://etherpad.openstack.org/p/austin-docs-newtonplan
> > API site bug list cleanup: move specific service API ref bugs to
> > project's Launchpad
> >
> > Ref.2
> > http://developer.openstack.org/api-ref/compute/
> > http://developer.openstack.org/api-ref/baremetal/
>
>
> Yes! I definitely got agreement from nova team that they want them. Does
> anyone have a Launchpad script that could help with the bulk filter/export?
> Also, are any teams concerned about taking on their API reference bugs?
> Let's chat.
>
>
> >
> >
> > 2)Status of API-Ref
> > a)Why keystone and senlin are no person at this moment?
> >
> >
> >
> Keystone -- after the Summit, keystone had someone sign up [1], but sounds
> like we need someone else. Brant, can you help us find someone?
>
> Senlin -- Qiming Teng had asked a lot of questions earlier in the process
> and tested the instructions. Qiming had good concerns about personal
> bandwidth limits following along with all the changes. Now that it's
> settled, I'll follow up (and hoping the senlin team is reading the list).
>
>
> > b)What is your plan for sahara and ceilometer?
> > (It seems already exist the document.)
> >
>
> Yes, these are two I had seen already have RST, but they do not use the
> helpful Sphinx extensions.
>
> Sahara -- Mike McCune, we should chat about the plans. Are you okay with
> moving towards the common framework and editing the current RST files to
> use the rest_method and rest_parameters Sphinx directives?
>
> Ceilometer -- sorry, Julien, I hadn't reached out individually to you.
> Could you let me know your plans for the RST API reference docs?
>
>
> > c)When is the table's status changed to "Done"?
> > nova (compute) and ironic (baremetal) seems first patch merged
> > and see the document already.
> >
>
> I'll change those two to Done.
>
> Thanks for asking -
> Anne
>
>
> >
> >
> > Ref.
> > [1]
> > https://wiki.openstack.org/wiki/Documentation/Migrate#API_Reference_Plan
> >
> >
> > Thanks
> >
> > Atsushi SAKAI
> >
>
>
>
> --
> Anne Gentle
> www.justwriteclick.com
--
Atsushi SAKAI <sak...@jp.fujitsu.com>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
