Difference between revisions of "FuSa SIG/Minutes/2019-05-14"

From Xen
(Created page with " === Important === * Please ensure you have access to all materials, e.g. able to comment on [https://trello.com/fusaxensig Trello boards] or [https://docs.google.com/docume...")
 
m (Materials)
 
Line 58: Line 58:
  
 
From now on everything will be published on Wiki
 
From now on everything will be published on Wiki
 
The online [https://html-css-js.com/js/compressor/ JS compressor tool] will help you to optimize your scripts for a faster page loading.
 
  
 
[[Category:Safety Certification/FuSa SIG]]
 
[[Category:Safety Certification/FuSa SIG]]
 
[[Category:Safety Certification]]
 
[[Category:Safety Certification]]

Latest revision as of 02:57, 15 May 2019


Important

  • Please ensure you have access to all materials, e.g. able to comment on Trello boards or SIG Charter document. Reviews and comments are welcome
  • Please add whatever I have missed in the meeting notes below and let me know if you think something needs to be prioritized for the next week’s call. Any other feedback is also appreciated

Attending

Not checked due to travel

Missed

Not checked due to travel

Minutes

Agreed to split the "gap elimination" stream into 2 parts covering Documentation and Testing as suggested by Stefano Stabellini due to significant amount of work in that area

Lars mentioned it is hard to find all materials since we do not yet have a “registry” and common mailing list. Agreed to reuse, if possible, existing Xen Project infrastructure created for Embedded & Automotive - wiki and mailing list. Mailing list members can be taken from the document listing SIG participants

For now materials are stored in Google Docs which may be an issue for Citrix folks due to corporate policies.

Agreed to assign stream owners according to Doodle poll

  • Safety management system - Artem or Francesco (must be discussed)
  • Eliminating documentation gaps for existing code - Stefano
  • Eliminating testing gaps for existing code - maybe Francesco? must be discussed
  • Process for interacting with mainline development community - Lars
  • Process automation tools - Kate

Agreed that backup leaders will be assigned later on

Stream leaders will check who agreed to participate in scoping effort (according to Doodle poll) and start filling Trello boards with tasks as soon as boards are shared within the SIG

  • Also contact assessors when and if needed for support in scoping efforts

From now on, Lars will be chairing the conference calls and collect agenda items prior to them, Artem will track meeting action items. Meeting will be rescheduled with Lars’ GTM invite

Action items

Update SIG charter according to agreed work streams and selected leaders (Artem)

Create Wiki page to store links to all materials (Lars)

Create mailing (Lars)

Check Google Docs access (Lars)

Create boards for streams and provide full access to Trello boards to all members (Artem)

Missing from previous call:

  1. Create project timeline draft. Since it is not clear what shall be “implementation milestones” can fill in only the “scoping” activities
  2. Review and agree on critical organizational topics related to scoping efforts and SIG operation

Materials

From now on everything will be published on Wiki