[openstack-dev] How to handle forking of projects

Mark McLoughlin markmc at redhat.com
Thu Jun 6 09:45:41 UTC 2013


On Thu, 2013-06-06 at 10:34 +0200, Matthias Runge wrote:
> Hey,
> I came to this question over the the following review:
> https://review.openstack.org/#/c/31725/
> 
> The situation is: Horizon ships a bundled library query-table-sorter,
> which hasn't seen a release since ages.
> The proposed commit changes the bundled lib, effectively creating a fork.
> 
> Is that allowed/desired, or how should we handle this?

I agree with you that we should avoid forking a library.

Maybe it wouldn't be ridiculous to have a patch file in the source tree
that gets applied to the library by e.g. devstack and we tell OpenStack
distributors they need to include the patch in their version of the
library ... assuming everyone isn't just using the bundled version. I
dunno.

> As a side note, that plugin is licensed as GPL (without a version) and MIT.
> 
> Are we allowed to bundle this at all?

Good question, referred to legal-discuss here:

  http://lists.openstack.org/pipermail/legal-discuss/2013-June/000077.html

Cheers,
Mark.




More information about the OpenStack-dev mailing list