2024-12-10-OSPO-EG

Owned by Masanori Itoh
Last updated: Dec 16, 2024 by Walt Miner
3 min read

Date/Time

Dec. 10, 2024, 1:00pm (UTC) / 10:00pm(JST) via Zoom

Attendees

  • Endo, Itoh, Yamashita (Toyota)

  • Ishii (Panasonic)

  • Walt, Jan-Simons (LF)

  • Marius (Collabora)

  • Yamaguchi (AISIN)

  • Nagayama, Miyashita (NISSAN)

  • Kusakabe, Tsubouchi (Honda)

  • Kwon(Hyundai)

  • Nobuta

  • Yamada

Agenda

Discussion Materials

Minutes

  • Note: AI Generated from Zoom transcript

1. Introduction and Agenda Overview

  • The meeting commenced with greetings among participants from various companies in the automotive industry.

  • Agenda Items:

    • Reviewing a list of issues related to OSS in the automotive industry.

    • Providing explanations and examples for these issues.

    • Introducing each company's approach to OSS management through showcases.

2. Adoption of Chatham House Rule

  • A brief discussion was held on adopting the Chatham House Rule to encourage open and confidential discussions.

  • Decision deferred; participants invited to share thoughts privately if interested.

3. Identification of Key Issues

Participants outlined ten primary issues affecting OSS usage in the automotive industry:

  1. Long-Term Support (LTS)

    • Need for extended maintenance due to the long lifespan of vehicles.

    • Challenges in ensuring ongoing support for OSS components over many years.

  2. Functional Safety and Regulations

    • Addressing safety certifications and compliance (e.g., ISO 26262).

    • Ensuring OSS components meet industry safety standards.

  3. Lack of Documentation

    • Insufficient documentation hinders understanding and integration.

    • Opportunity for the automotive industry to contribute to improving documentation.

  4. Balancing Safety and Cost ("Safe but Cheap")

    • Pressure to enhance safety while reducing costs.

    • Challenges in achieving high safety standards affordably with OSS.

  5. Executive Understanding and Support

    • Difficulty in convincing executives of the importance of investing in OSS.

    • Need to highlight the strategic value and benefits of OSS involvement.

  6. Misconceptions About OSS

    • Addressing beliefs that OSS is always free and requires no maintenance.

    • Educating stakeholders on the realities of OSS development and upkeep.

  7. Supply Chain Requirements

    • Managing OSS compliance throughout the supply chain.

    • Meeting regulatory requirements and avoiding potential risks.

  8. Talent Attraction and Retention

    • The role of OSS participation in attracting skilled engineers.

    • Offering opportunities for engineers to innovate and contribute.

  9. Motivating and Supporting Engineers

    • Encouraging internal teams to engage with and contribute to OSS.

    • Providing resources and support for OSS involvement.

  10. Establishing Open Source Program Offices (OSPOs)

    • Lack of knowledge on how to create and structure OSPOs.

    • Sharing best practices for launching and operating OSPOs.

4. Discussion on Positive Opportunities

  • Emphasized balancing challenges with the positive aspects of OSS.

  • Key Opportunities Identified:

    • Cost Savings: Shared development reduces costs.

    • Increased Productivity: Standardization and collaboration streamline processes.

    • Innovation: OSS allows rapid adoption of new technologies.

    • Talent Acquisition: Active OSS participation attracts top talent.

    • Standardization: Collaboration leads to industry-wide standards, improving compatibility.

5. Prioritization and Grouping of Issues

  • Agreed to prioritize critical issues to focus efforts effectively.

  • Suggestions:

    • Group related issues (e.g., combine "Lack of Documentation" with "Functional Safety").

    • Focus first on high-priority areas like Long-Term Support and Functional Safety.

6. Proposal for Company Showcases

  • Proposal to create a standardized template for companies to present OSS initiatives.

  • Showcase Template Includes:

    • Company Overview: Brief introduction.

    • OSPO Structure: Organization (formal or virtual).

    • Functions and Focus Areas: Responsibilities such as contribution practices, tooling, compliance, and security.

    • Success Stories and Lessons Learned: Share experiences to assist other companies.

  • Aim: Collect and share showcases to illustrate real-world practices and support executive discussions.

7. Next Steps and Action Items

  • Feedback Collection:

    • Members encouraged to provide input on the showcase template via mailing lists or online forums.

  • Refinement of Issues:

    • Continue discussions to refine the list of issues, incorporating challenges and opportunities.

    • Develop materials to effectively communicate the importance of OSS to executives.

  • Scheduling:

    • Next meeting scheduled for early January, considering the holiday period.

    • Participants agreed to maintain communication through digital channels in the interim.

8. Conclusion

  • Reinforced commitment to addressing OSS challenges in the automotive industry.

  • Emphasized collaboration, knowledge sharing, and proactive engagement to harness OSS's full potential.

Next Meeting

  • Jan. 7, 2025, 1:00pm (UTC) / 10:00pm(JST) via Zoom

    • Note: Dec. 24 is cancelled.