linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH resend] README: clarify redistribution requirements covering patents
@ 2015-05-14 17:56 Luis R. Rodriguez
  2015-05-14 18:29 ` Arend van Spriel
  0 siblings, 1 reply; 4+ messages in thread
From: Luis R. Rodriguez @ 2015-05-14 17:56 UTC (permalink / raw)
  To: kyle, linux-firmware
  Cc: netdev, linux-wireless, linux-kernel, gnomes, Luis R. Rodriguez

From: "Luis R. Rodriguez" <mcgrof@suse.com>

Firmware licenses on linux-firmware should include an implicit
or explicit patent grant to end users for full device operation
otherwise it would start making linux-firmware useless for many
Linux distributions which have positions against patent encumbered
software [0] [1] [2] and it would mean cherry picking firmware files
out. It can also mean making it problematic to redistribute linux-firmware
in some jurisdictions which could have different positions on
patents, or have already outlawed software patents.

Licenses with implicit patent grants are allowed given that otherwise
we couldn't carry permissively licensed firmwares which would be silly,
but using permissively licensed firmware files which remove patent
grants explicitly are not allowed.

A clarifications is needed as one attempt was already made to include
firmware encumbered by patents without a grant [3] and it was decided
we would not allow these. We clarify this to make this requirement
explicit and prevent these type of further attempts.

[0] https://www.debian.org/legal/patent
[1] http://fedoraproject.org/wiki/Software_Patents#Red_Hat.27s_position_on_Software_Patents
[2] http://www.openinventionnetwork.com/about-us/
[3] https://lkml.org/lkml/2014/3/14/182

Cc: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
---

This patch is unmodified, the discussion over it was brief [0] but I didn't
hear back from Alan on this. Sending again now that we have a new active
linux-firmware maintainer.

[0] https://lkml.org/lkml/2014/6/27/448

 README | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/README b/README
index f2ed92e..d2a56ec 100644
--- a/README
+++ b/README
@@ -18,7 +18,10 @@ and also cc: to related mailing lists.
 
 Your commit should include an update to the WHENCE file clearly
 identifying the licence under which the firmware is available, and
-that it is redistributable. If the licence is long and involved, it's
+that it is redistributable. Being redistributable includes ensuring
+the firmware license provided includes an implicit or explicit
+patent grant to end users to ensure full functionality of device
+operation with the firmware. If the licence is long and involved, it's
 permitted to include it in a separate file and refer to it from the
 WHENCE file.
 And if it were possible, a changelog of the firmware itself.
-- 
2.3.2.209.gd67f9d5.dirty


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH resend] README: clarify redistribution requirements covering patents
  2015-05-14 17:56 [PATCH resend] README: clarify redistribution requirements covering patents Luis R. Rodriguez
@ 2015-05-14 18:29 ` Arend van Spriel
  2015-05-19 20:18   ` Luis R. Rodriguez
  0 siblings, 1 reply; 4+ messages in thread
From: Arend van Spriel @ 2015-05-14 18:29 UTC (permalink / raw)
  To: Luis R. Rodriguez
  Cc: kyle, linux-firmware, netdev, linux-wireless, linux-kernel,
	gnomes, Luis R. Rodriguez

On 05/14/15 19:56, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"<mcgrof@suse.com>
>
> Firmware licenses on linux-firmware should include an implicit
> or explicit patent grant to end users for full device operation
> otherwise it would start making linux-firmware useless for many
> Linux distributions which have positions against patent encumbered
> software [0] [1] [2] and it would mean cherry picking firmware files
> out. It can also mean making it problematic to redistribute linux-firmware
> in some jurisdictions which could have different positions on
> patents, or have already outlawed software patents.
>
> Licenses with implicit patent grants are allowed given that otherwise
> we couldn't carry permissively licensed firmwares which would be silly,
> but using permissively licensed firmware files which remove patent
> grants explicitly are not allowed.
>
> A clarifications is needed as one attempt was already made to include
> firmware encumbered by patents without a grant [3] and it was decided
> we would not allow these. We clarify this to make this requirement
> explicit and prevent these type of further attempts.
>
> [0] https://www.debian.org/legal/patent
> [1] http://fedoraproject.org/wiki/Software_Patents#Red_Hat.27s_position_on_Software_Patents
> [2] http://www.openinventionnetwork.com/about-us/
> [3] https://lkml.org/lkml/2014/3/14/182
>
> Cc: netdev@vger.kernel.org
> Cc: linux-wireless@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Luis R. Rodriguez<mcgrof@suse.com>
> ---
>
> This patch is unmodified, the discussion over it was brief [0] but I didn't
> hear back from Alan on this. Sending again now that we have a new active
> linux-firmware maintainer.
>
> [0] https://lkml.org/lkml/2014/6/27/448
>
>   README | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/README b/README
> index f2ed92e..d2a56ec 100644
> --- a/README
> +++ b/README
> @@ -18,7 +18,10 @@ and also cc: to related mailing lists.
>
>   Your commit should include an update to the WHENCE file clearly
>   identifying the licence under which the firmware is available, and
> -that it is redistributable. If the licence is long and involved, it's
> +that it is redistributable. Being redistributable includes ensuring
> +the firmware license provided includes an implicit or explicit
> +patent grant to end users to ensure full functionality of device
> +operation with the firmware. If the licence is long and involved, it's

Just nitpicking here, but there is 'license' and 'licence' being used 
here. Better stick to one and preferably 'license'.

Regards,
Arend

>   permitted to include it in a separate file and refer to it from the
>   WHENCE file.
>   And if it were possible, a changelog of the firmware itself.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH resend] README: clarify redistribution requirements covering patents
  2015-05-14 18:29 ` Arend van Spriel
@ 2015-05-19 20:18   ` Luis R. Rodriguez
  2015-05-19 21:22     ` Kyle McMartin
  0 siblings, 1 reply; 4+ messages in thread
From: Luis R. Rodriguez @ 2015-05-19 20:18 UTC (permalink / raw)
  To: Arend van Spriel
  Cc: Kyle McMartin, linux-firmware, netdev, linux-wireless,
	linux-kernel, One Thousand Gnomes

On Thu, May 14, 2015 at 11:29 AM, Arend van Spriel <arend@broadcom.com> wrote:
> On 05/14/15 19:56, Luis R. Rodriguez wrote:
>> diff --git a/README b/README
>> index f2ed92e..d2a56ec 100644
>> --- a/README
>> +++ b/README
>> @@ -18,7 +18,10 @@ and also cc: to related mailing lists.
>>
>>   Your commit should include an update to the WHENCE file clearly
>>   identifying the licence under which the firmware is available, and
>> -that it is redistributable. If the licence is long and involved, it's
>> +that it is redistributable. Being redistributable includes ensuring
>> +the firmware license provided includes an implicit or explicit
>> +patent grant to end users to ensure full functionality of device
>> +operation with the firmware. If the licence is long and involved, it's
>
>
> Just nitpicking here, but there is 'license' and 'licence' being used here.
> Better stick to one and preferably 'license'.

Fixed, will submit a v2.

 Luis

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH resend] README: clarify redistribution requirements covering patents
  2015-05-19 20:18   ` Luis R. Rodriguez
@ 2015-05-19 21:22     ` Kyle McMartin
  0 siblings, 0 replies; 4+ messages in thread
From: Kyle McMartin @ 2015-05-19 21:22 UTC (permalink / raw)
  To: Luis R. Rodriguez
  Cc: Arend van Spriel, Kyle McMartin, netdev, linux-wireless,
	linux-kernel, One Thousand Gnomes

On Tue, May 19, 2015 at 01:18:14PM -0700, Luis R. Rodriguez wrote:
> >>   Your commit should include an update to the WHENCE file clearly
> >>   identifying the licence under which the firmware is available, and
> >> -that it is redistributable. If the licence is long and involved, it's
> >> +that it is redistributable. Being redistributable includes ensuring
> >> +the firmware license provided includes an implicit or explicit
> >> +patent grant to end users to ensure full functionality of device
> >> +operation with the firmware. If the licence is long and involved, it's
> >
> >
> > Just nitpicking here, but there is 'license' and 'licence' being used here.
> > Better stick to one and preferably 'license'.
> 
> Fixed, will submit a v2.
> 

Heh, it doesn't help that we now have LICENSE.* and LICENCE.* in the
tree as well. :/ I believe, at least in my Commonwealth english, that
licence is the file, and license is the action of licensing. I should
probably rename the LICENSE.* files in the tree to match.

--Kyle


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-05-19 21:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-14 17:56 [PATCH resend] README: clarify redistribution requirements covering patents Luis R. Rodriguez
2015-05-14 18:29 ` Arend van Spriel
2015-05-19 20:18   ` Luis R. Rodriguez
2015-05-19 21:22     ` Kyle McMartin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).