Well, this debate is in the archives, but I will attempt to explain again: The included files are patch files, not source files. I don't think there will be confusion that the patch files are copies of the source and that folks will attempt to modify the patch files in order modify future releases of CreateJS itself.
AIUI, folks creating a derivative work get to own the derivative work. The patch file describes the derivation. If it mattered that words from originally written by someone else ending up in your derivation meant that you didn't own the derivation, then it would be a pretty sad world in open source. It would mean that most folks wouldn't own patches they think they own, since it is hard to contribute small changes without mentioning words already in the source code. In sum, this is not source, so [1] does not apply. Thanks, -Alex On 9/6/16, 12:54 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >> I don't quite understand, why we have to remove the old header anyway >>... shouldn't it be possible to add the Apache header (would sort of be >>both in there) ... the Patch file itself should have an Apache Header, I >>think. But the resulting file shouldn't have the old header removed. > >Exactly as the policy here [1] > >Thanks, >Justin > >1. http://www.apache.org/legal/src-headers.html#3party
