<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="ace-line" id="magicdomid121"><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z">All,<br>
<br>
Many times we've heard a desire for more feedback and
interaction from users. However, their attendance at design
summit sessions is met with varied success.</span></div>
<div class="ace-line" id="magicdomid123"><br>
</div>
<div class="ace-line" id="magicdomid509"><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z">However,
last summit, by happy accident, a swift session turned into a
something a lot more user driven. A competent user was able to
describe their use case, and the developers were able to stage a
number of question to them. In this way, some of the assumptions
about the way certain things were implemented, and the various
priorities of future plans became clearer. It worked really well
... perhaps this is something we'd like to have happen for all
the projects?<br>
</span></div>
<div class="ace-line" id="magicdomid511"><br>
</div>
<div class="ace-line" id="magicdomid1130"><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z b"><b>Idea</b></span><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z">:
Add an "ops" session for each project in the design summit<br>
</span><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z
url"><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></span><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z"><br>
</span></div>
<div class="ace-line" id="magicdomid628"><br>
<br>
</div>
<div class="ace-line" id="magicdomid1184"><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z">Most
operators running OpenStack tend to treat it more holistically
than those coding it. They are aware of, but don't necessarily
think or work in terms of project breakdowns. To this end, I'd
imagine the such sessions would:</span></div>
<div class="ace-line" id="magicdomid1196">
<ul class="list-bullet1">
<li><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z">have
a primary purpose for developers to ask the operators to
answer questions, and request information</span></li>
</ul>
</div>
<div class="ace-line" id="magicdomid1197">
<ul class="list-bullet1">
<li><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z">allow
operators to tell the developers things (give feedback) as a
secondary purpose that could potentially be covered better
in a cross-project session</span></li>
</ul>
</div>
<div class="ace-line" id="magicdomid1198">
<ul class="list-bullet1">
<li><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z">need
good moderation, for example to push operator-to-operator
discussion into forums with more time available (eg </span><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z
url"><a
href="https://etherpad.openstack.org/p/ATL-ops-unconference-RFC">https://etherpad.openstack.org/p/ATL-ops-unconference-RFC
)</a></span></li>
</ul>
</div>
<div class="ace-line" id="magicdomid1261">
<ul class="list-bullet1">
<li><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z">be
reinforced by having volunteer "good" users in potentially
every design summit session (</span><span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z
url"><a
href="https://etherpad.openstack.org/p/ATL-ops-in-design-sessions">https://etherpad.openstack.org/p/ATL-ops-in-design-sessions
)</a></span></li>
</ul>
</div>
<br>
Anyway, just a strawman - please jump on the etherpad (<span
class="author-a-lmz122zz66zz69zz73zz65zz90z6z75zkk1az66zz69z url"><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>)</span>
or leave your replies here!<br>
<br>
<br>
Regards,<br>
<br>
<br>
Tom<br>
</body>
</html>