What is the acceptable license for documentation files in Zephyr?


Bobby
 

Hello,

I wan´t to partly re-use doumentation from Linux for Zephyr documentation (rst files not source files). Linux documentation is (presumably) GPLv2.

The documentation file header might become:

..
    Copyright (c) 2017 Linux
    Copyright (c) 2017 ...
    SPDX-License-Identifier: GPL-2.0

Is it possible to include such GPLv2 documentation in Zephyr?

Thanks
Bobby


Kinder, David B <david.b.kinder@...>
 

Hi Bobby,

 

There is a process documented here for how to get non Apache-2.0 material into the Zephyr tree. 

 

Best though, would be to avoid inclusion of GPL content (docs or code) into the Zephyr tree.  The nice thing about content is you can write a short summary in the Zephyr docs in your own words, and then include a link to the Linux documents for more details, rather than directly including them.  You could also include short quotes and properly cite the source material with a link to provide due credit to the authors.

 

-- david

 

 

From: zephyr-devel-bounces@... [mailto:zephyr-devel-bounces@...] On Behalf Of b0661
Sent: Friday, November 17, 2017 5:52 AM
To: zephyr-devel@...
Subject: [Zephyr-devel] What is the acceptable license for documentation files in Zephyr?

 

Hello,

I wan´t to partly re-use doumentation from Linux for Zephyr documentation (rst files not source files). Linux documentation is (presumably) GPLv2.

The documentation file header might become:

..
    Copyright (c) 2017 Linux
    Copyright (c) 2017 ...
    SPDX-License-Identifier: GPL-2.0

Is it possible to include such GPLv2 documentation in Zephyr?

Thanks

Bobby


David Brown
 

On Fri, Nov 17, 2017 at 03:36:37PM +0000, Kinder, David B wrote:

Best though, would be to avoid inclusion of GPL content (docs or code) into the
Zephyr tree. The nice thing about content is you can write a short summary in
the Zephyr docs in your own words, and then include a link to the Linux
documents for more details, rather than directly including them. You could
also include short quotes and properly cite the source material with a link to
provide due credit to the authors.
Has anyone tried to figure out what the GPL even would mean for
documentation? Forming a derived work kind of makes sense, but what
about compiling and source code? Would including a chapter of GPL
documentation into a document under another license cause the rest of
the work to be a derived work?

There is a reason the FSF doesn't use the GPL for their documentation.

David