public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: linux-man@vger.kernel.org, Martin Schulze <joey@infodrom.org>
Cc: Andi Kleen <ak@linux.intel.com>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Adam Dobes <adobes@redhat.com>, Chris Lameter <cl@linux.com>
Subject: Re: SPDX license review requests
Date: Sat, 8 Jul 2023 18:44:43 +0200	[thread overview]
Message-ID: <978e3f22-8017-eb91-0737-9a043c335122@gmail.com> (raw)
In-Reply-To: <e8f9685b-ef42-6d0f-c18e-861a26922f6e@Shaw.ca>


[-- Attachment #1.1: Type: text/plain, Size: 3435 bytes --]

[Add Martin Schulze, as he holds copyright of dir_colors.5.]

On 6/29/23 19:01, Brian Inglis wrote:
> On 2023-06-29 10:01, Lameter, Christopher wrote:
>> On Thu, 29 Jun 2023, Lukas Javorsky wrote:
>>>       >> VERBATIM_TWO_PARA
>>>       >>      This license was first used in the Linux man-pages in 
>>> version
>>>       >>      3.07 (year 2008) in a single page:
>>>       >>
>>>       >>              move_pages.2
>>>       >>                      Added by Michael Kerrisk 
>>> <mtk.manpages@gmail.com>,
>>>       >>                      but Copyright (C) 2006 Silicon 
>>> Graphics, Inc.
>>>       >>                                        Christoph Lameter
>>>       >>
>>>       >>      It was later reused in another page:
>> The manpage was written by me and later edited by Michael as far as I 
>> remember.
>>>       >>
>>>       >>              migrate_pages.2
>>>       >>                      Copyright 2009 Intel Corporation
>>>       >> .\"                Author: Andi Kleen
>>>       >> .\" Based on the move_pages manpage which was
>>>       >> .\" This manpage is Copyright (C) 2006 Silicon Graphics, Inc.
>>>       >> .\"                               Christoph Lameter
>>>       >>
>>>       >>      This license is the one considered non-free by Fedora, 
>>> and which
>>>       >>      we need to drop.  Luckily it's only two pages, so they 
>>> could be
>>>       >>      reasonably rewritten in a worst case.
>> The licensing was GPL and not a proprietary one.
>>>       So, given this, if you give consent to change your pages to use
>>>       Linux-man-pages-copyleft, I'll do so provided for the pages 
>>> that are
>>>       completely yours, and will keep in mind that when others agree, 
>>> I'll also
>>>       change the pages that are shared.
>> I have no objections.
> 
> Updating these licences are really nice to haves for this project.
> 
> Just to be clear, the FSF and Fedora issue is only with *dir_colors*(5) 
> licensed under *LDPv1* which contains the contentious clause:
> 
>      "c) You must not add notes to the Document implying that the reader 
> had better read something produced using Texinfo."
> 
>      https://gitlab.com/fedora/legal/fedora-license-data/-/issues/211
> 
>      https://github.com/spdx/license-list-XML/issues/1957
> 
> which restricts modification, especially by GNU or other projects which 
> may wish to offer and promote alternative doc formats or interfaces.
> 
> LDPv2 requires notifying the author of modifications by email if 
> provided, and suggested authors could add a generic clause c) 
> prohibiting modifications without author consent.
> 
> TLDP is now by default under GFDLv1.2+.
> 
> Another problematic licence is *JSON*, which contains the clause:
> 
>      "The Software shall be used for Good, not Evil."
> 
> restricting use with non-specific subjective terms, unlike similar 
> licences with specific objective restrictions, like not being used for 
> anything related to animal testing or nuclear weapons.
> 

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-07-08 16:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 12:38 SPDX license review requests Adam Dobes
2023-05-25 22:56 ` Alejandro Colomar
2023-05-25 23:03   ` Alejandro Colomar
2023-05-26 11:46     ` Alejandro Colomar
2023-05-30 12:47       ` Andi Kleen
     [not found]         ` <eda85fda-6182-fc13-3943-9084b187433e@gmail.com>
     [not found]           ` <CAK719L2PjTr=-c_AEi89TVrJV7DHwyfBJjH6z6Bozc0Rk+rOfQ@mail.gmail.com>
2023-06-29 16:01             ` Lameter, Christopher
2023-06-29 17:01               ` Brian Inglis
2023-07-08 16:44                 ` Alejandro Colomar [this message]
2023-07-08 20:14                   ` Joey Schulze
2023-07-15 13:50                     ` Alejandro Colomar
2023-07-15 19:04                       ` Joey Schulze
2023-07-16  1:11                         ` Alejandro Colomar
2023-09-25 23:08               ` Alejandro Colomar
2023-05-26 11:58   ` Alejandro Colomar
2023-05-26 12:00     ` Alejandro Colomar
2023-05-26 13:15   ` G. Branden Robinson
2023-05-26 14:10     ` Alejandro Colomar
2023-05-26 14:37       ` G. Branden Robinson
2023-05-26 23:17         ` Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=978e3f22-8017-eb91-0737-9a043c335122@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=adobes@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cl@linux.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=joey@infodrom.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox