In-vehicle Infotainment (IVI)
MeeGo IVI is setting the new standard for in-vehicle infotainment in cars, buses, airplanes, etc. MeeGo IVI is a Free and Open-Source Software (FOSS) OS distribution integrating the MeeGo Core for embedded systems leveraging and extending functionality known from mobile computers and handsets into vehicles. Building on the MeeGo OS Base and the MeeGo OS Middleware the MeeGo IVI software stack enables rich Internet and multimedia experiences to consumers while traveling.
Organization
The MeeGo IVI organization is composed of a Working Group and a Project Team. The Working Group is responsible for the definition of the roadmap and the MeeGo IVI Project Team executes the implementation through the partnering organizations using the best practices of open-source development. Through the collaboration of organizations and companies covering automotive, computer hardware, communications, and software industries this partnership enables jump-starting product development for rapid delivery allowing adopters to concentrate on their core competencies while benefiting from this extensive know-how and the open-source assets.
For a graphical representation of the organizational structure: Media:MeeGo_IVI_OrgStruct.pdf
Working Group
The Working Group is composed from the following members and roles:
- Working Group Chair
- Represents and promotes the Working Group.
- Leads strategic discussions on requirements, direction, policies.
- Commitment: full-time role.
- Current Working Group Chair: Rudi Streif (Linux Foundation)
- Working Group Representative (the number is not limited, others participants to be invited)
- Represents his/her organization in the Working Group.
- Collects, organizes, prioritizes, and contributes requirements from his/her organization.
- Commitment: 20% - 50% dependent on how actively the organization wants to contribute requirements.
- Current Working Group Representatives:
- Product Manager (cross-function across Working Group and Project Team)
- Unifies and prioritizes overall requirements set.
- Owns the roadmap.
- Leads the Project Team and defines the release schedule together with the Project Manager.
- Accountable to the Working Group for delivery of agreed upon requirements.
- Commitment: full-time role.
- Full job description: Media:MeeGo_IVI_PDM.pdf
- Current Product Manager:
- Program Manager (cross-functional across Working Group and Project Team)
- Works the Lead Architects and Lead Designers on effort estimates and schedules.
- Leads the Project Team together with the Project Manager.
- Accountable to the Working Group for deliverables and schedule.
- Commitment: full-time role.
- Full job description: Media:MeeGo_IVI_PJM.pdf
- Current Program Manager: Joel Clark (Intel)
The Working Group meets regularly. Information on current and past meetings can be found on IVI Working Group.
Project Team
The Project Team has members with various roles that are subject to change according to the requirements of the current projects. The number of members and roles in the Project Team is not limited and grow as the team gains momentum and takes on larger tasks.
- Lead Architect
- Defines technical architecture to meet the requirements n terms of functionality, performance, etc.
- Defines interfaces between modules and components together with other Lead Architects within the same and/or other Project Teams.
- Performs feasibility studies and provides feedback to product manager on technical challenges, difficulties, “show stoppers”.
- Commitment: > 50% dependent on sub-project complexity.
- Current Lead Architect: Tom Counihan (Intel)
- Lead Designer (multiple roles)
- Responsible for the detailed implementation design of the architecture.
- Estimates the effort necessary for implementation.
- Leads implementation team comprised of engineering resources of his/her organization.
- Commitment: full-time role.
- Current Lead Designers
- QA Lead (multiple roles)
- Transforms requirements into functionality test plans.
- Develops interface and compliance test procedures according to the architecture.
- Implements black box and white box test tools through the resources of his/her organization.
- Executes test plans and provides test reports.
- Commitment: full-time role.
- Current QA Leads:
- Release Manager
- Coordinates bug tracking, build and release with the design and QA leads.
- Develops and manages build tools.
- Leads build and release engineering team.
- Commitment: full-time role.
- Current Release Manager: Jeremiah Foster (Pelagicore)
- Engineers for Development and QA (many roles)
- Implement and test the required functionality.
- Qualification varies with sub-project.
- Commitment: full-time role.
Roadmap
The roadmap is always under discussion. But the important thing it that it is open and transparent - and you can contribute. The path to contribution begins on the MeeGo IVI mailing list. This list is the central communication point with all the MeeGo IVI stakeholders participating. Through this list you can contribute ideas, code, and other resources. You will also receive support and advice as well as pointers to other resources on this list, this is where the community comes together.
Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. When creating a feature request, select "New" or "File a Bug" and then on the next screen near the bottom select "MeeGo Features..." and then "MeeGo IVI Features..." and continue from there. For a Feature Request to become part of the MeeGo IVI release plan, it needs to clearly define the engineering requirements and have resources working on development.
More details on the long term direction and short term Release plan may be found at Roadmap Details
Releases
Resources