[openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

Brad Topol btopol at us.ibm.com
Thu Jun 4 18:49:16 UTC 2015


How big a work item is this?


Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet:  btopol at us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680



From:   Thai Q Tran/Silicon Valley/IBM at IBMUS
To:     "OpenStack Development Mailing List \(not for usage questions\)" 
<openstack-dev at lists.openstack.org>
Date:   06/04/2015 02:20 PM
Subject:        Re: [openstack-dev] [magnum][horizon] Making a dashboard 
for Magnum - need a vote from the core team



I am interested but not sure how much time I have this release cycle. I 
can take on a more hands-off approach and help review to make sure that 
magnum-ui is align with future horizon directions.

-----"Steven Dake (stdake)" <stdake at cisco.com> wrote: -----
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev at lists.openstack.org>
From: "Steven Dake (stdake)" <stdake at cisco.com>
Date: 06/04/2015 11:03AM
Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - 
need a vote from the core team

Hey folks,

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.

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.

As far as “how to get patches approved”, there are two models we can go 
with.

Option #1:
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.

Option #2:
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.

Cores, please vote on Option #1, or Option #2, and Adrian can make a 
decision based upon the results.

Regards
-steve

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150604/8642697d/attachment.html>


More information about the OpenStack-dev mailing list