On 04/22/2015 09:55 PM, Anita Kuno wrote:
> On 04/22/2015 09:46 PM, Kyle Mestery wrote:
>> On Wed, Apr 22, 2015 at 7:44 PM, Armando M. <arma...@gmail.com> wrote:
>>
>>>
>>>
>>> On 22 April 2015 at 11:19, Russell Bryant <rbry...@redhat.com> wrote:
>>>
>>>> Hello!
>>>>
>>>> A couple of things I've been working on lately are project governance
>>>> issues as a TC member and also implementation of a new virtual
>>>> networking alternative with a Neutron driver.  So, naturally I started
>>>> thinking about how the Neutron driver code fits in to OpenStack
>>>> governance.
>>>>
>>>> There are basically two areas with a lot of movement related to this
>>>> issue.
>>>>
>>>> 1) Project governance has moved to a "big tent" model [1].  The vast
>>>> majority of projects that used to be in Stackforge are being folded in
>>>> to a larger definition of the OpenStack project.  Projects making this
>>>> move meet the following criteria as being "one of us":
>>>
>>>
>>> Is it sensible to assume that Stackforge is going away entirely at some
>>> point in the future, and we'll have a single namespace - OpenStack?
>>>
>>>
>>
>> IMHO, I'm not sure what the StackForge designation means anymore now that
>> we have the Big Tent. I obviously also don't have the authority to make the
>> call on when it goes away however.
> Moving everything from Stackforge into the OpenStack namespace is
> something that Jim Blair has said he would like to see happen. There has
> been no resolution or focused discussion on this exact point that has
> been put before the TC that I have seen.

I think things are moving fast enough.  We need to make sure all of the
repos are properly captured under a team, but it seems momentum is
picking up.  This thread is part of that.

-- 
Russell Bryant

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

Reply via email to