Re: Licensing issue with cvs2svn

Michael Haggerty wrote:
> [...]
> The problem is that Mercurial is GPLv2, and it is not clear to me that
> the CollabNet license is compatible with GPLv2; it seems likely that it
> is not.  Therefore it is at best questionable whether linking cvs2svn
> and Mercurial is permitted [1].

Great news!  I inquired at [email protected] whether cvs2svn's CollabNet
license is GPLv2-compatible.  According to the response (attached), it is!

So, happily, we do not have to continue debating whether importing a
Python library creates a "derived work", because in either case it is
permissible for cvs2svn and cvs2hg to import from Mercurial.

In light of this development, it would be a definite step backwards to
relicense cvs2svn under an Apache 2.0 license.  So I think the status
quo is perfectly acceptable.

Now I can try to get to reviewing Greg Ward's patches :-)

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2399159

To unsubscribe from this discussion, e-mail: [[email protected]].