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: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to