cvs commit: fptools/libraries/base LICENSE

Ross Paterson ross@soi.city.ac.uk
Sat, 22 Jun 2002 15:54:43 +0100


On Fri, Jun 21, 2002 at 12:21:00PM +0100, Alastair Reid wrote:
> The most extreme case of many independent open source projects being
> distributed as one is the GPL-licensed Utah OSKit which contains code
> from Linux, FreeBSD, Mach and many other sources
> 
>    http://www.cs.utah.edu/flux/oskit/
> 
> The documentation
> 
>   http://www.cs.utah.edu/flux/oskit/html/oskit-wwwpa6.html#x64-3338000VI
> 
> contains all the individual copyrights and licenses at the end of the
> documentation.  As I understand it, this was all put at the end to
> keep it out of the way.  The Acknowledgements section says a little
> about this.
> 
> License information is also kept in the relevant subdirectory in the
> source tree.

Right: the documentation includes a summary of the copyright and licencing
information that is given precisely elsewhere, closer to the source code.

In the Haskell libraries, there is no clear indication of the licencing
of each individual module.  (There's a pointer to a file that contains
4 BSD-like licences now, maybe 20 next year.)  No problem for people
who use the library as a whole, but it will be for people who want to
extract some modules and modify them for their own purposes.  At the
least we need to name the licences and mention the name in the License
field of the module header.  It would be a little bit of work now,
but it would be simple for new modules to follow.