Open Stack

I noticed a good statement, marked it inline.


On 9/28/16 7:24 AM, John Davidge wrote:
> Hi Zane,
>
> Thanks for pointing this out! My interpretation of the StackForge
> Retirement page[1] was wrong on that point. I've updated the blog post to
> reflect that (without removing the original interpretation).
>
> The discussion about renaming git repos is a bit of a red herring, because
> what we're really talking about is what it *means* to be in Stackforge vs.
> OpenStack vs. OpenStack Family, not which git namespace a project should
> live in. Apologies if I didn't make that clear.
>
> Like many of us, I do my best to keep up with historical context, but when
> there is so much contradictory information/opinion out there about what
> OpenStack is/isn't was/wasn't it can be a struggle at times. The crux of

"""
> my proposal is aiming to solve that by not trying to be everything to
> everyone under one tent - by defining sensible boundaries to separate the
> different goals of the community.
"""

+1000 to sensible boundaries. the key factor is to strike the balance.
>
> All the best,
>
> John
>
> [1] https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement
>
> On 9/27/16, 5:13 PM, Zane Bitter wrote:
>
>> On 27/09/16 06:19, John Davidge wrote:
>>>> Having Stackforge as a separate Github organization and set of
>>>>> repositories was a maintenance nightmare due to the awkwardness of
>>>>> renaming projects when they "moved into OpenStack".
>>> There's no reason that this would need a separate github structure, just
>>> separate messaging and rules.
>> That's exactly what we have now.
>>
>> This statement on your blog:
>>
>> "[StackForge] was retired in October 2015, at which point all projects
>> had to move into the OpenStack Big Tent or leave entirely."
>>
>> is completely false. That never happened. There are still plenty of
>> repos on git.openstack.org that are not part of the Big Tent. At no time
>> has any project been required to join the Big Tent in order to continue
>> being hosted.
>>
>> Maybe you should consider reading up on the historical background to
>> these changes. There are a lot of constraints that have to be met - from
>> technical ones like the fact that it's not feasible to rename git repos
>> when they move into or out of the official OpenStack project, to legal
>> ones like how the TC has to designate projects in order to trigger
>> certain rights and responsibilities in the (effectively immutable)
>> Foundation by-laws. Rehashing all of the same old discussions without
>> reference to these constraints is unlikely to be productive.
>>
>> cheers,
>> Zane.
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> ________________________________
> Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse at rackspace.com and delete the original message. Your cooperation is appreciated.
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil