Re: License of the contrib plugins

On Mon, 4 Apr 2005, Tollef Fog Heen wrote:
>
> What would probably be more useful is if we say that «Any plugins 
> distributed in the contrib tarball must be licensed under the GPL, MIT 
> or BSD license».  As the author, you are free to change the license on 
> your software, so you could tell somebody with checkin rights that 
> «please change the license of firstdaydiv.py to the MIT license by 
> putting this (instert LICENSE.txt from the pyblosxom core here, replace 
> «Wari Wahab» with «Blake Winton») at the head of the file».
>
> (Or similarly for the GPL, where you'd insert the last part of the 
> license, where it says «How to Apply These Terms to Your New Programs», 
> and again similarly for the BSD license.)
>
> For the core, it's fine to just have a single LICENSE file, but I think 
> it would be best if each plugin carried the license (or license 
> boilerplate, in the case of GPL) in the file itself so it's completely 
> clear which license applies to which file.

In case we all get hit by buses and this issue pops up again, I'll toss a 
README.contributers into the contrib directory which clearly explains the 
requirements for plugins to be added to the contrib package.  It'll have 
the above requirements in addition some niceties that I want in the 
plugins to make it easier for users to install, configure, and use 
plugins.

I'll try to get that done this week, too.

/will