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

Re: Backporting features from trunk to 1.6.x

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 21 Jun 2011 13:52:37 +0200

On Tue, Jun 21, 2011 at 01:29:56PM +0200, Björn Kasteleiner wrote:
> Hello,
> I'm new to the subversion users mailing list.
> Due to a larger subversion server setup, I would like to backport the AuthzSVNReposRelativeAccessFile feature of the Apache authz module.
> This backport patch is based on the revisions 1030536 and 1071781. Except one small change due to missing API calls.
> So far, it doesn't seem to be a problem.
> But then I've realized that the code license has been changed between the 1.6.x releases and the current trunk including the code mentioned above.
> Is it allowed to use new change sets (from trunk, Apache License) in combination with the codebase of version 1.6.x (CollabNet License)?
> Or, does it violate the licenses?
> I want to host the backport as Debian/Ubuntu package at a Launchpad ppa (personal package archive).
> Do I've to mention the license change somewhere in the package/patch, if I include change sets from trunk? Or does everything sticks on the old license?
> Best regards
> Björn

Neither the Apache Licence 1 (which the licence of Subversion 1.6 is
based on), nor the Apache Licence 2 (which is the licence of Subversion
1.7) require that derivative works be distributed under the exact
same licence terms as the original work. They just require attribution.
See http://en.wikipedia.org/wiki/Apache_License for a good summary.

In short: This isn't copyleft, so do whatever you please, but quote the
licences you've used to ensure proper attribution. E.g. you could include
a NOTICE file in your modified distribution that contains the APLv2
and explains which of the particular changes you backported this licence
applies to.

We don't bother to do this with our official backports though.
The backports simply fall under the terms of the old licence when
they get released. But then again, the project owns copyright to
these changes in the first place :)
Received on 2011-06-21 13:53:54 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.