Skip to content

Sep 23, 2024 ‐ 15:00 UTC

Philipp Ahmann edited this page Sep 23, 2024 · 4 revisions

Host:

  • Philipp Ahmann

Participants:

  • Sebastian Hetze
  • Daniel Weingaertner
  • Gabriele Paoloni
  • Alfred Strauch
  • Steven Carbno

Regrets:

  • Nicole Pappler
  • Kate Stewart

Attended Recently

  • Karen Bennet
  • Walt Miner
  • Axel
  • Olivier Charrier
  • Thomas Mittelstädt
  • Andreas Bartelt
  • Guy Lunardi
  • Stewart Hildebrand

Topics & Notes:

Check past action items

Project Proposal: Good Quality Practices in Open Source [cont.]

  • Feedback from LF Europe Advisory Board Meeting
  • Process rendering within Eclipse SDV Automotive Process SIG
  • Text brought from gdoc to github wiki md file: https://github.com/elisa-tech/wg-systems/wiki/Software-Quality-Good-Practices-in-Open-Source-%E2%80%90-Proposal
  • gdoc for further reference: https://docs.google.com/document/d/1AR4JtW7tBtqUsWgtxANyGiexpLBywu7nPLlMm6RPzPI
  • Philipp presented the idea at the Linux Foundation Advisory Board meeting.
    • Gabriele Columbro was positive on the proposal and wants to align with Kate on this.
    • OFE was also sending positive signs on the initiative.
    • Relation and overlap to CRA needs to be checked.
    • Potential to make this a project on its own, in case we do not meet deadline for EU submission
    • LF Europe announced that Zephyr project and yocto project will be assessed as example (PoC) to show what is needed to comply with CRA requirments.
  • What is the clear role of the university?
    • For Dirk Dirk Riehle it could be interesting in case ROS2 is involved.
    • University work should focus more on literature work and comparison of techniques.
    • Safety experience and concrete SW systems engineering should come from companies.
      • Interesting parties: TÜV or exida. AlektoMetis already mentioned to participate.
      • Further industry support is needed here.
  • First discussion with Michael Plagge from Eclipse during BitKom open source event
    • need follow up.
    • Automotive process SIG has a high overlap on what we want to achieve.
    • Proper further discussion with Sara Gallian, Dana Vede, and Ansgar Lindwedel.
  • AI: Draw a picture which shows the interaction of all the initiatives currently around (CRA, Eclipse Automotive Process SIG, ELISA)
  • AI: Draw a picture illustrating the project proposal in a graphical way.
  • Involvement of DIN can also be interesting. Sebastian will take a first contact.
  • Where whole things can lead to: https://github.com/elisa-tech/wg-systems/pull/16/files
  • When ELISA started we tried to map part 6 to Linux Kernel, which was not really successful. We need to make sure that Automotive Process SIG at Eclipse will not run in the same issue.
    • You will not be able to certify a complex pre-existing software fully compliant to part 6.
    • Same is true for trying a full compliance to ASPICE (as the standard was not written for open source software)
    • You need by guided by objectives and not clause by clause of the standards.
  • When showing that we want to be equivalent to a requirements driven process, without being a requirements driven process, the objectives need to be the same for both sides.
  • Regarding the creation of documenting standards there is some semi-automated tooling activity inside Red Hat.

Update of meta-elisa due to failing CI image check

  • new docker container prepared
  • SSTATE temporary mirror enabled for ricefish release
  • intermediate step from needlefish to quillback may be useful as yocto version is the same.

ELISA WS at NASA (Washington DC area)

AoB

  • Meeting October 7th skipped. Meeting next week (September 30th) as normal.
Clone this wiki locally