All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Jonathan Corbet <corbet@lwn.net>, collins@gene3.ait.iastate.edu
Cc: Igor Matheus Andrade Torrente <igormtorrente@gmail.com>,
	gregkh@linuxfoundation.org, grandmaster@al2klimov.de,
	rdunlap@infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: Convert the Speakup guide to rst
Date: Wed, 2 Jun 2021 00:06:43 +0200	[thread overview]
Message-ID: <20210601220643.uzep2ju2zlcmpa57@begin> (raw)
In-Reply-To: <875yyxbenm.fsf@meer.lwn.net>

Jonathan Corbet, le mar. 01 juin 2021 12:53:01 -0600, a ecrit:
> I am concerned about one thing, though: the licensing of this document
> is not GPL-compatible, which means we can't build it into the rest of
> the docs.

? I see various GFDL-1.1-no-invariants-or-later documentation in
userspace-api/media notably, do they have such build restriction? What
is actually posing problem in the GFDL licence?

> What are the chances that we can get the authors to agree on a change to
> a GPL-compatible license for this file?

I don't know about Collins' opinion on this, Cc-ing him with the latest
mail my archives know for him (which dates 2008...)

The copyright "the Speakup Team" is a more complex thing to look for.

Samuel

  reply	other threads:[~2021-06-01 22:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 21:57 [PATCH v2] docs: Convert the Speakup guide to rst Igor Matheus Andrade Torrente
2021-05-31 22:07 ` Samuel Thibault
2021-05-31 22:40   ` Chime Hart
2021-05-31 22:42   ` Didier Spaier
2021-05-31 22:44     ` Samuel Thibault
2021-05-31 22:54       ` Samuel Thibault
     [not found]     ` <648b7668-1aa8-dc1d-c92e-7dfc8d3270a7@slint.fr>
2021-05-31 23:03       ` Didier Spaier
2021-06-01  2:11     ` Chris Brannon
2021-05-31 23:15   ` Gregory Nowak
2021-05-31 23:19     ` Samuel Thibault
2021-05-31 23:29     ` Didier Spaier
2021-05-31 23:39       ` Samuel Thibault
2021-05-31 23:31   ` Alexander Epaneshnikov
2021-06-01  4:17   ` Tom Fowle
2021-06-01 15:39   ` Igor Torrente
2021-06-01 21:55     ` Samuel Thibault
2021-06-01 23:32       ` Igor Torrente
2021-06-02 12:27         ` Jani Nikula
2021-06-02 13:38           ` Igor Torrente
2021-06-01 11:28 ` [PATCH v2] " Jani Nikula
2021-06-01 15:11   ` Igor Torrente
2021-06-01 15:51     ` Jani Nikula
2021-06-01 21:58       ` Samuel Thibault
2021-06-01 21:57     ` Samuel Thibault
2021-06-01 23:43       ` Igor Torrente
2021-06-01 18:53 ` Jonathan Corbet
2021-06-01 22:06   ` Samuel Thibault [this message]
2021-06-01 22:18     ` Jonathan Corbet
2021-06-01 22:37       ` Samuel Thibault
2021-06-01 22:44         ` Samuel Thibault
2021-06-01 22:45           ` Samuel Thibault
2021-06-01 22:48             ` Samuel Thibault
2021-06-02  0:54               ` Kirk Reiser
2021-06-02  0:55                 ` Kirk Reiser
2021-06-01 22:47         ` Jonathan Corbet
2021-06-02  6:47           ` Samuel Thibault
2021-06-02  2:54         ` Chris Brannon
2021-06-02  6:46           ` Samuel Thibault
2021-06-04 13:21       ` Greg KH

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=20210601220643.uzep2ju2zlcmpa57@begin \
    --to=samuel.thibault@ens-lyon.org \
    --cc=collins@gene3.ait.iastate.edu \
    --cc=corbet@lwn.net \
    --cc=grandmaster@al2klimov.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=igormtorrente@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@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 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.