[LTP] [RFC] Reduce LICENCE/COPYING files

Enji Cooper yaneurabeya@gmail.com
Fri Jun 4 19:47:30 CEST 2021


I’d actually exercise some caution here. If there was a top-level LICENSE file that was distributed, that would be awesome, but if people take bits and pieces of subprojects and hack it in elsewhere without there being appropriate attributions to the original authors and such, you could get into serious legal trouble.

Doing the “right thing” requires getting all authors’ sign-off in order to change licensing information and such. The FreeBSD project for instance has had to hop through a lot of hoops to change code from BSD 3-clause to 2-clause because some of the authors didn’t sign over the code to the project when contributing it, since the concern with signing off on code and such predated the code contribution.

Unless there’s a real need for consolidating the LICENSE files, I’d leave it well enough alone in the source tree and just aggregate all of the licenses as an uber license and distribute it with the binary packages.

That’s just my 2 cents,
-Enji
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210604/461ce00b/attachment.sig>


More information about the ltp mailing list