<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 30, 2014 at 11:48 AM, Joe Gordon <span dir="ltr"><<a href="mailto:joe.gordon0@gmail.com" target="_blank">joe.gordon0@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Oct 30, 2014 at 9:20 AM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Thu, Oct 30, 2014 at 10:53 AM, Joe Gordon <span dir="ltr"><<a href="mailto:joe.gordon0@gmail.com" target="_blank">joe.gordon0@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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Thu, Oct 30, 2014 at 4:01 AM, Thierry Carrez <span dir="ltr"><<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</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"><span>Jay Pipes wrote:<br>
> On 10/29/2014 09:07 PM, Russell Bryant wrote:<br>
>> On 10/29/2014 06:46 PM, Rochelle Grober wrote:<br>
>>> Any chance we could use the opening to move either the Refstack<br>
>>> session or the logging session from their current joint (and<br>
>>> conflicting) time (15:40)? QA really would be appreciated at both.<br>
>>> And I'd really like to be at both. I'd say the Refstack one would go<br>
>>> better in the debug slot, as the API stuff is sort of related to the<br>
>>> logging. Switching with one of the 14:50 sessions might also work.<br>
>>><br>
>>> Just hoping. I really want great participation at all of these<br>
>>> sessions.<br>
>><br>
>> The "gate debugging" session is most likely going to be dropped at this<br>
>> point. I don't see a big problem with moving the refstack one to that<br>
>> slot (the first time).<br>
>><br>
>> Anyone else have a strong opinion on this?<br>
><br>
> Sounds good to me.<br>
<br>
</span>Sounds good.<br></blockquote><div><br></div></span><div>With the "gate debugging" session being dropped due to being the wrong format to be productive, we now need a new session. After looking over the etherpad of proposed cross project sessions I think there is one glaring omission: the SDK. In the "Kilo Cycle Goals Exercise" thread [0] having a real SDK was one of the top answers. Many folks had great responses that clearly explained the issues end users are having [1]. As for who could lead a session like this I have two ideas: Monty Taylor, who had one of the most colorful explanations to why this is so critical, or Dean Troyer, one of the few people actually working on this right now. I think it would be embarrassing if we had no cross project session on SDKs, since there appears to be a consensus that the making life easier for the end user is a high priority. </div><div><br></div></div></div></div></blockquote><div><br></div></span><div>There are many discussion sessions related to SDKs, they just aren't all in the cross-project slots. Plus these don't require an ATC badge (something users may not have).</div></div></div></div></blockquote><div><br></div></span><div>If we want to make sure the end user has a more uniform experience, having the individual python-*client discussions isn't sufficient. </div><div><br></div><div>Also, the issue is not lack of user feedback, the issue here is more of a lack of people implementing the feedback.</div></div></div></div></blockquote><div><br></div><div>Agreed, so a cross-project session may help with that. Still, non-ATCs may want to pick up this work and just don't know how. I'd like to see ATC at the Ecosystem sessions to help with that direction of contribution. I know we need this session, just trying to find a place.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><p>Application Ecosystem Working Group<br><span></span></p>
<p><span><a href="https://wiki.openstack.org/wiki/Application_Ecosystem_Working_Group" target="_blank">https://wiki.openstack.org/wiki/Application_Ecosystem_Working_Group</a></span></p>
<p><span>Monday 2:30 (Degas)</span></p>
<p><span>Thursday 1:40 (Hyatt)</span></p></div></div></div></div></blockquote><div><br></div></span><div>These sessions have pretty broad scopes, and I don't think a discussion on SDKs here is enough, since the issue isn't a lack of feedback.</div></div></div></div></blockquote><div><br></div><div>Okay, fair enough. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>
<p><span></span></p><p>I think we can talk about the real SDK at one of these.</p><p><span>There's also:</span></p><p><span>Getting Started with the OpenStack Python SDK</span></p>
<p><span>Monday 4:20 (Room 242AB)</span></p></div></div></div></div></blockquote></span><div>This isn't a a design summit session, so it doesn't really make sense to do future design work here.</div></div></div></div></blockquote><div><br></div><div>Agreed, was just making sure people on this list are aware.</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><span><font color="#888888">
<p>Anne <br></p><p><span></span></p></font></span></div><span><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>The current catch is, the free slot is now at 15:40, so it would compete with 'How to Tackle Technical Debt in Kilo,' a session which I expect to be very popular with the same people who would be interested in attending a SDK session.</div><div><br></div><div>[0] <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-September/044766.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2014-September/044766.html</a></div><div>[1] <a href="https://etherpad.openstack.org/p/6cWQG9oNsr" target="_blank">https://etherpad.openstack.org/p/6cWQG9oNsr</a></div><span><div><br></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">
<span><font color="#888888"><br>
--<br>
Thierry Carrez (ttx)<br>
</font></span><div><div><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</div></div></blockquote></span></div><br></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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></span></div><br></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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></span></div><br></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></div></div>