openstack team mailing list archive

[Anne Gentle <anne@xxxxxxxxxxxxx>]

Couple of reasons from my perspective:

We've got to get me out of the loop for reviews of the API spec - I'm happy
to review and would like to be a reviewer of all the API docs for OpenStack,
but we need better governance of API updates.

Also, my goal was to move doc source to github prior to October 3. Based on
this discussion, it also makes a decision about how many "books" per repo we
have. I'm now leaning towards one repo per "book" deliverable.

Anne
*Anne Gentle*
anne@xxxxxxxxxxxxx
 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 Tue, Aug 23, 2011 at 3:01 AM, Thierry Carrez <thierry@xxxxxxxxxxxxx>wrote:

> Vishvananda Ishaya wrote:
> > Ultimately I would like the spec to be generated from the code, but as a
> > first pass, we should at least be able to edit the future version of the
> > spec as we make changes.  I've proposed the current version of the spec
> > here:
> >
> > https://code.launchpad.net/~vishvananda/nova/add-api-docs/+merge/72506<https://code.launchpad.net/%7Evishvananda/nova/add-api-docs/+merge/72506>
> >
> > Are there any issues with this approach?
>
> Looks like there are diverging opinions. That sounds like work for... a
> design summit brainstorm session !
>
> Any reason why we'd need to discuss this *now*, as opposed to after
> Diablo is released ?
>
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>