-
Notifications
You must be signed in to change notification settings - Fork 1
Meeting September 19th 2025
Philipp Ahmann edited this page Sep 19, 2025
·
3 revisions
- Philipp Ahmann (Host)
- Gabriele Paoloni (alternative host)
- Wendi Urribarri
- Hugo Cornelis
- Karen Bennet
- Tu Thanh Nguyen
- Girish
- Simone Weiss
- Philipp Ahmann (Host)
- Ivan Perez
- Nicole Pappler
- Michael Armbruster
- Daniel Pisanu
- Olivier Charrier
- Daniel Weingaertner
- Vinicius Tadeu Zein
- Leonardo Rossetti
- Naoto Yamaguchi
- Yuya Okamoto
- Hiroaki Shigehara
- Sebastian Hetze
- Philippe Quere
- Roberto Paccapeli
- Eric Laurin
- Fadi Labib
- Daniel Haack
- Mikel Azkarate
- Deena
- Naga (Timesys/Lynx)
-
AI-Simone and AI-Michael will create a spread sheet for Xen
- Simone and Michael will sync.
- Simone starts working on it. Considers to take a 2nd sheet for Yocto.
- Plan is to present the status during the ELISA Workshop in November for community discussions.
- Make a 30% review and compare Xen with Yocto during next meeting
- AI-Wendi will create a spread sheet for LLVM
- AI-Daniel W. and AI-Ivan will create a spread sheet for Linux
- AI-Nicole will create a spread sheet for Zephyr (later probably due to BW issues)
-
AI-Gab add a descriptions in Best practices sheet (as he anyway has to do it for another topic).
- DONE by Roberto. Could be reviewed.
-
AI-Nicole Invite Stefan to the next Elisa workshop. https://forms.gle/PrvR4JAEbCFQTVPy9
- DONE. Stefan confirmed he can travel.
- Template for filling (new working document): https://docs.google.com/spreadsheets/d/1jR0oGQpwJTdThJAOtWP70GrdWSz7K-ol84j5BWX2h8g
- Descriptions are added. Ready for review.
- AI-Philipp: Review the sheets "Practices" and "Common themes" and provide feedback to Wendi.
- Create a first small deliverable (report) out of the following artifacts:
- Template
- Common Theme & Practices
- First check with Xen & Yocto
- The first deliverable can serve as a documentation for others.
- Paul Albertella discusses "definition of Quality" in OSEP-WG. It would be good to know the outcome.
- New topic which came up recently.
- Overall, need to make sure, we are not creating too much overlap. Close alignment needed with OSEP, to keep consistency.
- AI-Philipp: Check with Paul where this is leading to.
- Try to reuse the OSEP artifact. Also get it into the Glossary.
- Some people showed interest in funding during the survey.
- What could be done to get a funding.
- Funding was our way of getting long term invest.
- We start making progress with template, listing projects.
- From an abstract proposal we concretely drafting practices.
- Define checkpoint on regular intervals, if the interest in funding has grown.
- What is a good critical mass? --> LF says typically 3-4 paying members.
- Example:
- Buildroot (https://buildroot.org/) did not have an LTS. Sponsorship program was started. Going to conference and cooperate with core maintainers.
- The program helps to produce a service to existing customers to prepare a security service to customers.
- Not many sponsors and money, but very practical and provides benefits to buildroot overall.
- Important to search for tools in use for companies willing to pay for them. The tools are the commercial service offering.
- ELISA workshop (Nov 18 to 20 in Munich) topic proposal open: https://forms.gle/PrvR4JAEbCFQTVPy9
- One proposal: Status of Lighthouse-SIG by Simone
- Check on status of OSS JP submissions during next meeting.
Helpful links
- Repository: https://github.com/elisa-tech/lighthouse-oss/
- Location of meeting minutes: https://github.com/elisa-tech/lighthouse-oss/wiki
- GDrive: https://drive.google.com/drive/folders/1MRq7-5fnGnB4Ve3pJn0coD4XeOMT_rbl
- Mailing list: https://lists.elisa.tech/g/lighthouse
- Discord: https://chat.elisa.tech
Collaborative editing: https://mensuel.framapad.org/p/lighthouse-oss-af5r?lang=en