On Mon, Sep 17, 2007 at 01:18:05PM +0200, Hannah Schroeter wrote:
quoted text
> >So for code which is single-licensed under a BSD license, someone can
> >create a new derived work, and redistribute it under a more
> >restrictive license --- either one as restrictive as NetApp's (where
> >no one is allowed to get binary unless they are a NetApp customer, or
> >source only after signing an NDA), or a GPL license.  It is not a
> >relicencing, per se, since the original version of the file is still
> >available under the original copyright; it is only the derived work
> >which is under the more restrictive copyright.   
> 
> No. The derivative work altogether has a *mixed* license. BSD/ISC for
> the parts that are original, the other (restrictive, GPL, whatever)
> license for the modifications/additions.

Yes, agreed.  I was being sloppy.  In actual practice, the GPL is more
restrictive, aod so the terms of the GPL are what tend to have more
effect, but you are absolutely correct.

quoted text
> *If* you choose to distribute source along with the binaries, the part
> of the source that's original is BSD/ISC licensed even in the derivative
> work (though one may put *the additions/modifications* under restrictive
> conditions, e.g. of commercial non-disclosure type source licensing).

Yes, although actually, the place where the BSD license must be
honored is in a binary distribution, since the BSD license and
copyright attribution must be distributed as part of the binary
distribution.  (Even Microsoft does this when they use BSD code.)

For a source distribution, retaining the copyright attribution and
permission statement in the comments is sufficient to meet the BSD
license requirements, and since the open source world normally deals
mostly with source, we sometimes get sloppy with how we phrase things.

Regards,

						- Ted