Re: Licensing on donated code in the Python bindings

On 04 Aug 2005 11:20:03 -0500, kfogel@collab.net <kfogel@collab.net> wrote:
> Brian Behlendorf <brian@collab.net> writes:
> > On Wed, 3 Aug 2005, David James wrote:
> > > In order to comply with the New BSD license, we'll need to add the
> > > following disclaimer into the directory containing the new abstraction
> > > layer and test suite. Would this be OK? This license only applies to
> > > the code that the Trac team has donated to us. We'll still own the
> > > full copyright on any code we write.
> >
> > Speaking for CollabNet, submissions under this license are perfectly fine.
>
> If Brian says it's okay by CollabNet, then go for it, David.
>
> (But thanks for asking first.)
Thanks, Brian and Karl!

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

-- 
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org