linux-kernel - Re: [PATCH v2] docs: Convert the Speakup guide to rst

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <875yyxbenm.fsf@meer.lwn.net>
Date:   Tue, 01 Jun 2021 12:53:01 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Igor Matheus Andrade Torrente <igormtorrente@...il.com>,
        gregkh@...uxfoundation.org, samuel.thibault@...-lyon.org,
        grandmaster@...klimov.de, rdunlap@...radead.org
Cc:     Igor Matheus Andrade Torrente <igormtorrente@...il.com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2] docs: Convert the Speakup guide to rst

Igor Matheus Andrade Torrente <igormtorrente@...il.com> writes:

> Modify some parts of the text and add the necessary formatting to leverage
> the rst features. Including links, code-blocks, bullet lists, etc.
>
> Also, adds a table of contents at the beginning and a section to the
> license.
>
> This change helps integrate this documentation to the rest of the rst
> documentation.
>
> Signed-off-by: Igor Matheus Andrade Torrente <igormtorrente@...il.com>

Thanks for doing this work - I'm definitely in favor of it, and if the
RST format works for the intended readers, we want it.

Do please follow through on Jani's comments.

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.  It looks like it entered Documentation/ from staging, through
Greg's [added to CC] tree.  Greg, were you aware of this licensing when
you added this document?

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

Thanks,

jon