/
2026-01-20-OSPO-EG

2026-01-20-OSPO-EG

January 20, 2026, 12:00am (UTC) / 10:00pm(JST) via Zoom

Attendees

  • Walt Miner (Linux Foundation)

  • Jan-Simon (Linux Foundation)

  • Masanori Itoh (Toyota)

  • Masato Endo (Toyota)

  • Hiroyuki Ishii (Panasonic)

  • …

Discussion Materials

  • OSPO-EG direction

Next Meeting

2026/02/17 (skip 2/3).

Agenda/Minutes

  1. Re-consideration of OSPO-EG Operations

Discussion from Japan local team

AGL OSPO‑EG — Proposed Future Direction (1-Page summary for Walt )

Endo(Toyota), Itoh(Toyota), Ishii(Panasonic)

  1. Overall Direction

    1. Maintain continuity of OSPO‑EG activities, even at a small scale.

    2. Shift to sustainable, lightweight activities.

    3. Focus on actions that steadily help grow contributors within the automotive OSS community.

  2. Increasing Contributors (Primary Goal)

    1. OSPO‑EG will reposition itself as a group that supports both mentors and potential contributors by helping resolve their practical challenges.

    2. This approach follows the direction presented at OSSJ (see attached slide), but will initially focus on a small portion and expand step by step.

      https://ossjapan2025.sched.com/event/29Fm9/driving-oss-contribution-agl-ospo-eg-insights-and-strategic-plans-for-the-automotive-community-masanori-itoh-toyota-motor-corporation-hiroyuki-ishii-panasonic-automotive-systems

      image-20260120-112322.png

  3. Mentoring Model (Initial Trial)

    1. To establish a repeatable mentoring framework:

      1. Mentor candidate: Yamaguchi (AISIN)

      2. Mentee candidate: Kuzuu (PAS)

        1. Panasonic has an internal activity shooting for upstream contributions.葛生(Kuzuu) san can be a very good candidate.

        2. Next step could be other (maybe Japanese) OEMs (e.g. Mazda, Nissan (and maybe Toyota))

      3. Will serve as the first trial case (“pilot” role) to understand workload and refine the process.

    2. OSPO‑EG will also:

      1. Support both mentor and mentee in solving technical and/or in‑company issues, including creating common guidelines

      2. Identify and prepare Good First Issues

      3. Seek cooperation from community members (For example, JS, Joel…

      4. Encourage OEM involvement (Toyota, Mazda, Nissan, Suzuki, etc.)

  4. Meeting Structure Proposal

    1. (A) AGL OSPO‑EG

      1. Continue as a monthly meeting, focused on:

        1. AGL‑internal topics

        2. Consultation time with Walt and AGL community

        3. Japanese‑language Local meeting will be paused.

    2. (B) “Automotive Open Source Governance Meeting” (tentative)

      1. To address global requests (EU/US) for consolidation of automotive OSS governance discussions:

        1. A lightweight, cross‑project governance session

        2. Recorded for asynchronous viewing

        3. Weekly cycle covering Asia / North America / Europe, avoiding late‑night participation

        4. OpenChain will prepare a front page listing:

      2. Topics

        1. Mentor/Mentee information

        2. Contact points / how to request mentoring

        3. Inclusive reach‑out: OpenChain, AGL, ELISA, EclipseSDV, etc. (Ensure no barriers for non‑LF projects)

      3. Actions

        1. Endo-san will create github pages to recruit participants (mentors/mentees, etc.)

  5. Initial Actions to Launch

    1. Recruit contributors

    2. Recruit mentors

    3. Publish and maintain Good First Issues

These three tangible items will serve as the foundation for restarting steady OSPO‑EG activity.

Conclusion

  • Consensus formed. Go forward along with this way.

  • The kick-off meeting will be February. Endo-san will make an announcement.

  • Endo-san will make an announcement of the governance meeting by the end of next week, and Walt will mention the meeting at the FOSDEM Automotive BoF.

  • Next meeting: