| I think if nobody else has any agenda items today maybe we should defer But I think I will jump onto the call briefly: maybe there are any interesting updates from Linear Connect: this is a specific question to Arm If there is nothing to discuss we can finish fairly quickly
On the other hand: I cannot host the call in two weeks as it clashes with a talk slot I have at Open Source Summit in Lyon
Lars
Dear All,
unfortunately I'm not able to join today.
regarding my actions:
ACTION: Francesco to publish sanitized version of ISO2626 sheets
STILL OPEN, will try to send it out by this week.
ACTION: Francesco’s team to double check MISRA results and later share with group we double checked, the results are ok and I'll share it with the group by the end of this week
my best Regards,
Francesco.
Il 07/10/2019 17:08, Lars Kurth ha scritto:
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 "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." 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
-- Francesco BrancatiInnovation Manager and SW Solutions Expert
Email: francesco.brancati@xxxxxxxxxxxxx
Phone: +39 0587 21 24 65 (internal number: 104)
Mobile: +39 333 48 52 041
Skype: francesco.brancati
<Logo_ResilTech.png>www.resiltech.com
This e-mail and related attachments are property of ResilTech S.r.l. and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender.
You shouldn't copy it or use it for any purpose nor disclose or distribute its contents to any other person.
Questa e-mail e tutti i suoi allegati sono proprietà di ResilTech S.r.l. e possono essere soggetti a restrizioni legali. Se non siete l'effettivo destinatario o avete ricevuto il messaggio per errore siete pregati di cancellarlo dal vostro sistema e di avvisare il mittente. E' vietata la duplicazione, l'uso a qualsiasi titolo, la divulgazione o la distribuzione dei contenuti di questa e-mail a qualunque altro soggetto.
|
