On 12/14/2017 04:49 PM, Matthew Wilcox wrote:
>
> I've written a couple of thousand words of documentation for the XArray.
> I need to decide how to license it. There are no SPDX tags in Documentation/
> to date, so I have no examples to crib from.
>
> 1. How does one add an SPDX tag to an rst f
On Thu, 14 Dec 2017, Matthew Wilcox wrote:
> 1. How does one add an SPDX tag to an rst file?
Do we want the SPDX tags visible in the generated documentation or not?
If not, you have to put it in an rst comment:
.. SPDX-License-Identifier: GPL-2.0
If yes, I'd go for using bibliographic data fie
I've written a couple of thousand words of documentation for the XArray.
I need to decide how to license it. There are no SPDX tags in Documentation/
to date, so I have no examples to crib from.
1. How does one add an SPDX tag to an rst file?
2. What license should I use? I'd like people to be
se to clearly indicate
> the documentation license somewhere in the rendered docs?
The documentation is a part of the kernel as a whole, and much of it is
generated directly from (and is thus a derived product of) overtly
GPLv2-licensed source. So yes, GPLv2 is the license to assume for kernel
mentation is "GNU GPLv2 unless otherwise
> indicated?" And if that's not the case (because I'm not sure GPLv2 is a sane
> license for documentation), would it make sense to clearly indicate the
> documentation license somewhere in the rendered docs?
Given that there
se I'm not sure GPLv2 is a
sane license for documentation), would it make sense to clearly indicate
the documentation license somewhere in the rendered docs?
Best,
Konstantin
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to
