[FuSa SIG] Agenda Items FuSa Sig meeting 02/07/2019

[Lars Kurth <lars.kurth@xxxxxxxxxx>]

Hi all,

please find attached the shared agenda document at

https://cryptpad.fr/pad/#/2/pad/edit/1gQerdCe5T6+qH7UIyuJvDU3/

Regards

Lars

P.S.: A copy of the actions and proposed agenda can be found below

 

C.1) Recently closed Actions

 

1. Lars: to dedicate the next meeting to Developer Summit Brainstorm and preparation

C.2) Actions not yet resolved

1. Francesco to review and propose modifications to charter entry. 
   Excerpt from SIG charter for Francesco’s convenience - note that Lars wrote this section, but is not attached to it: Define and implement guidelines and examples related to the verification of requirements, architecture, design and APIs as required for safety certification. Develop a strategy to produce missing documentation and work with the Community Interactions and Processes stream to ensure documentation stays up-to-date and is generated where needed.
2. Lars to set up a smaller meeting with Franceso, Kate, Artem & Vasco to walk through the test infrastructure we have. Will talk to Ian Jackson and/or other stake-holders.
   Initial chat with Ian and Andrew. Will follow up with more detail.
   Agreed.
   Ian requested a set of questions, to make the session more productive before the meeting.
   ACTION: Artem will start a discussion thread - thread has started
   https://lists.xenproject.org/archives/html/fusa-sig/2019-06/msg00007.html
   But there was no response
3. Kate to share draft document on tools
   Lars to add tools we have in the Xen community which might be useful to Kate’s list
4. Artem to discuss a more clear subset of what is needed for Misra C / Potential coding standards with George off-line
   Still open
5. Artem to think about design session with regards to toolstack
   Still open
6. Artem to clarify which parts of MISRA C/ISO we need to definitely follow - check with assessors
   Still open. Have been contactiung David. Some will be covered later on.
7. Artem to review Stefano's API list
   See https://design-sessions.xenproject.org/uid/discussion/disc_6i95TjW2zZe7FpTdR6aR/view 
8. Artem to organize call between Franceso, Roberto and himself to discuss and close some open questions in the safety management stream - report back to the group if relevant

C.3) New Actions

D) Proposed Agenda Items

D.1) Quick Progress Update

​Traceability and Docs​​​​​​:
Related to docs and test traceability, Lars has been looking for open source tools which do this: there are lots of proprietary solutions out there, most of which seem to be very heavyweight and expensive. E.g. IBM Rational DOORS and competitors

The only open source tool I could find was Doorstop

• https://doorstop.readthedocs.io/en/latest/
• https://github.com/jacebrowning/doorstop
• https://scholarworks.gvsu.edu/cgi/viewcontent.cgi?article=1016&context=oapsf_articles

which seems to be reasonably active and is primarily based on storing information in-tree and managing these in-tree. I am wondering though, whether there are any more. It also has a scripting API (not documented) which could potentially be used for a traceability test which could be integrated into the GitLab CI or some other existing infra.

@Kate and people experienced with traceability: it would be good to get a sense whether something like doorstop would work

D.2) Developer Summit Brainstorm

Goal: decide which design sessions should be submitted taking into account

• All committers of the project will be there - we actually have a chance to get everyone aligned
• But: realistically we should only have 2-3 dedicated sessions, unless they are technical, otherwise there will be processfatigue 
• Sessions which will happen anyway will be around next-gen CI infrastructure, which would lay the groundwork for safety

 

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