[openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team
Bradley Jones (bradjone)
bradjone at cisco.com
Thu Jun 4 21:28:51 UTC 2015
>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.
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.
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 :)
On 4 Jun 2015, at 21:35, Steven Dake (stdake) <stdake at cisco.com<mailto:stdake at cisco.com>> wrote:
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 :)
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?
From: Hongbin Lu <hongbin.lu at huawei.com<mailto:hongbin.lu at huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thursday, June 4, 2015 at 1:30 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team
Could we have a new group magnum-ui-core and include magnum-core as a subgroup, like the heat-coe-tempalte-core group.
From: Steven Dake (stdake) [mailto:stdake at cisco.com]
Sent: June-04-15 1:58 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team
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.
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.
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.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev