[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] License of the svnClientAdapter

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-08-29 18:00:46 CEST

"Martin Letenay" <mle@whitestein.com> wrote on 08/29/2005 11:48:04 AM:

> as you've already noticed I've spent some time on svnCleintAdapter over
the weekend.
> Besides several bugfixes I also checked the licensing stuff there.
>
> It seems that most of the files have copyright header with Apache 2.0
license.
> Based on this assumption, I've updated our license.txt file with 2.0
text too.
>
> If you agree, you should then update the web home page where apache 1.1
is
> mentioned as svnClientAdpaters license.

This stuff was all set before I got here, so I cannot provide you any
definitive comment. You are right that all of the source I looked at has
an Apache 2.0 header, so I guess the safest thing it to just update the
web site to reflect this.

> Other issue is that there is 1 file in sources and several test cases
with
> collabnet's license header.
> Is it intentional ? Are they copyrighted that way ?

Again, I do not know. I seem to recall that some of the test suite was
copied from the JavaHL test suite. That may be why.

> And one more, I'm not legal expert at all, but shouldn't we include
thrid
> party license files with their binaries ?
> I mean JavaSVN, Jsch etc, jakarta-regexp ...

Again, no real opinion. Some of these are BSD-style licenses which do not
really carry any kind of requirements. I do not object to having copies
of their license somewhere and generally think it is a good idea. I see
that JavaSVN is changing to a MySQL-type license. We will have to keep
our eyes on the details of that and perhaps stop distributing JavaSVN with
our code depending on the requirements. I do not see how we can mix an
Apache-style license with that license, but all they currently say is that
it will be "like" the MySQL license. So we will need to see the details.
It would be too bad if we had to stop including it after we finally get it
integrated so well.

I guess this also means that they have decided not to contribute JavaSVN
to the Subversion project as was once discussed.

Too bad.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Tue Aug 30 02:00:46 2005

This is an archived mail posted to the Subclipse Dev mailing list.