Open Stack

Adiran,

Disagree.

The python-magnumclient and heat-coe-templates have separate launchpad trackers.  I suspect we will want a separate tracker for python-k8sclient when we are ready for that.

IMO each repo should have a separate launchpad tracker to make the lives of the folks maintaining the software easier :)  This is a common best practice in OpenStack.

Regards
-steve


From: Adrian Otto <adrian.otto at rackspace.com<mailto:adrian.otto at rackspace.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: Friday, June 12, 2015 at 7:47 AM
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

Steve,

There is no need for a second LP project at all.

Adrian


-------- Original message --------
From: "Steven Dake (stdake)" <stdake at cisco.com<mailto:stdake at cisco.com>>
Date: 06/12/2015 7:41 AM (GMT-08:00)
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

Adrian,

Great thanks for that.  I would recommend one change and that is for one magnum-drivers team across launchpad trackers.  The magnum-drivers team as you know (this is for the benefit of others) is responsible for maintaining the states of the launchpad trackers.

Regards,
-steve

From: Adrian Otto <adrian.otto at rackspace.com<mailto:adrian.otto at rackspace.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 11, 2015 at 7:21 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

Team,

We are fortunate enough to have a thriving community of developers who want to make OpenStack great, and several of us have pledged support for this work in Magnum. Due to the amount of interest expressed in this pursuit, and the small amount of overlap between the developers in magnum-core, I’m authorizing the creation of a new gerrit ACL group named magnum-ui-core. Please install me as the pilot member of the group. I will seed the group with those who have pledged support for the effort from the “essential” subscribers to the following blueprint. If our contributors to the magnum-ui repo feel that review velocity is too low, I will add magnum-core as a member so we can help. On regular intervals, I will review the activity level of our new group, and make adjustments as needed to add/subtract from it in accordance with input from the active contributors. We will use the Magnum project on Launchpad for blueprints and bugs.

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

There are 8 contributors identified, who will comprise our initial magnum-ui-core group.

I ask that the ACLs be configured as follows:

[access "refs/heads/*"]
abandon = group magnum-ui-core
create = group magnum-milestone
label-Code-Review = -2..+2 group magnum-ui-core
label-Workflow = -1..+1 group magnum-ui-core

[access "refs/tags/*"]
pushSignedTag = group magnum-milestone

[receive]
requireChangeId = true
requireContributorAgreement = true

[submit]
mergeContent = true

Thanks everyone for your enthusiasm about this new pursuit. I look forward to working together with you to make this into something we are all proud of.

Adrian

PS: Special thanks to sdake for initiating this conversation, and helping us to arrive at a well reasoned decision about how to approach this.

On Jun 4, 2015, at 10:58 AM, 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

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