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 netstack team. 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. :)
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. The review system on that project is set for the doc-core team to review those manuals but any other votes are also welcomed. Thanks, Anne *Anne Gentle* 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> 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> 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> >> Date: Wed, Sep 14, 2011 at 9:45 AM >> Subject: [Openstack] Compute API and doc >> To: 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 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 >> Post to : openst...@lists.launchpad.net >> 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 >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > 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 : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
