Lucifers,
I'm about to release an open-source project that uses Charmonizer as build
system. When thinking about the legal implications, a few questions popped up.
A project using on Charmonizer typically ships the following files containing
source code copied verbatim or derived from the Charmonizer source:
* charmonizer.c which contains various Charmonizer source files
* configure scripts for POSIX and Windows shells
* regen_charmonizer.pl
Obviously I have to add a copy of the Apache License, Version 2.0. Since
Charmonizer also has a NOTICE file, any project using Charmonizer "must
include a readable copy of the attribution notices contained within such
NOTICE file" (ALv2, clause 4d). I have the choice to put the relevant contents
of the NOTICE file in a couple of places:
* within my own NOTICE file
* within the Source form or documentation
I think an easy and fool-proof solution would be to
* make regen_charmonizer.pl add the contents of NOTICE to
charmonizer.c automatically.
* release the configure scripts and regen_charmonizer.pl into
public domain or under an extremely permissive license that
doesn't require any attribution. These files contain just a bit
of mostly trivial code.
This way, the only requirement would be to ship a copy of the ALv2.
I also think that the NOTICE files of Lucy and Clownfish should mention
Charmonizer. See
http://www.apache.org/dev/licensing-howto.html#alv2-dep
Nick
