Open Stack

Initial draft of spec is out for review here https://review.openstack.org/188958 feedback welcome :)

Thanks,
Brad Jones

On 4 Jun 2015, at 22:30, Adrian Otto <adrian.otto at rackspace.com<mailto:adrian.otto at rackspace.com>> wrote:

Team,

I have published a top level blueprint for a magnum-horizon-plugin:

https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin

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).

I think that this effort would benefit from a spec submitted as a review using the following template:

http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/liberty-template.rst

Adapt it for magnum (I have not contributed a spec template of our own yet. TODO.)

Contribute it here:

http://git.openstack.org/cgit/openstack/magnum/tree/specs

Thanks,

Adrian

On Jun 4, 2015, at 12:58 PM, Steven Dake (stdake) <stdake at cisco.com<mailto:stdake at cisco.com>> wrote:

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<mailto: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<mailto: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/20150605/17948dd5/attachment.html>