Xen project Mailing List

Thanks for pointing this out: seems I got led astray when I was looking at this earlier and confused CC BY 4 with CC BY SA 4

In any case, we do still need to make a decision on what type of license we want and work backwards from it.

I was assuming the ideal would be a weak or no copyleft license but that should be confirmed by business rep’s on the group

Lars

From: Rich Persaud <persaur@xxxxxxxxx>
Date: Monday, 7 October 2019 at 15:49
To: Lars Kurth <lars.kurth@xxxxxxxxxx>
Cc: "fusa-sig@xxxxxxxxxxxxxxxxxxxx" <fusa-sig@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [FuSa SIG] Proposed agenda items for tomorrow's meeting

Re: CC-BY, http://www.gnu.org/licenses/license-list.en.html#OtherLicenses

"This is a non-copyleft free license that is good for art and entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software."

Rich

On Oct 7, 2019, at 10:01, Lars Kurth <lars.kurth@xxxxxxxxxx> wrote:

Hi all,

can you please propose agenda items for tomorrow?

I have an interesting question which we do need to resolve before the docs efforts can complete:

Ultimately, we ought to decide what license documentation artefacts and generated safety docs should have. I was originally assuming something like CC-BY-4 would be ideal, but CC-BY-4 is not compatible with GPL2 and my understanding is that safety docs would be tightly coupled with code, which may be an issue (or it may be a non-issue)
Then there is a question about business needs: how strong of a copyleft for docs would be acceptable for use in safety contexts
I think the example Antonio was preparing may be of help in making that decision

Regards

Lars

Open actions

ACTION: Artem will send part 2 of ISO2626 customization example to the group
ACTION: Francesco to publish sanitized version of ISO2626 sheets
ACTION: Artem, Francesco, Lars and Artem to discuss what skills we need in a sub-group to drive progress on ISO2626 customization and see how we can make this happen

ACTION: Francesco’s team to double check MISRA results and later share with group

ACTION: Antonio to provide a sanitized example of safety docs (including requirements) for system software that we can use as an example

_______________________________________________
Fusa-sig mailing list
Fusa-sig@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/fusa-sig