Derived Works: how much change info should the license require?
Im not an expert on licensing but it seems different licenses require amounts of notification to the user when the software is modified.
For example, copying a setion from the GPL:
'a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.'
this seems to say to me that you should embed in the files something like:
LOOK AT THIS!!!!: FILE CHANGE on 10/24/2021
while the Python Software Foundation License states this:
'3. In the event Licensee prepares a derivative work that is based on or incorporates Python 2.1.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 2.1.1.'
Which to me seems to require a notification like:
1. Changed ints so they will now be doubles.
2. Changed synchronized keyword to lockthis
3. Added bytecode called invokedynamite
I could be reading these licenses wrong but they do seem to be different points on the spectrum of what should be required.
For myself I think Id like a detailed requirement of what has changed. If I download someones altered JVM Id like an opportunity to take in all that is different before sending it on its merry way on the command line.
So what about it, which would you feel more comfortable with?