[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC] Documentation formats, licenses and file system structure


  • To: "lars.kurth@xxxxxxxxxx" <lars.kurth@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Artem Mygaiev <Artem_Mygaiev@xxxxxxxx>
  • Date: Fri, 11 Oct 2019 10:49:29 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=epam.com; dmarc=pass action=none header.from=epam.com; dkim=pass header.d=epam.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9mt3fwfRi+pPtLLjlVyDEJF86S6l2IYZ23pGcSf2xjQ=; b=U73hmrWNiPkUu7flRVPaqcBlYY1h2DjqvaGHNtA/MxzN1iDQVgF5pECpmLATi4HnHP07z4JYMQvUdI/vfJb62MsII5kyzCTVUUGMVvVLYN7O8vvJnIeFvg8VcwJ7YE0nfJxKTT30dut6um0cLfxmicJoQSF7//ecH2jArvoIZhTBvFbg0OJTkokZWZYrSuokJ6k1f+0JKj3tgcmlTMmhj7Ys5+ajSRH19DUhSrtG9jqqzeiQuMY36RbZI6nMg8eoIDX6y6BlFJgUKbP7gfoepZQBH6P+PHpIWjthmzdtOaHG+9Zsmq8hk7Ndo241OIDpnU7x9tIJpG54Hdxqphuu2A==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AW1tmbsbnj6xls9rg/8oBBI2ClFzcQ8gTK4eDwl72R6lHnW41/2x3eJlYWUNRqt34Nkf9j8mbGNVqsA/mIYrmC652Y4nJzo1kggbICrxYCgVoPoRZ/jyn6MQ6H9z2vx27brKkMrKmr/FnAme8ldEgrtEhrwORG+9vPqweZVc6d4KG/hL7ZYVRpJ/uThN/I4tCkamIIsEDX+rZA6ap5dGA+C5+cM4hs3HvKvhuYfOaLY+paLGi/zmE+XiEqI+6J/wu5x0uXSrpcojAAv5EtnRpj1ahrNpjVCR91XkgmKu00NuSjgf3VeklnzPIaY/KC+hLM4j1mX4JPxF1SHkUIEqLQ==
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Artem_Mygaiev@xxxxxxxx;
  • Cc: "committers@xxxxxxxxxxxxxx" <committers@xxxxxxxxxxxxxx>
  • Delivery-date: Fri, 11 Oct 2019 10:49:38 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHVf2cRdQE5+PIufEarnRjQ6zCVf6dVRE0A
  • Thread-topic: [RFC] Documentation formats, licenses and file system structure

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@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.