From: Artem Mygaiev <Artem_Mygaiev@epam.com>
To: "lars.kurth@citrix.com" <lars.kurth@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "committers@xenproject.org" <committers@xenproject.org>
Subject: Re: [Xen-devel] [RFC] Documentation formats, licenses and file system structure
Date: Fri, 11 Oct 2019 10:49:29 +0000 [thread overview]
Message-ID: <ca381fbbfde3447ca5b2ce2033efb8b733c52ccd.camel@epam.com> (raw)
In-Reply-To: <F3EDAC03-A573-4E60-8D0C-8D84949E796B@citrix.com>
Hi Lars
On Thu, 2019-10-10 at 12:34 +0000, Lars Kurth wrote:
> * Possibly stuff such as
> https://urldefense.com/v3/__https://xenbits.xen.org/docs/unstable/support-matrix.html__;!K6dmGCEab4ueJg!lwAwYJi7cUkbX7CUXnOD9i7laj_9xcyafF714u6PO04tu0CYUKDHWBHAy2XD0mvEiA$
> (which is currently GPL-2,
> but we could relicense to say GPL-2 and CC-BY-4 if we had to)
> The implication is that the sphinx docs would not be fully CC-BY-4,
> but the bulk of the pages would be
>
> * Would we ever include API docs generated from GPLv2 code? E.g. for
> safety use-cases?
> @Stefano, @Artem: I guess this one is for you.
> I suppose if we would have a similar issue for a safety manual
> I am also assuming we would want to use sphinx docs and rst to
> generate a future safety manual
>
Yes, I think we will have to use some API docs in safety related
documentation. But I do not see any issue with that because using
"description" part of headers in documentation can be treated as "fair
use" and thus will not create a license conflict as confirmed in
https://www.gnu.org/licenses/gpl-faq.en.html#SourceCodeInDocumentation
-- Artem
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-10-11 10:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 12:34 [Xen-devel] [RFC] Documentation formats, licenses and file system structure Lars Kurth
2019-10-10 17:05 ` Andrew Cooper
2019-10-10 18:30 ` Lars Kurth
2019-10-11 1:24 ` Stefano Stabellini
2019-10-11 11:09 ` Lars Kurth
2019-10-11 17:33 ` Stefano Stabellini
2019-10-15 1:56 ` P S
2019-10-15 1:58 ` Rich Persaud
2019-10-15 12:25 ` Lars Kurth
2019-10-16 16:34 ` Rich Persaud
2019-10-17 13:24 ` Lars Kurth
2019-10-17 16:32 ` Stefano Stabellini
2019-10-17 16:41 ` Rich Persaud
2019-10-17 16:53 ` Stefano Stabellini
2019-10-17 17:05 ` Rich Persaud
2019-10-17 17:30 ` Lars Kurth
2019-10-21 12:54 ` Artem Mygaiev
2019-11-07 19:26 ` Lars Kurth
2019-11-08 18:55 ` Stefano Stabellini
2019-10-11 8:32 ` Jan Beulich
2019-10-11 12:25 ` Lars Kurth
2019-10-11 17:28 ` Stefano Stabellini
2019-10-11 10:49 ` Artem Mygaiev [this message]
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=ca381fbbfde3447ca5b2ce2033efb8b733c52ccd.camel@epam.com \
--to=artem_mygaiev@epam.com \
--cc=committers@xenproject.org \
--cc=lars.kurth@citrix.com \
--cc=xen-devel@lists.xenproject.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.