[FuSa SIG] New private/unarchived Fusa-Sig list, secure document store and changes to agenda template

[Lars Kurth <lars.kurth.xen@xxxxxxxxx>]

Dear FuSa SIG members!

First of all, I hope you had a great holiday and I also wanted to wish you a 
Happy New Year!

I had a number of actions to create a discussion space and document store which 
would allow us discuss MISRA C and Safety Spec related activities.
This required setting up new infrastructure, such that we do not accidentally 
share information publicly that may be covered by a (c)

The mail also contains some organizational 

1.1 Fusa-sig-noarchive@
-----------------------

I set up https://lists.xenproject.org/mailman/listinfo/fusa-sig-noarchive and 
subscribed EVERYONE who has let me know that they have access
to a MISRA C spec to the list

The master copy is of who has what is at: 
https://cryptpad.fr/sheet/#/2/sheet/edit/Euub0cqo9lzf89Z4A+ispZTt/

I do not have information from some of our core team members, such as

robin.randhawa@xxxxxxx
artem_mygaiev@xxxxxxxx
kstewart@xxxxxxxxxxxxxxxxxxx
shinya.konishi.xw@xxxxxxxxxxx
hisao.munakata.vt@xxxxxxxxxxx

whether they have access to a MISRA C spec or any other safety standard. Please 
edit the spreadsheet or let me know by responding
privately to this mail and I will add you to the unarchived list.

1.2 Ground Rules for the list
-----------------------------
To avoid any (c) issues, fusa-sig-noarchive@ membership is restricted to 
full-time named SIG members who have access to MISRA C 
and optionally additional safety standards. 

This allows us to:
- Have free discussions about MISRA C and share (c) snippets of the MISRA C 
spec on this list
- It does not allow us to do the same for ISO 26262 and other safety standards
- However, we can have discussions say about ISO 26262, and refer to documents 
which are stored in a secure 
  and access controlled document store (see 1.3)

As the list is not archived, documents should be 
- Stored in a secure access controlled document store (see 1.3)
- Anything which does affect everyone should be published on fusa-sig@ (maybe 
with references to docs in the store,
  and maybe sometimes in a sanitized fashion)  

1.3 Cryptpad teams
-------------------

1.3.1 Team: Restricted (Misra)

I have set up one cryptpad team space as part of the subscription we have.

A team, is essentially an entirely separate collaboration space which can only 
be accessed by registered and manually added 
cryptpad users. This should ensure, that only FuSa SIG members who have 
purchased respective standards, can access materials 
that may be protected by that standard's copyright.

I will send out a set of instructions on how to sign up and access documents in 
a separate mail.

1.3.1 Team: Restricted (Other)

I also propose we set up a second such team for discussions about other 
standards. However, as I do not have access to a spec
I cannot be part of the "team" and I will need a volunteer who can act as an 
owner and/or admin.

@Artem, @Antonio: is t?his something you are willing to pick up


1.4 Minutes / Agenda
--------------------
On request, I changed the Agenda/Minute template such that it is clear whether 
Assessors input is needed. See snippet below

  A) Agenda Items
> A.1) Agenda Items that need Assessor input
> ...

  A.2) Other agenda items
  ...

In essence: I reordered the template such that it is easy for assessors to 
decide whether to attend a meeting

1.5 Next meeting
----------------
The first meeting in 2020 is on Jan 14 at the usual time
There is no meeting next week

Best Regards
Lars




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