<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="">
Sure, I’ve got the patch ready just waiting on a final decision re: governance.
<div class=""><br class="">
</div>
<div class="">Brad</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 9 Jun 2015, at 14:46, 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="">Adrian,</div>
<div class=""><br class="">
</div>
<div class="">I think you are on the road but perhaps you have access to email.</div>
<div class=""><br class="">
</div>
<div class="">Can you pull the trigger on your preferred governance approach? Brad will do the rest (creation of stackforge project, etc) From my perspective, the UI spec is ready to hit the repo and we shouldn’t block these folks good work because we can’t
make a decision :).</div>
<div class=""><br class="">
</div>
<div class="">Given the broad interest from a lot of interested parties and no defined best practice in OpenStack for handling UI governance, I think a separate magnum-ui-core may make the most sense so the Magnum core team responsible for the infrastructure
doesn’t balloon with a bunch of folks that don’t know much about Magnum in detail. If the ui dev team has slow reviews, which I doubt, we can add magnum-core to the magnum-ui-core team as a subteam in gerrit.</div>
<div class=""><br class="">
</div>
<div class="">I know this is a change in my previous stance, but I didn’t expect such broad interest.</div>
<div class=""><br class="">
</div>
<div class="">Brad,</div>
<div class=""><br class="">
</div>
<div class="">Once we get a decision from Adrian, can you submit a stackforge repo creation and link the review on this thread so interested parties can review appropriately?</div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">-steve</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>Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" class="">adrian.otto@rackspace.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 2: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 class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Team,
<div class=""><br class="">
</div>
<div class="">I have published a top level blueprint for a magnum-horizon-plugin:
<div class=""><br class="">
</div>
<div class=""><a href="https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin" class="">https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin</a></div>
<div class=""><br class="">
</div>
<div class="">My suggestion is that any contributor interested in contributing to this feature should subscribe to that blueprint, and record their intent to contribute in the Whiteboard of the BP. Furthermore, I suggest that any contributors who are a good
fit for core reviewer duties for this effort subscribe to the blueprint and mark themselves as “Participation Essential” so I can get a clear picture of how to deal with grouping the related core reviewer team (or adding them to the current core group).</div>
<div class=""><br class="">
</div>
<div class="">I think that this effort would benefit from a spec submitted as a review using the following template:</div>
<div class=""><br class="">
</div>
<div class=""><a href="http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/liberty-template.rst" class="">http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/liberty-template.rst</a></div>
<div class=""><br class="">
</div>
<div class="">Adapt it for magnum (I have not contributed a spec template of our own yet. TODO.)</div>
<div class=""><br class="">
</div>
<div class="">Contribute it here:</div>
<div class=""><br class="">
</div>
<div class=""><a href="http://git.openstack.org/cgit/openstack/magnum/tree/specs" class="">http://git.openstack.org/cgit/openstack/magnum/tree/specs</a></div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class=""><br class="">
</div>
<div class="">Adrian</div>
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Jun 4, 2015, at 12:58 PM, 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="">Hey folks,</div>
<div class=""><br class="">
</div>
<div 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.</div>
<div class=""><br class="">
</div>
<div 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.</div>
<div class=""><br class="">
</div>
<div class="">As far as “how to get patches approved”, there are two models we can go with.</div>
<div class=""><br class="">
</div>
<div class="">Option #1:</div>
<div 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.</div>
<div class=""><br class="">
</div>
<div class="">Option #2:</div>
<div 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.</div>
<div class=""><br class="">
</div>
<div class="">Cores, please vote on Option #1, or Option #2, and Adrian can make a decision based upon the results.</div>
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class="">-steve</div>
<div class=""><br class="">
</div>
</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>
</div>
</div>
</div>
</blockquote>
</span></div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>