<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">There is a formal structure via the OpenStack user committee and the associated working groups (https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee).
We have Monday afternoon and all of Thursday in the summit time dedicated to discussions. The specs review process was prepared with the TC to allow easy ways for deployers and consumers of OpenStack to give input before code gets written.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Further volunteers and suggestions on how to improve the process in this area would be more than welcome in the design summit tracks
around the Ops summit and working groups. Please see <a href="http://kilodesignsummit.sched.org/">
http://kilodesignsummit.sched.org/</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Mike Spreitzer [mailto:mspreitz@us.ibm.com]
<br>
<b>Sent:</b> 24 October 2014 07:05<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [all] How can we get more feedback from users?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><tt><span style="font-size:10.0pt">Angus Salkeld <<a href="mailto:asalkeld@mirantis.com">asalkeld@mirantis.com</a>> wrote on 10/24/2014 12:32:04 AM:</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt>> I have felt some grumblings about usability issues with Heat </tt><br>
<tt>> templates/client/etc..</tt></span> <br>
<tt><span style="font-size:10.0pt">> and wanted a way that users could come and give us feedback easily
</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>> (low barrier). I started an etherpad (<a href="https://">https://</a></tt><br>
<tt>> etherpad.openstack.org/p/heat-useablity-improvements) - the first </tt><br>
<tt>> win is it is spelt wrong :-O</tt><br>
</span><br>
<tt><span style="font-size:10.0pt">> We now have some great feedback there in a very short time, most of
</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>> this we should be able to solve.</tt><br>
</span><br>
<tt><span style="font-size:10.0pt">> This lead me to think, "should OpenStack have a more general
</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>> mechanism for users to provide feedback". The idea is this is not </tt><br>
<tt>> for bugs or support, but for users to express pain points, requests </tt><br>
<tt>> for features and docs/howtos.</tt><br>
</span><br>
<tt><span style="font-size:10.0pt">> It's not easy to improve your software unless you are listening to your users.</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
</span><br>
<tt><span style="font-size:10.0pt">> Ideas?</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
</span><br>
<tt><span style="font-size:10.0pt">I very much agree with this.</span></tt> <br>
<br>
<tt><span style="font-size:10.0pt">I am actually surprised that OpenStack does not have something fairly formal and organized about this. I suppose it is part of the TC's job, but I think we need more than they can do. I would suggest some sort of user's
council that gets involved in blueprint and change reviews. Perhaps after first working toward some degree of consensus and some degree of shaping what the developers work on in each release (this latter is part of the overall program of improving review
queue speed, by better focusing developers and reviewers on some shared agenda).</span></tt>
<br>
<br>
<tt><span style="font-size:10.0pt">Other products have discussion fora, some explicitly dedicated to feedback. You could approximate this with etherpads, or use some real discussion forum platform.</span></tt>
<br>
<br>
<tt><span style="font-size:10.0pt">Regards,</span></tt> <br>
<tt><span style="font-size:10.0pt">Mike</span></tt><o:p></o:p></p>
</div>
</div>
</body>
</html>