From 47940ed1e0c149a3993828171803fa6b589670db Mon Sep 17 00:00:00 2001 From: dragonmux Date: Sat, 27 Aug 2022 23:15:04 +0100 Subject: [PATCH] misc: Added advice on how contribution licensing should be done and works --- CONTRIBUTING.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d7f0501..cf7ff33 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -66,3 +66,16 @@ to dip into the commit descriptions as this improves the general Git experience Try to keep commits focused on a single small and atomic change to ease review, and aid the process if we end up having to `git bisect` through your changes, or `git revert` in the extreme case something seriously broke. We use rebasing to merge pull requests, so please keep this in mind. + +## Licensing + +When making contributions to existing code, we ask that you update the copyright and authorship notice at +the top with any authorship information you wish to provide. This is so you get proper attribution. +The contribution must be made under the existing code's license terms as stated per file. + +When making original contributions as new files to the project, this presents a choice on licensing. +Historically the project uses GPLv3+, however contributions have been made using compatible licensing such +as MIT and BSD-3-Clause. We would ask that you preferentially choose between GPLv3+ and BSD-3-Clause. + +Keep in mind that the resulting binary is GPLv3+ licensed due to how the license is worded, but the individual +contributions retain their source licensing when considering re-use in other projects.