<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;" class="">
>From a quick look around there doesn’t seem to be a consensus on how to deal with UI teams, some projects seem to use just the main projects core team (group based policy ui), others use a mix of the project core team and the Horizon core team (monasca-ui)
and in the case of tuskar-ui they use just the Horizon core team. I can’t find a case of another project having a dedicated ui-core team but as I say it was a quick look through the project config acls so I may have missed some.
<div class=""><br class="">
</div>
<div class="">My two cents are that it is important that the people working on this effort have some level of control over the code base in order for things to progress quickly and to that end either approach #1, #2 or Hongbin’s suggestions achieves that goal.
So either of the options work for me from that point of view and the decision really has to come down to what will work best in getting current Magnum folks participating in all aspects of the ui design, implementation and particularly reviewing. </div>
<div class=""><br class="">
</div>
<div class="">It is also important to have Horizon cores participate in reviews to ensure that we don’t diverge too much from upstream changes in Horizon, it sounds like we already have that commitment for reviews from David and Thai so thanks guys :)</div>
<div class=""><br class="">
</div>
<div class="">Brad Jones</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 4 Jun 2015, at 21:35, Steven Dake (stdake) <<a href="mailto:stdake@cisco.com" class="">stdake@cisco.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Hongbin,</div>
<div class=""><br class="">
</div>
<div class="">I hadn’t thought of that, even though it seems obvious ;) We can absolutely do that. I almost like this option better then #1 but I don’t want the ui folks to feel like second class citizens. This goes back to the trust the ui developers to
not review things they know not about :)</div>
<div class=""><br class="">
</div>
<div class="">Bradley,</div>
<div class=""><br class="">
</div>
<div class="">How are other OpenStack projects handling the UI teams which clearly have a totally different specialty than the typical core team for a project with the Horizon big tent changes?</div>
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class="">-steve</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<span id="OLK_SRC_BODY_SECTION" class="">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class="">
<span style="font-weight:bold" class="">From: </span>Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com" class="">hongbin.lu@huawei.com</a>><br class="">
<span style="font-weight:bold" class="">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Date: </span>Thursday, June 4, 2015 at 1:30 PM<br class="">
<span style="font-weight:bold" class="">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Subject: </span>Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team<br class="">
</div>
<div class=""><br class="">
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;" class="">
<div 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" class="">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)" class="">
<style class=""><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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 lang="EN-CA" link="blue" vlink="purple" class="">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Could we have a new group magnum-ui-core and include magnum-core as a subgroup, like the heat-coe-tempalte-core group.<o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Thanks,<o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Hongbin<o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></p>
<div class="">
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="">
<p class="MsoNormal"><b class=""><span lang="EN-US" style="font-size: 10pt; font-family: Tahoma, sans-serif;" class="">From:</span></b><span lang="EN-US" style="font-size: 10pt; font-family: Tahoma, sans-serif;" class=""> Steven Dake (stdake) [<a href="mailto:stdake@cisco.com" class="">mailto:stdake@cisco.com</a>]
<br class="">
<b class="">Sent:</b> June-04-15 1:58 PM<br class="">
<b class="">To:</b> OpenStack Development Mailing List (not for usage questions)<br class="">
<b class="">Subject:</b> [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team<o:p class=""></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p class=""> </o:p></p>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">Hey folks,<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">I think it is critical for self-service needs that we have a Horizon dashboard to represent Magnum. I know the entire Magnum team has no experience in UI development,
but I have found atleast one volunteer Bradley Jones to tackle the work.<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">I am looking for more volunteers to tackle this high impact effort to bring Containers to OpenStack either in the existing Magnum core team or as new contributors.
If your interested, please chime in on this thread.<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">As far as “how to get patches approved”, there are two models we can go with.<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">Option #1:<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">We add these UI folks to the magnum-core team and trust them not to +2/+A Magnum infrastructure code. This also preserves us as one team with one mission.<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">Option #2:<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">We make a new core team magnum-ui-core. This presents special problems if the UI contributor team isn’t large enough to get reviews in. I suspect Option #2 will
be difficult to execute.<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">Cores, please vote on Option #1, or Option #2, and Adrian can make a decision based upon the results.<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">Regards<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class="">-steve<o:p class=""></o:p></span></p>
</div>
<div class="">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</span></div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>