Licensing issue with cvs2svn

Hello,

I'm the main maintainer of cvs2svn, which is under a CollabNet license.

Greg Ward has been working on cvs2hg, a variation of cvs2svn that
converts directly to Mercurial.  For this work, he would like to "import
mercurial" from cvs2svn code (it is Python) and push the output to
Mercurial via its API.

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].

There was a discussion on the cvs2svn dev mailing list a while ago about
changing the license of cvs2svn [2].  I would support such a change.  It
seems that part of the process would be finding somebody to whom the
license can be assigned.  One obvious choice would be the Subversion
Foundation.

I have no strong preference about what open-source license should apply
to cvs2svn, except that it be GPLv2-compatible.  Unfortunately, that
seems to exclude the Apache license version 2.0 (which is used by
Subversion) [3].

If CollabNet could be persuaded to assign the cvs2svn license to the
Subversion Foundation, would you be willing to accept it?  And if so,
would you be willing to do so under a GPLv2-compatible license?

Suggestions and/or help would be *greatly* appreciated!

Thanks,
Michael

[1]
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&viewType=browseAll&dsMessageId=2393193#messagefocus
[2]
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&viewType=browseAll&dsMessageId=2375923
[3] http://www.gnu.org/philosophy/license-list.html

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

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