-
Notifications
You must be signed in to change notification settings - Fork 15
18 Dec 2024
Philipp Ahmann edited this page Dec 18, 2024
·
2 revisions
** indicates TSC voting members*
- *Philipp Ahmann
- *Alessandro Carminati
- *Igor Stoppa
- *Gabriele Paoloni
- *Nicole Pappler
- *Matt Weber
- Michael Mahoney
- *Kate Stewart
- Jaylin
- *Paul Albertella
- Naresh Ravuri
- *Matt Kelly
- Elana Copperman
- *Sudip Mukherjee
- Pete Brink
- *Lukas Bulwahn
- Steve VanderLeest
- Youssef Hajjioui
- JE[A]Y
- Vipul Gupta
- *Olivier Charrier
- *Christopher Temple
- Qasim
- Action items in github issues
- https://github.com/elisa-tech/tsc/issues
-
AI-Paul: Discuss in OSEP WG meeting where to put the "good practices for Open Source" document
- Discussed, but not a proposal yet
-
AI: EMQ SDV WG ideas to be added to one of next TSC meeting agenda
- Follow up between Philipp and Jaylin during January.
- Space vs. Aviation:
- DO-178 is for aviation while Space is regulated by NASA's standard.
- Radiation is worse in space.
- People element and NASA is between aviation and military. Many space vehicle have lower risk on human life.
- Unmanned control systems are typically level C in aerospace. Military is less rigorous. You can start with military or NASA and make it forward to commercial aerospace.
- What was presented in workshops was mainly for unmanned spaceships.
- F Prime, cFS and SpaceROS can support also other industries and their problems. From DO178 perspective it is most likely level D or QM level for ISO 26262. They heavily take availability into account.
- This may be worth a follow up discussion with the presenters (like Ivan)
- A table mapping the different standards and levels to each other can be useful.
- MIL standard for the level of rigor levels MIL-STD-882E
- Survey results will be shared in one of the following TSC meetings after completion and summary being availble
- Virtual experience:
- Majority of live talks were good. Some mic issues happend with audience questions (especially from last row).
- Weird with the camera of the owl. You partially just saw the middle of people, no head not feed.
- Follow discussions was hard due to mic issues.
- Question came up if this will be an annual thing now. Need to investigate for next year and look for other NASA site or there is space conference in summer (before or after).
- SGL practical next steps:
- Identify people who want to work on it.
- Clone eventually AGL configurations and work from there. Which compents need to go in. How does this interact with cFS, SpaceROS and so on (as userspce level).
- Minimal Boeing kernel config is more in the aerospace, but it need to be checked, if it fits for aerospace (Config is not build for class D)
- Mainly systems were baremetal with RTOS and Linux (also on one Chip), but there was a mentioning to go for mixed-criticality. Also container technology was of interest for working model and having different payloads.
- TSC members to upload their content.
- Content presented by TSC members is considered to be CC 4.0
- Proposal:
- Add presentations from TSC participants during workshops.
- Make them part of PR review
- Ping TSC members to review.
- Side topic: Alessandro recorded his session from day 1 of workshop. Should we post upload it?
- This is good. Everybody is welcome to share own recordings in case they are done.
- https://github.com/elisa-tech/wg-osep/pull/49 is ready to get approval by Gab or Igor. After this Paul can merge it.
- Also presentations from other events with slides and recordings should be added to knowledge base, not only ELISA workshop content.
- Review potential PRs by the author of slides. Additionally, bring them up in TSC meetings.
-
Review and publish 'Contributions' material as 'official' ELISA guidance
-
Stages of quality.
- Documentation in repo
- Published as github pages
-
Rinat may be a candidate for support on setting things up.
-
Paul need share information how he setup things so far.
-
Idea:
- Have one main github repo as the Index project linking from elisa.tech resource section.
- Have a Github action to create sub-domains for workgroups to publish their results
- sub-domains are for free, just need to be created.
- WG leads to approach Min as she can create sub domains for github elisa-tech organisation.
- https://docs.google.com/document/d/1c7S7YAledHP2EEQ2nh26Ibegij-XPNuUFkrFLtJPlzs
- Feedback from workshop incorporated in the document as proposed changes.
- Gets reviewed on Friday in Arch WG meeting.
- Steven Rostedt volunteered to be a pilot with ftrace subsystem to evaluate proposed template.
- We should try to get some parts of the requirements out of the direct code.
- Next will be practical proposal how to achieve this, e.g. by touching symantics syntax.
- Pretty clear idea on the practical upstreaming parts to be touched.
- The document needs the reasoning and rational and make this a released ELISA whitepaper.
Up to 3 bullet points
- Aerospace/Space
- Automotive
- Medical
- Arch
- Linux Features
- OSEP
- Tools
- Systems
- **Next TSC Meeting will be January 18th **
- Will be on LFX. Make sure to have the invitation updated!
- https://zoom-lfx.platform.linuxfoundation.org/meeting/93854839763?password=407e2a6d-4bc0-463c-aae7-75d63e8b5859
- To be defined: SDV seminar by EMQ to motivate the update and cloud part of HPC systems
- RT webinar once PREEMPT_RT as last patch is mainline.🥳
- Past webinars on website: https://elisa.tech/seminar-series/
- Later next year:
- ELISA user story by a company.
- Julia Lawall about formal verification (derived from Lund Linux Con presentation
- 01-02 Feb Fosdem in Brussels (Belgium)
- AGL AMM Tokyo
- Embedded World Nurenburg
- LF Member summit
Collaborative editing: https://mensuel.framapad.org/p/elisa-tsc-minutes-a9tp?lang=en