<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 31, 2014 at 10:40 PM, Adam Young <span dir="ltr"><<a href="mailto:ayoung@redhat.com" target="_blank">ayoung@redhat.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>On 03/28/2014 03:01 AM, Tom Fifield 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">
Thanks to those projects that responded. I've proposed sessions in swift, ceilometer, tripleO and horizon.<br>
</blockquote>
<br>
<br></div>
Keystone would also be interested in user feedback, of course.</blockquote><div><br></div><div>Crossing openstack-dev threads [1] here, gathering feedback on proposed deprecations would be a great topic for such a session.</div>
<div><br></div><div>[1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-April/031652.html">http://lists.openstack.org/pipermail/openstack-dev/2014-April/031652.html</a></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><div><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">
<br>
On 17/03/14 07:54, Tom Fifield 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">
All,<br>
<br>
Many times we've heard a desire for more feedback and interaction from<br>
users. However, their attendance at design summit sessions is met with<br>
varied success.<br>
<br>
However, last summit, by happy accident, a swift session turned into a<br>
something a lot more user driven. A competent user was able to describe<br>
their use case, and the developers were able to stage a number of<br>
question to them. In this way, some of the assumptions about the way<br>
certain things were implemented, and the various priorities of future<br>
plans became clearer. It worked really well ... perhaps this is<br>
something we'd like to have happen for all the projects?<br>
<br>
*Idea*: Add an "ops" session for each project in the design summit<br>
<a href="https://etherpad.openstack.org/p/ATL-ops-dedicated-design-summit-sessions" target="_blank">https://etherpad.openstack.<u></u>org/p/ATL-ops-dedicated-<u></u>design-summit-sessions</a> <br>
<br>
<br>
Most operators running OpenStack tend to treat it more holistically than<br>
those coding it. They are aware of, but don't necessarily think or work<br>
in terms of project breakdowns. To this end, I'd imagine the such<br>
sessions would:<br>
<br>
* have a primary purpose for developers to ask the operators to answer<br>
questions, and request information<br>
<br>
* allow operators to tell the developers things (give feedback) as a<br>
secondary purpose that could potentially be covered better in a<br>
cross-project session<br>
<br>
* need good moderation, for example to push operator-to-operator<br>
discussion into forums with more time available (eg<br>
<a href="https://etherpad.openstack.org/p/ATL-ops-unconference-RFC" target="_blank">https://etherpad.openstack.<u></u>org/p/ATL-ops-unconference-RFC</a> )<br>
<br>
* be reinforced by having volunteer "good" users in potentially every<br>
design summit session<br>
(<a href="https://etherpad.openstack.org/p/ATL-ops-in-design-sessions" target="_blank">https://etherpad.openstack.<u></u>org/p/ATL-ops-in-design-<u></u>sessions</a> )<br>
<br>
<br>
Anyway, just a strawman - please jump on the etherpad<br>
(<a href="https://etherpad.openstack.org/p/ATL-ops-dedicated-design-summit-sessions" target="_blank">https://etherpad.openstack.<u></u>org/p/ATL-ops-dedicated-<u></u>design-summit-sessions</a>) <br>
or leave your replies here!<br>
<br>
<br>
Regards,<br>
<br>
<br>
Tom<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>