On Mon, Jul 1, 2013 at 11:05 PM, Anne Gentle <annegen...@justwriteclick.com>wrote:
> > > > On Sun, Jun 30, 2013 at 8:46 PM, Christopher Yeoh <cbky...@gmail.com>wrote: > >> On Sat, Jun 29, 2013 at 10:40 PM, Anne Gentle < >> annegen...@justwriteclick.com> wrote: >>> >>> I was thinking of making sure it gets in the weekly newsletter and >>> asking the user committee if they have ideas, plus Twitter. Another mailing >>> list post may not be a different enough channel. >>> >>> >> I've made a blog post, tweeted it and asked for it to be included in the >> weekly newsletter. >> >> >> http://chris.yeoh.info/2013/07/01/nova-api-extensions-not-to-be-ported-to-v3/ >> >> Just wondering if you knew what the right way to contact the user >> committee is? There didn't seem to be a contact email address on their web >> page. >> >> > Good thinking Chris. Here's the contact list for the user-committe: > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee. > > Thanks! > I am also realizing that what I really want is a full document describing > v3. What are the plans for that? (Sorry if that's really obvious and I'm > not seeing it.) > > We have a blueprint for H3 to do doco and I've been planning on sending you an email about that :-) https://blueprints.launchpad.net/nova/+spec/v3-api-specification https://blueprints.launchpad.net/openstack-manuals/+spec/multi-version-api-site The rough plan was to have a v3 version of test_api_samples and produce pretty much exactly what we do for the v2 API. But if there is a better way to do it that it makes it easier to produce API docs this is a good opportunity to change what is done for v3. If we do that will the doc team be able to handle the creation of the documentation? There's around 60-70 extensions so there will be quite a lot of stuff going in for throughout H3. Regards, Chris
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev