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 <[email protected]> Date: Wed, Sep 14, 2011 at 9:45 AM Subject: [Openstack] Compute API and doc To: [email protected] 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 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 *Anne Gentle* [email protected] 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> _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks, Inc. www.nicira.com | www.openvswitch.org Sr. Product Manager cell: 650-906-2650 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~netstack Post to : [email protected] Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
