From 74b4760aa81222de32147e16fa7605ce55db9922 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sat, 21 Sep 2019 13:58:09 +0200 Subject: DOCS/contribute.md: license clarifications Basically, both the license of the file and the preferred license of the project (LGPLv2.1+) counts. I'm doing that so that files with more liberal licenses don't get infected by LGPL, but allow copy & pasting to LGPL source files without jumping through lawyer bullshit hoops. Mention this in Copyright too. --- DOCS/contribute.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'DOCS') diff --git a/DOCS/contribute.md b/DOCS/contribute.md index a11b2982a8..5f514b06d6 100644 --- a/DOCS/contribute.md +++ b/DOCS/contribute.md @@ -17,10 +17,14 @@ Sending patches - All new code must be LGPLv2.1+ licensed, or come with the implicit agreement that it will be relicensed to LGPLv2.1+ later (see ``Copyright`` in the repository root directory). + Changes in files with more liberal licenses (such as BSD, MIT, or ISC) are + assumed to be dual-licensed under LGPLv2.1+ and the license indicated in the + file header. - You must be either the exclusive author of the patch, or acknowledge all authors involved in the commit message. If you take 3rd party code, authorship and copyright must be properly acknowledged. If the license of the code is not LGPLv2.1+, this must be mentioned. +- These license statements are legally binding. - Don't use fake names (something that looks like an actual names, and may be someone else's name, but is not your legal name). Using a pseudonyms is allowed if it can be used to identify or contact you, even if whatever -- cgit v1.2.3