...
Masanori Itoh (Toyota)
Hiroyuki Ishii (Panasonic)
Masato Endo (Toyota)
Walt…
…Walt (Linux Foundation)
Jan-Simon (Linux Foundation)
Discussion Materials
View file name AGL-OSPO-EG-20250304.pptx Presentation deck under review: https://docs.google.com/presentation/d/1xOR1PVTob6HcsxVgw6_DID2x3-dEvgHT/edit
...
Next Meeting
Next scheduled meeting is Mar. 18 during the LF Member Summit in Napa. Better to cancel Mar. 18 call?
Agenda/Minutes
Recap of Recent Events
AGL AMM Spring
Three Two in-person meetings regarding OSPO-EG (Feb. 25 before SC, Feb. 26 OSPO-EG Updates session, Feb. 28 workshop), and we got several important comments / questions and discussion.
KPI of OSPO activities
What is the most important among OSPO activities (Strategy, Compliance, Contribution)?
(Quantitative) KPI of OSPO activities
…
OpenChain JapanWG Community Day Recall
Mar. 3-4
Panel Discussion
“Your OSPO is not my OSPO“
Some companies started OSPO formation from SBOM handling.
…
Executive Deck Review Status
Ongoing.
Key Discussion Points:
Status Update
Presentation Deck
Need review comments!!
Approval process?
English/design blush up help?
OSPO Show Case
Got answers from 4 companies.
Update: Events
OpenChain JapanWG Community Day (Mar. 3-4)
FYI: Call invitation
Save this file (
| View file | ||
|---|---|---|
|
Executive Presentation Deck:
The deck is under public review until February 19, 2025 (Japan time).
No comments have been received yet; attendees were encouraged to provide feedback.
Discussion on improving the deck's English and design quality before finalization.
Suggestions to consult the Steering Committee (SC) for approval and feedback.
AGL Google Drive will be used to host the deck for easier collaboration and commenting. See https://docs.google.com/presentation/d/1xOR1PVTob6HcsxVgw6_DID2x3-dEvgHT/edit?usp=share_link&ouid=102685495927314229835&rtpof=true&sd=true
Feedback on Presentation Deck:
Concerns were raised about the balance between explaining open source usage and contribution.
Suggestions to restructure the document:
Combine chapters 1-3 into a concise background section.
Move detailed explanations to an appendix.
Focus more on the purpose of the Open Source Program Office (OSPO) in the main content.
Agreement to create two versions of the deck: a detailed version and a simplified version for executives.
Special Case Study:
Contributions from Toyota, Honda, Bosch, and an anonymous German OEM were reviewed.
Insights into community contributions and differences in approaches were discussed.
Event Updates:
Adjustments to the schedule for the face-to-face workshop at the AGL All Member Meeting (AMM) in Tokyo.
Collaboration with OpenChain for a community day event on March 3-4, 2025, at Toyota's venue.
Registration is required for in-person attendance.
Next Steps:
Attendees to provide comments on the presentation deck via Google Drive or other channels.
A follow-up discussion on the deck will be scheduled for Tuesday, February 25, 2025, before the SC meeting.
Further refinements to the deck based on feedback.
Action Items:
Masanori Itoh:
Incorporate feedback into the presentation deck.
Prepare two versions of the deck (detailed and simplified).
Walt Miner:
Set up a follow-up discussion on February 25, 2025.
All Attendees:
Review the presentation deck and provide comments via Google Drive or email.
Prepare for the next discussion on the deck.
Next Meeting
Mar. 4, 2025, 1:00pm (UTC) / 10:00pm(JST) via Zoom
...
AMM Feb. 26-27
“AGL OSPO-EG Updates and Discussion”, Feb. 26 16:10 - 16:40(JST(UTC+9))
“Update on Open Source Program Office (OSPO) Activities in Japan - Special Session for Japanese Attendees”
AMM F2F Feb. 28
https://wiki.automotivelinux.org/agl-distro/feb2025-f2f
...
https://zoom.us/j/783452290?pwd=Z2p0Z0lQaUNxMWVtZSt6ZmRKSTNxdz09
https://docs.google.com/spreadsheets/d/1NBjIdJnRoet8v-Y4Hr5kvAim2FYJvFeR28W3dzE0-kc/edit?gid=0#gid=0
...
Renesas case was interesting because their contribution activity was driven/promoted by marketing team not engineering team.
Day2 panel
Lots of companies are still handling SBOM using Excel. We have to support those companies/people and ease their pains by offering .
Q. What is the use case of SBOM files?
(1) License Compliance, (2) Security Assurance, …
Some people mentioned configuration management too. E.g., Dependency management
Now, there is no clear standard/guideline for SBOM quality. Some organizations/documents mention SBOM quality, but not clear. For example, what kind of information an SBOM file contain? Supplier name, package name, version, etc. Fluctuations in abbreviation. This causes difficulties to handle SBOMs.
Q. Linux kernel case?
D. Yocto kernel, Renesas kernel…
Executive Deck Review Status
English Expression Improvement → Reflected comments from Philipp
Section 1.3 wording: “Consumption” instead of “Usage“ → “Usage”
Chapter 2 cover slide wording: “Opportunities” or “Benefits” --> “Opportunities”
“Usage or Contribution” per each slide
Section 1.3 “Usage and Contribution” is not described/mentioned later chapters, especiially Chapter 2(“Opportunities”) and Chapter 3(“Management” to control “Risks”).
Discussion to put badge(s) (“Usage“ or/and “Contribution“ ) in the title line of each slide. But, many slides have both aspects. Endo-san will update slides.
“2.1 Ecosystem“
Ecosystem has 2 sides. One is to be the leader of leaders as a winner of competition, the other is sharing a set of software components as a kind of common property to be maintained/improved collectively. Philipp’s statement (already reflected) covers both (IMHO). Endo-san has another idea.
Consider to add (example) KPIs