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

Re: Licensing on donated code in the Python bindings

From: Brian Behlendorf <brian_at_collab.net>
Date: 2005-08-04 20:35:40 CEST

The license filename sounds fine, I'll leave it to the others to
comment on branch strategy.


On Thu, 4 Aug 2005, David James wrote:
> How do you think I should format the copyright and license notices? I
> can put the legal code in a file named "LICENSE_FOR_PYTHON_BINDINGS"
> under the Python bindings. The license will basically say:
> The Python bindings for Subversion are distributed under the following terms:
> 1. [The text of the Subversion license, with copyright statements]
> 2. [The text of the New BSD license, with copyright statements]
> Does that work? For an example of this technique, see the SWIG license:
> http://www.swig.org/copyright.html
> In each contributed file from Trac, I'll have three copyright
> statements (one for CollabNet, one for Edgewall, and one for
> Christopher Lenz), plus a reference to the
> "LICENSE_FOR_PYTHON_BINDINGS" file. Does that sound good?
> If you're OK with this, I'll start work on it. Should I create a new
> branch for this purpose, or should I just keep working in
> "python-bindings-improvements"?
> Thanks,
> David

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 4 20:37:55 2005

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

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