<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Tom,
<div>This is a great idea! Feel free to reach out to the user experience folks, as they’ll be interested both in attending and helping coordinate.
<div><br>
</div>
<div><a href="http://ask-openstackux.rhcloud.com/questions/">http://ask-openstackux.rhcloud.com/questions/</a></div>
<div><a href="mailto:openstack-personas@lists.openstack.org">openstack-personas@lists.openstack.org</a></div>
<div><br>
</div>
<div>Best,</div>
<div>Jacki<br>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div>
<div>On Mar 28, 2014, at 2:01 AM, Tom Fifield <<a href="mailto:tom@openstack.org">tom@openstack.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">Thanks to those projects that responded. I've proposed sessions in swift, ceilometer, tripleO and horizon.<br>
<br>
On 17/03/14 07:54, Tom Fifield wrote:<br>
<blockquote type="cite">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">https://etherpad.openstack.org/p/ATL-ops-dedicated-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>
https://etherpad.openstack.org/p/ATL-ops-unconference-RFC )<br>
<br>
* be reinforced by having volunteer "good" users in potentially every<br>
design summit session<br>
(https://etherpad.openstack.org/p/ATL-ops-in-design-sessions )<br>
<br>
<br>
Anyway, just a strawman - please jump on the etherpad<br>
(https://etherpad.openstack.org/p/ATL-ops-dedicated-design-summit-sessions)<br>
or leave your replies here!<br>
<br>
<br>
Regards,<br>
<br>
<br>
Tom<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>