<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 05/11/15 09:47, Tim Bell wrote:<br>
</div>
<blockquote
cite="mid:5D7F9996EA547448BC6C54C8C5AAF4E5010A161ED4@CERNXCHG44.cern.ch"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
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]-->
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Within the user committee, we’ve been
reviewing how the various teams and working groups around
operators, end users and ecosystem developers could be
structured. In particular, how we can turn the ideas into
actionable items and expand the activities given the growth in
the user community.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In preparation for the summit, we would
welcome feedback from those interested in the user committee
and product working groups on the proposal below before wider
circulation. The details are in
<a moz-do-not-send="true"
href="https://etherpad.openstack.org/p/uc-2015">https://etherpad.openstack.org/p/uc-2015</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Tim, Jon, Subbu and Tom<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
Hi Tim, this looks like a great start. <br>
<br>
There is something that I am missing and perhaps there could be a
way to pursue this further at the summit.<br>
<br>
Collecting requirements, from different segments - and then what?<br>
<br>
There should be a defined way that this is fed back into the TC or
the project groups and how these requirements and items are made
actionable and placed on the relevant project's roadmap with a
defined target date (release).<br>
<br>
Currently there are a number of groups that are collecting all sorts
of information - which is a great thing - but I am still missing the
other part of the equation. <br>
<br>
So to go back to your North/South idea - perhaps also an east/west
segment - with a feedback loop also to the teams/TC/Foundation? <br>
<br>
<div class="moz-signature">-- <br>
Best Regards,<br>
Maish Saidel-Keesing</div>
</body>
</html>