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
Cc: Brian Inglis <Brian.Inglis@Shaw.ca>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andi Kleen <ak@linux.intel.com>,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Adam Dobes <adobes@redhat.com>
Subject: Re: SPDX license review requests
Date: Fri, 26 May 2023 13:58:10 +0200	[thread overview]
Message-ID: <fdb702c8-1411-f143-8932-c18722511b19@gmail.com> (raw)
In-Reply-To: <bd1a81d0-456a-bc19-7df0-fdbcc2a51395@gmail.com>


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

On 5/26/23 00:56, Alejandro Colomar wrote:
[...]

> Also, Linux-man-pages-copyleft seems to contain a sentence that
> makes it differ from VERBATIM_PROF:
> 
> """
>   The author(s) may
> not have taken the same level of care in the production of this
> manual, which is licensed free of charge, as they might when working
> professionally.
> """
> 
> I believe the quality of non-professional code and manuals to be
> at least as high as the professional one.  We have more freedom to
> reject crap.  I propose also deprecating Linux-man-pages-copyleft
> and moving to VERBATIM_PROF as the single surviving license from
> all four variants.

I reconsidered.  The non-pro version does actually reflect reality,
as it doesn't say the level of care is less, but just different.
That can --and more often than not does-- mean higher level of care.

So, I prefer Linux-man-pages-copyleft over VERBATIM_PROF.

<https://github.com/spdx/license-list-XML/issues/1959#issuecomment-1564255785>

> 
> We're also discussing the names that each of these four should be
> given in SPDX.
> 
> 
> I suggest (in order of appearance in this email):
> 
> -  Linux-man-pages-copyleft to be renamed to the following, and
>    mark it as a deprecated license.
> 
> 	Linux-man-pages-copyleft-nopro
> 	Linux man-pages Copyleft (non-professional)

I drop my suggestion of renaming this one (and of deprecating it).

> 
> -  VERBATIM_PROF to be SPDX'd as:
> 
> 	Linux-man-pages-copyleft-qual
> 	Linux man-pages Copyleft (high quality)
> 
> -  VERBATIM_TWO_PARA to be SPDX'd as:
> 
> 	Linux-man-pages-copyleft-notrans
> 	Linux man-pages Copyleft (no translations)
> 
> -  VERBATIM_ONE_PARA to be SPDX'd as:
> 
> 	Linux-man-pages-copyleft-verbatim
> 	Linux man-pages Copyleft (verbatim)
> 
> 

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

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

  parent reply	other threads:[~2023-05-26 11:58 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
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 [this message]
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=fdb702c8-1411-f143-8932-c18722511b19@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=Brian.Inglis@Shaw.ca \
    --cc=adobes@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=g.branden.robinson@gmail.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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