Re: Turning cvs2{svn,git} into cvs2hg

Michael Haggerty wrote:
> [...]
> By the way, there is also a possible problem related to the license of
> cvs2svn vs. those of the DVCSs.  IANAL but it seems to me that the
> CollabNet license is *not* GPLv2-compatible.  Therefore it might not
> even be possible to create a tight integration of cvs2svn and hg code.
> It might be possible to get CollabNet to change the license that is
> applied to cvs2svn (for example, I would certainly support a change to
> GPLv2), but those discussions haven't even been started.

Greg,

I don't remember that you ever addressed this issue.  Before I start
committing cvs2hg patches willy-nilly, can you please let us know why
you think that we are on safe ground license-wise?

Or if not, then we should see whether we can convince CollabNet to
change the cvs2svn license, for example to GPLv2 (I haven't yet pursued
this).  See this thread for more info:

http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&viewType=browseAll&dsMessageId=2375923#messagefocus

Michael

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

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