2025-04-15-OSPO-EG
Date/Time
Apr. 15, 2025, 12:00am (UTC) / 09:00pm(JST) via Zoom
Attendees
Masanori Itoh (Toyota)
Hiroyuki Ishii (Panasonic)
Masato Endo (Toyota)
Walt (Linux Foundation)
Victor Lu
@Keiya Nobuta
@tokita.hiroshi
@Takashi NINJOUJI (Honda)
@Naoto YAMAGUCHI (AISIN)
Morris Hung (ARM)
Discussion Materials
Re-organized discussion points summary from Apr. 1 call
to be uploaded
Next Meeting
Apr. 29, 2025 → after Golden Week May. 13
Agenda/Minutes
Sync up of the OSS & Promotion deck status (Itoh, Walt)
Discussion of Next Actions
x
Discussion
OSS & Promotion deck status
Handed over to Walt, waiting for completion of
Asking AB for comments (in 2 weeks)
Emily suggested to talk to Mike Wooster(?), the head of business development of LF. He could provide more slides for references. Emily is interested in blog post regarding this activity.
Introducing the published deck (and related topics) at AGL AMM Summer in July
Walt will check how long the English check and artwork improvement will take to LF.
Next Actions
OSS & Promotion deck companions
(1) Guidelines for behavior – “The Illusions and Truths of Participating in OSS Communities“
(en + ja)
(2) Incremental improvement of the deck reflecting feedbacks from the consultation trial
Usage guide matrix depending on the target and maturity level of company (TBD)
Consultation trial
Underway for 2 companies
Acceleration of OSS Contribution
Management side problems break down and resolutions
x
Hands-on training of contribution depending on various projects/SCMs etc.
When contributing to projects hosted at
GitHub (, Gitlab)
Launchpad
When contributing to AGL
JIRA : reporting issues
Gerrit : contributing code
When contributing to Linux kernel
mainline kernel
LTS kernel
More fine grained topics (e.g. git knowhow)
How to ‘git send email’
etc.
Collect real/actual problems through the EG call, prioritize them and discuss solutions (Ishii-san’s suggestion)
management side, technical side…
Conduct a survey? (Endo)
But how can we design the questionary set? (Itoh)
examples of questions
workload issue (no time to do contribution) → management issue
some reluctant(?) inside one’s own company (???)
collect pain points/opinions through a shared document (e.g. google doc)
Until one month later (There is a vacation season in Japan so called the Golden Week)
Continue discussion through Discord/email/confluence, and discuss online on May 13. (next OSPO-EG call)
Apr. 1 call log.
Some additional materials for the (Executive) Presentation deck
Matrix of ways to use the presentation depending on the target and company’s maturity level
How to spread out this document (promotion strategy) is important. It’s important to improve this document or create variations of this document based on 'real' opinions (feedbacks). (Endo)
Consultation/support for establishing OSPO for companies (meeting base)
Explanation story depending on company’s maturity level
Actual operations of OSPO after its launch
Japan team already began a trial under LF Anti Trust Policy
Brainstorming Seeds
How to accelerate contributions to AGL UCB (priority: highest)
Not only AGL
How to set KPI of contribution
Creating a FAQ for front line engineers
How to handle Corporate CLA
Hands-on of Contribution (Improve technical skills)
Concrete activities of 'Contribution' (Improve Understanding what todo)
In preparation of an explanation deck of ‘Illusion and Reality of Contribution’
Why it’s hard to make contributions (from Japanese?) companies/automotive industry?
company side
system/rule/…
engineers side
x
OSPO-EG as the OSPO of AGL?
AGL UCB SBOM improvement [priority: medium?, direction: different from OSPO-EG focus? (Endo)]
Collaboration with CIAT-EG?
Scarthgap uses SPDX 2.2(2.3?), master uses SPDX 3.
Need discussion.
Coverage/Correctness
Tooling topic : commercial products do not support SPDX 3.x yet.
During EW, there was a discussion of tooling improvement.
discussion
In the context of ELISA, they are interested in SPDX safety profile. When will we move to SPDX 3.0?
1 year later when Yocto LTS moves to SPDX 3.0.
How to drive upstream based development?
Other issues/pain points
…
How to proceed these works?
Create sub taskforce?