Re: [openstack-dev] Designate Incubation Request (Approved)

2014-06-11 Thread Mac Innes, Kiall
On Sat, 2014-05-24 at 17:24 +, Hayes, Graham wrote: > Hi all, > > Designate would like to apply for incubation status in OpenStack. > > Our application is here: > https://wiki.openstack.org/wiki/Designate/Incubation_Application > > As part of our application we would like to apply for a ne

Re: [openstack-dev] Designate Incubation Request

2014-06-06 Thread Mac Innes, Kiall
Several of the TC requested we have an openstack-infra managed DevStack gate enabled before they would cast their vote - I'm happy to say, we've got it :) With the merge of [1], Designate now has voting devstack / requirements / docs jobs. An example of the DevStack run is at [2]. "Vote Designate

Re: [openstack-dev] Designate Incubation Request

2014-05-30 Thread Thierry Carrez
Zane Bitter wrote: > I think the problem is that we still have elements of the 'project' > terminology around from the bad old days of the pointless > core/core-but-don't-call-it-core/library/gating/supporting project > taxonomy, where project == repository. The result is that every time a > new pr

Re: [openstack-dev] Designate Incubation Request

2014-05-29 Thread Zane Bitter
On 29/05/14 05:26, Thierry Carrez wrote: Sean Dague wrote: I honestly just think we might want to also use it as a time to rethink our program concept. Because all our programs that include projects that are part of the integrated release are 1 big source tree, and maybe a couple of little trees

Re: [openstack-dev] Designate Incubation Request

2014-05-29 Thread Mac Innes, Kiall
On Thu, 2014-05-29 at 08:00 +0930, Michael Davies wrote: > On Thu, May 29, 2014 at 4:22 AM, Sean Dague wrote: > > I would agree this doesn't make sense in Neutron. > > > > I do wonder if it makes sense in the Network program. I'm getting > > suspicious of the programs for projects model if every n

Re: [openstack-dev] Designate Incubation Request

2014-05-29 Thread Mac Innes, Kiall
On Thu, 2014-05-29 at 11:26 +0200, Thierry Carrez wrote: > Back to the topic, the tension here is because DNS is seen as a > "network" thing and therefore it sounds like it makes sense under > "Networking". But "programs" are not categories or themes. They are > teams aligned on a mission statement

Re: [openstack-dev] Designate Incubation Request

2014-05-29 Thread Sean Dague
On 05/29/2014 05:26 AM, Thierry Carrez wrote: > Sean Dague wrote: >> I honestly just think we might want to also use it as a time to rethink >> our program concept. Because all our programs that include projects that >> are part of the integrated release are 1 big source tree, and maybe a >> couple

Re: [openstack-dev] Designate Incubation Request

2014-05-29 Thread Thierry Carrez
Sean Dague wrote: > I honestly just think we might want to also use it as a time to rethink > our program concept. Because all our programs that include projects that > are part of the integrated release are 1 big source tree, and maybe a > couple of little trees that orbit it (client and now specs

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Sean Dague
On 05/28/2014 07:11 PM, James E. Blair wrote: > Sean Dague writes: > >> I would agree this doesn't make sense in Neutron. >> >> I do wonder if it makes sense in the Network program. I'm getting >> suspicious of the programs for projects model if every new project >> incubating in seems to need a

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread James E. Blair
Sean Dague writes: > I would agree this doesn't make sense in Neutron. > > I do wonder if it makes sense in the Network program. I'm getting > suspicious of the programs for projects model if every new project > incubating in seems to need a new program. Which isn't really a > reflection on desig

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Michael Davies
On Thu, May 29, 2014 at 4:22 AM, Sean Dague wrote: > I would agree this doesn't make sense in Neutron. > > I do wonder if it makes sense in the Network program. I'm getting > suspicious of the programs for projects model if every new project > incubating in seems to need a new program. Which isn't

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Carl Baldwin
That is what I was not sure about, if they are currently one in the same. Thanks for the link. Carl On May 28, 2014 2:47 PM, "Hayes, Graham" wrote: > Sorry - not sure what happened there - as I was saying: > > The "Networking Program" is Neutron. > > https://wiki.openstack.org/wiki/Programs > >

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Hayes, Graham
Sorry - not sure what happened there - as I was saying: The "Networking Program" is Neutron. https://wiki.openstack.org/wiki/Programs Graham On 28/05/2014 21:29, "Hayes, Graham" wrote: >___ >OpenStack-dev mailing list >OpenStack-dev@lists.openst

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Hayes, Graham
smime.p7m Description: S/MIME encrypted message ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Carl Baldwin
+1 This makes sense except that I'm not sure what the "Network Program" is. Is there already such a thing formally? Carl On Wed, May 28, 2014 at 12:52 PM, Sean Dague wrote: > I would agree this doesn't make sense in Neutron. > > I do wonder if it makes sense in the Network program. I'm getting

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Kyle Mestery
On Wed, May 28, 2014 at 1:52 PM, Sean Dague wrote: > I would agree this doesn't make sense in Neutron. > > I do wonder if it makes sense in the Network program. I'm getting > suspicious of the programs for projects model if every new project > incubating in seems to need a new program. Which isn't

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Zane Bitter
On 28/05/14 14:52, Sean Dague wrote: I would agree this doesn't make sense in Neutron. I do wonder if it makes sense in the Network program. I'm getting suspicious of the programs for projects model if every new project incubating in seems to need a new program. Which isn't really a reflection o

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Sean Dague
I would agree this doesn't make sense in Neutron. I do wonder if it makes sense in the Network program. I'm getting suspicious of the programs for projects model if every new project incubating in seems to need a new program. Which isn't really a reflection on designate, but possibly on our progra

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Carl Baldwin
Does this make sense in Neutron? In my opinion it doesn't. DNSaaS is external to Neutron and is independent. It serves DNS requests that can come from the internet just as well as they can come from VMs in the cloud (but through the network external to the cloud). It can serve IPs for cloud res

Re: [openstack-dev] Designate Incubation Request

2014-05-28 Thread Mac Innes, Kiall
On Tue, 2014-05-27 at 17:42 -0700, Joe Gordon wrote: > On Sat, May 24, 2014 at 10:24 AM, Hayes, Graham > wrote: > > * You mention nova's dns capabilities as not being adequate one of the > incubation requirements is: > Project should not inadvertently duplicate functionality present in other

Re: [openstack-dev] Designate Incubation Request

2014-05-27 Thread Joe Gordon
On Sat, May 24, 2014 at 10:24 AM, Hayes, Graham wrote: > > Hi all, > > Designate would like to apply for incubation status in OpenStack. > Our application is here: > https://wiki.openstack.org/wiki/Designate/Incubation_Application Based on http://git.openstack.org/cgit/openstack/governance/tr

[openstack-dev] Designate Incubation Request

2014-05-24 Thread Hayes, Graham
Hi all, Designate would like to apply for incubation status in OpenStack. Our application is here: https://wiki.openstack.org/wiki/Designate/Incubation_Application As part of our application we would like to apply for a new program. Our application for the program is here: https://wiki.opens