[copyleft-next] New definition of Corresponding Source

Richard Fontana fontana at sharpeleven.org
Thu Dec 6 02:29:48 UTC 2012


On 12/04/2012 08:30 AM, Bradley M. Kuhn wrote:
> Luis Rodriguez wrote at 17:19 (EST) on Monday:
>>  I personally see a benefit to evolve copyleft-next slowly to enhance
>> copyleft where GPLv2 left off,
[...]
> I suggest that you take merge request in, which will document my reasons
> why I think it should be there in the git log.  Then, when you remove it
> again, you can put your reasons why you're removing it into the git log.

I have now made a significant revision to the definition of
Corresponding Source:

"Corresponding Source" of a Covered Work in Object Code form means (i)
the Source Code of the Covered Work; (ii) all associated interface
definition files; (iii) all scripts, instructions and similar
information that were used to build such Source Code; and (iv) a
list clearly identifying all Separate Works that were used in
building and installing the Covered Work. Corresponding Source must
be machine-readable.


More information about the copyleft-next mailing list