All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Rename VERBATIM license (was: Re: [RFC v3 8/9] Many pages: [Verbatim-man-pages] Use SPDX markings)
Date: Wed, 8 Sep 2021 10:22:09 +0200	[thread overview]
Message-ID: <8b513d06-3e9e-3d2f-6217-07bf2fa3765c@gmail.com> (raw)
In-Reply-To: <20210908043502.xcmj6yoxrneokwl5@localhost.localdomain>

Hi, Branden, and Michael!

On 9/8/21 6:35 AM, G. Branden Robinson wrote:
> Hi, Alex!
> 
> I'd like to request a different choice of name for the SPDX license tag
> used by the man-pages documents affected by this change.  It's my
> understanding that there is freedom to make such a choice because the
> proposed tag does not yet appear in the SPDX license list[1].
> 
> I have a few reasons: (1) the license tag says "Verbatim" which implies
> to me that permission to modify the document is excluded--but it is not;

Completely agree!

I never understood why it was called Verbatim, and I even thought that 
my understanding of the concept "verbatim" was wrong, because it 
contradicted the license contents.  I had to re-read it (and google 
"verbatim") many times to arrive to the conclusion that the naming and 
the contents simply don't match.

> (2) with the exception of the paragraph about the kernel and system
> libraries being in flux, this license appears identical to what I (and
> some folks in Debian) started terming the "traditional GNU documentation
> license) about 18 years ago when debate over the GNU FDL was raging[2];
> this was in fact the license the GNU project used for most of its
> documentation before it promulgated the FDL.  As far as I know, this
> license text has no earlier provenance; I would appreciate correction on
> this point.  Thirdly, since that time, the GNU project has christened
> the license terms for many of its web pages the "GNU Verbatim Copying
> License"[3].  You can perhaps see how this might generate confusion.
> 
> Because the warranty-disclaiming third paragraph about the Linux kernel
> is unique to the Linux man-pages project and the term "verbatim" implies
> too much restriction in my view, I envision a few alternatives.
> 
> man-pages-doc
> man-pages-document-copyleft
> man-pages-copyleft
> 
> Any of the above could be further prefixed with "Linux-" to reinforce
> the specificity to this project, of course.  If pressed for a
> preference, I reckon I would pick "Linux-man-pages-copyleft".

I like that name.  Less historical, but more precise.  Michael?

Acked-by: Alejandro Colomar <alx.manpages@gmail.com>

I don't know if the Linux man-pages license has made it into other man 
pages, in which case, I would omit the "Linux-" prefix for 
compatibility.  I guess BSD man pages use the BSD license.

The identifier "Verbatim-man-pages" is already in SPDX, but it is yet 
unreleased.  They talked about releasing soon, so could you please jump 
in there and propose that change to SPDX?:
<https://github.com/spdx/license-list-XML/issues/1310#issuecomment-911876593>


BTW, does the "traditional GNU documentation license" have an SPDX 
identifier?

> 
> I feel that the "VERBATIM" string is similarly misleading, but it's not
> presented as an SPDX license tag, and I see that its use is already
> well-entrenched.  I expected to find something like a sed script in the
> man-pages scripts/ directory that manipulated lines matching
> '%%%LICENSE_START(' but failed to.  Perhaps a convenient new moniker
> could be adopted to supersede "VERBATIM" in this context, once the SPDX
> tagging initiative is complete?

The SPDX license text doesn't contain the LICENSE_START and LICENSE_END 
lines, so if we change the name, there will be no traces of VERBATIM 
(apart from the git history, that is).

Cheers,

Alex

> 
> Regards,
> Branden


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-09-08  8:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05 13:25 [RFC v3 0/9] Use SPDX markings Alejandro Colomar
2021-09-05 13:25 ` [RFC v3 1/9] LICENSES/GPL-1.0-or-later.txt, many pages: " Alejandro Colomar
2021-09-05 21:53   ` Richard Fontana
2021-09-08  9:23     ` Alejandro Colomar (man-pages)
2021-09-05 13:25 ` [RFC v3 2/9] LICENSES/GPL-2.0-or-later.txt: Add license text Alejandro Colomar
2021-09-05 13:25 ` [RFC v3 3/9] Many pages: [GPL-2.0-or-later] Use SPDX markings Alejandro Colomar
2021-09-05 21:21   ` Richard Fontana
2021-09-05 21:42     ` Alejandro Colomar (man-pages)
2021-09-05 13:25 ` [RFC v3 4/9] " Alejandro Colomar
2021-09-05 13:25 ` [RFC v3 5/9] " Alejandro Colomar
2021-09-05 13:25 ` [RFC v3 6/9] " Alejandro Colomar
2021-09-05 13:25 ` [RFC v3 7/9] " Alejandro Colomar
2021-09-05 13:25 ` [RFC v3 8/9] Many pages: [Verbatim-man-pages] " Alejandro Colomar
2021-09-08  4:35   ` G. Branden Robinson
2021-09-08  8:22     ` Alejandro Colomar (man-pages) [this message]
2021-09-26  6:03       ` Rename VERBATIM license (was: Re: [RFC v3 8/9] Many pages: [Verbatim-man-pages] Use SPDX markings) G. Branden Robinson
2021-09-05 13:25 ` [RFC v3 9/9] Many pages: [Verbatim-man-pages] Use SPDX markings 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=8b513d06-3e9e-3d2f-6217-07bf2fa3765c@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.