[openstack-dev] How to handle forking of projects

Mark McLoughlin markmc at redhat.com
Thu Jun 6 13:38:35 UTC 2013


On Thu, 2013-06-06 at 11:53 +0200, Thierry Carrez wrote:
> Mark McLoughlin wrote:
> > 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.
> 
> We should avoid bundling in the first place... But those one-file .js
> projects put those good principles to a hard reality test by making it
> very convenient to copy and very inconvenient to depend on.

Right, agree :)

Cheers,
Mark.




More information about the OpenStack-dev mailing list