Hi, I'm completely happy to align Quantum with the other Openstack projects, and move the API documentation in a separate repo. I'm totally fine with granting +2 rights to doc-core team, and I believe that their reviews will be of great help to improve the quality of the documentation.
Salvatore ________________________________________ From: netstack-bounces+salvatore.orlando=eu.citrix....@lists.launchpad.net [netstack-bounces+salvatore.orlando=eu.citrix....@lists.launchpad.net] On Behalf Of Dan Wendlandt [d...@nicira.com] Sent: Wednesday, September 28, 2011 8:07 PM To: Anne Gentle Cc: netstack@lists.launchpad.net Subject: Re: [Netstack] [Openstack] Compute API and doc On Wed, Sep 28, 2011 at 11:54 AM, Anne Gentle <a...@openstack.org<mailto:a...@openstack.org>> wrote: Hi Netstackers - Yes, Dan has outlined the basic benefits to the separate repo. In the case of the network-api repository (is that the right name?), the OpenStack doc-core team does have the ability to vote +2 in addition to the core netstac That doc-core team is me, David Cramer, and Kevin Bringard. We all understand the voting and review process and won't push something through without the right votes, though. :) Ok, yeah, I think that is the main concern. I'll leave it up to Salvatore as to whether he prefer the API docs to be with the code or in a separate repo. For the admin manual, which I'm very pleased about, we can house it in the openstack-manuals project with the other admin manuals and publish to docs.openstack.org/incubation<http://docs.openstack.org/incubation>. The review system on that project is set for the doc-core team to review those manuals but any other votes are also welcomed. Yes, that makes sense. I will send you the docbook file for the admin guide and we can get that started asap. Thanks! Dan Thanks, Anne Anne Gentle a...@openstack.org<mailto:a...@openstack.org> my blog<http://justwriteclick.com/> | my book<http://xmlpress.net/publications/conversation-community/> | LinkedIn<http://www.linkedin.com/in/annegentle> | Delicious<http://del.icio.us/annegentle> | Twitter<http://twitter.com/annegentle> On Wed, Sep 28, 2011 at 1:46 PM, Dan Wendlandt <d...@nicira.com<mailto:d...@nicira.com>> wrote: Hi folks, Anne's suggestion is to have Quantum follow the other OpenStack projects and have our API docs in a separate repo. This has the benefit of keeping the large docbook diffs out of the main repo, but has the downside that it may be harder to enforce that code & API docs are in sync. Unless someone has concerns here, we'll follow the standard path. Anne, I assume that the same core team is responsible for approving changes to the API docs? Dan On Wed, Sep 14, 2011 at 10:20 AM, Dan Wendlandt <d...@nicira.com<mailto:d...@nicira.com>> wrote: All major openstack projects seem to be heading in the direction of keeping their API documentation in a separate repo. Salvatore, what are your thoughts on taking this approach with Quantum? Any one else see pluses or minus, other than the obvious benefit of mapping to what other OpenStack projects are doing? My assumption is that the api repo is managed by the core team, just like the main code repo. Dan ---------- Forwarded message ---------- From: Anne Gentle <a...@openstack.org<mailto:a...@openstack.org>> Date: Wed, Sep 14, 2011 at 9:45 AM Subject: [Openstack] Compute API and doc To: openst...@lists.launchpad.net<mailto:openst...@lists.launchpad.net> Hi all - The move to Github for the Compute API is now complete and the 1.1 API spec, the 1.0 API doc, and the API Extension proposal now live in this repository: https://github.com/openstack/compute-api There's also a new Jenkins job that builds the documents to docs.openstack.org/trunk<http://docs.openstack.org/trunk> out of this repo. Next I'll move the rest of the books out of the Launchpad openstack-manuals repository, though you can continue to log doc bugs in Launchpad at http://bugs.launchpad.net/openstack-manuals. Thanks for hanging in there through the transition. Anne _______________________________________________ Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack> Post to : openst...@lists.launchpad.net<mailto:openst...@lists.launchpad.net> Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack> More help : https://help.launchpad.net/ListHelp -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks, Inc. www.nicira.com<http://www.nicira.com> | www.openvswitch.org<http://www.openvswitch.org> Sr. Product Manager cell: 650-906-2650<tel:650-906-2650> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks, Inc. www.nicira.com<http://www.nicira.com> | www.openvswitch.org<http://www.openvswitch.org> Sr. Product Manager cell: 650-906-2650<tel:650-906-2650> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks, Inc. www.nicira.com<http://www.nicira.com> | www.openvswitch.org<http://www.openvswitch.org> Sr. Product Manager cell: 650-906-2650 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
