Skip to contentSkip to conversation

Documentation: clarify driver licensing rules

PATCH Applied Dave Hansen 4 participants 4 messages Aug 14, 2020 – Aug 31, 2020

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 Documentation: clarify driver licensing rules

From: Dave Hansen <[email protected]>

Greg has challenged some recent driver submitters on their license choices. He was correct to do so, as the choices in these instances did not always advance the aims of the submitters.

But, this left submitters (and the folks who help them pick licenses) a bit confused. They have read things like Documentation/process/license-rules.rst which says:

individual source files can have a different license which is required to be compatible with the GPL-2.0

and Documentation/process/submitting-drivers.rst:

We don't insist on any kind of exclusive GPL licensing, and if you wish ... you may well wish to release under multiple licenses.

As written, these appear a _bit_ more laissez faire than we've been in practice lately. It sounds like we at least expect submitters to make a well-reasoned license choice and to explain their rationale. It does not appear that we blindly accept anything that is simply GPLv2-compatible.

Drivers appear to be the most acute source of misunderstanding, so fix the driver documentation first. Update it to clarify expectations.

Cc Dan Williams <[email protected]>
Cc H. Peter Anvin <[email protected]>
Cc Thomas Gleixner <[email protected]>
Cc Greg Kroah-Hartman <[email protected]>
Cc Jonathan Corbet <[email protected]>

--

Changes from v1:
* Remove mention of maintainers enforcing particular license choices.
* Change the wording to ensure that folks understand that the trigger that requires an explanation is not multiple licenses per se, but non-GPL licenses. You could argue that GPLv2-or-later is multiple liceses, for instance.
---

 b/Documentation/process/submitting-drivers.rst |    9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)
Documentation/process/submitting-drivers.rst renamed from Documentation/process/submitting-drivers.rst~clarify-dual-licensing +5 -4
diff -puN Documentation/process/submitting-drivers.rst~clarify-dual-licensing Documentation/process/submitting-drivers.rst
@@ -60,10 +60,11 @@ What Criteria Determine Acceptance
 
 Licensing:
 		The code must be released to us under the
-		GNU General Public License. We don't insist on any kind
-		of exclusive GPL licensing, and if you wish the driver
-		to be useful to other communities such as BSD you may well
-		wish to release under multiple licenses.
+		GNU General Public License. If you wish the driver to be
+		useful to other communities such as BSD you may release
+		under multiple licenses. If you choose to release under
+		licenses other than the GPL, you should include your
+		rationale for your license choices in your cover letter.
 		See accepted licenses at include/linux/module.h
 
 Copyright:

_

maintainer Reviewed-by on v2 1/1
#1 lore raw
Quoted 72 lines · Dave Hansen

From: Dave Hansen <[email protected]>

Greg has challenged some recent driver submitters on their license choices. He was correct to do so, as the choices in these instances did not always advance the aims of the submitters.

But, this left submitters (and the folks who help them pick licenses) a bit confused. They have read things like Documentation/process/license-rules.rst which says:

individual source files can have a different license which is required to be compatible with the GPL-2.0

and Documentation/process/submitting-drivers.rst:

We don't insist on any kind of exclusive GPL licensing, and if you wish ... you may well wish to release under multiple licenses.

As written, these appear a _bit_ more laissez faire than we've been in practice lately. It sounds like we at least expect submitters to make a well-reasoned license choice and to explain their rationale. It does not appear that we blindly accept anything that is simply GPLv2-compatible.

Drivers appear to be the most acute source of misunderstanding, so fix the driver documentation first. Update it to clarify expectations.

Cc Dan Williams <[email protected]>
Cc H. Peter Anvin <[email protected]>
Cc Thomas Gleixner <[email protected]>
Cc Greg Kroah-Hartman <[email protected]>
Cc Jonathan Corbet <[email protected]>

--

Changes from v1:
* Remove mention of maintainers enforcing particular license choices.
* Change the wording to ensure that folks understand that the trigger that requires an explanation is not multiple licenses per se, but non-GPL licenses. You could argue that GPLv2-or-later is multiple liceses, for instance.
---

 b/Documentation/process/submitting-drivers.rst |    9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff -puN Documentation/process/submitting-drivers.rst~clarify-dual-licensing Documentation/process/submitting-drivers.rst

Documentation/process/submitting-drivers.rst renamed from Documentation/process/submitting-drivers.rst~clarify-dual-licensing +5 -4
@@ -60,10 +60,11 @@ What Criteria Determine Acceptance
 
 Licensing:
 		The code must be released to us under the
-		GNU General Public License. We don't insist on any kind
-		of exclusive GPL licensing, and if you wish the driver
-		to be useful to other communities such as BSD you may well
-		wish to release under multiple licenses.
+		GNU General Public License. If you wish the driver to be
+		useful to other communities such as BSD you may release
+		under multiple licenses. If you choose to release under
+		licenses other than the GPL, you should include your
+		rationale for your license choices in your cover letter.
 		See accepted licenses at include/linux/module.h
 
 Copyright:
Quoted 1 line

_

Looks good, thanks for the modifications:

maintainer Applied
#2 lore raw
In reply to Dave Hansen
Quoted 17 lines · On Fri, 14 Aug 2020 07:56:25 -0700 Dave Hansen <[email protected]>…

Greg has challenged some recent driver submitters on their license choices. He was correct to do so, as the choices in these instances did not always advance the aims of the submitters.

But, this left submitters (and the folks who help them pick licenses) a bit confused. They have read things like Documentation/process/license-rules.rst which says:

individual source files can have a different license which is required to be compatible with the GPL-2.0

and Documentation/process/submitting-drivers.rst:

We don't insist on any kind of exclusive GPL licensing, and if you wish ... you may well wish to release under multiple licenses.

Quoted 8 lines

As written, these appear a _bit_ more laissez faire than we've been in practice lately. It sounds like we at least expect submitters to make a well-reasoned license choice and to explain their rationale. It does not appear that we blindly accept anything that is simply GPLv2-compatible.

Drivers appear to be the most acute source of misunderstanding, so fix the driver documentation first. Update it to clarify expectations.

Applied, thanks.

jon

#3 lore raw
In reply to Dave Hansen
Quoted 20 lines · Dave Hansen

From: Dave Hansen <[email protected]>

Greg has challenged some recent driver submitters on their license choices. He was correct to do so, as the choices in these instances did not always advance the aims of the submitters.

But, this left submitters (and the folks who help them pick licenses) a bit confused. They have read things like Documentation/process/license-rules.rst which says:

individual source files can have a different license which is required to be compatible with the GPL-2.0

and Documentation/process/submitting-drivers.rst:

We don't insist on any kind of exclusive GPL licensing, and if you wish ... you may well wish to release under multiple licenses.

Quoted 9 lines

As written, these appear a _bit_ more laissez faire than we've been in practice lately. It sounds like we at least expect submitters to make a well-reasoned license choice and to explain their rationale. It does not appear that we blindly accept anything that is simply GPLv2-compatible.

Drivers appear to be the most acute source of misunderstanding, so fix the driver documentation first. Update it to clarify expectations.

Well written! Retroactive Ack from me :)

-hpa