<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 1, 2013 at 9:19 AM, Christopher Yeoh <span dir="ltr"><<a href="mailto:cbkyeoh@gmail.com" target="_blank">cbkyeoh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div class="im">On Mon, Jul 1, 2013 at 11:05 PM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div>On Sun, Jun 30, 2013 at 8:46 PM, Christopher Yeoh <span dir="ltr"><<a href="mailto:cbkyeoh@gmail.com" target="_blank">cbkyeoh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div>On Sat, Jun 29, 2013 at 10:40 PM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="auto"><div>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. </div><br>
</div></blockquote><div><br></div></div><div>I've made a blog post, tweeted it and asked for it to be included in the weekly newsletter.<br><br><a href="http://chris.yeoh.info/2013/07/01/nova-api-extensions-not-to-be-ported-to-v3/" target="_blank">http://chris.yeoh.info/2013/07/01/nova-api-extensions-not-to-be-ported-to-v3/</a><br>
<br></div><div>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.<br><br></div></div></div></div></blockquote><div><br></div>
</div></div><div>Good thinking Chris. Here's the contact list for the user-committe: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a>. </div>
<div><br></div></div></div></div></blockquote><div><br></div></div><div>Thanks!<br></div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra"><div class="gmail_quote"><div></div><div>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.)</div>
<div><br></div></div></div></div></blockquote><div><br></div></div><div>We have a blueprint for H3 to do doco and I've been planning on sending you an email about that :-)<br><br><a href="https://blueprints.launchpad.net/nova/+spec/v3-api-specification" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-api-specification</a><br>
<a href="https://blueprints.launchpad.net/openstack-manuals/+spec/multi-version-api-site" target="_blank">https://blueprints.launchpad.net/openstack-manuals/+spec/multi-version-api-site</a><br></div><div> <br></div><div>
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 <br>
</div><div> what is done for v3. <br><br></div><div>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.<br>
</div><div><br></div></div></div></div></blockquote><div><br></div><div style>I'd like to talk through it in a meeting, can someone come to next week's doc team meeting? <a href="https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting">https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting</a>. I've added it to the agenda. </div>
<div style><br></div><div style>It's pretty rare to assign a doc team person to an API spec, typically the PTL works on it. We do have Diane Fleming on the doc team for API work and she's super knowledgeable and helpful. I have her working with Keystone team on their v3 right now, possibly we can have her help you as well if we plan and scope the work. Or you can identify someone with the right knowledge. Let's talk more at the meeting on Tuesday July 9, 2013, 1300 UTC.</div>
<div style><br></div><div style>Thanks,</div><div style>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>Regards,<br><br>Chris<br></div></div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div></div>