Latest revision as of 15:19, 4 January 2012

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:
    • Intel: Joel Hoffmann
    • LG Electronics: Hyungjin Jeon
    • Nokia: Alistair Adams
    • Pelagicore: Mikael Soderberg
    • Visteon: Pavel Konopelko

• Product Manager (cross-function across Working Group and Project Team)
  • Unifies and prioritizes overall requirements set.
  • Owns the roadmap.
  • co-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 with the Lead Architects and Lead Designers on effort estimates and schedules.
  • co-leads the Project Team together with the Product 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)

Working Group Meetings and Minutes

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.

Shipping MeeGo IVI Products

• Hawtai B11
• Geely EC8
• iKarPC datasheet and catalog page

MeeGo IVI Demos

• MeeGo IVI UI from ICS: video and info, including source code

MeeGo IVI UI (HMI)

MeeGo IVI includes a Sample UI. This UI is sample only because it has always been stolen from some other MeeGo device project and ported with little change to the IVI builds. Also the underlaying UI framework and the UI applications have changed in every version of MeeGo so far.

The MeeGo IVI 1.2.0 UI is primarily based on a collection of QML based applications designed for MeeGo Tablet. It has a IVI specific taskbar app launcher that adds support for scrollwheel and voice command imputs.

• MeeGo IVI 1.2.0 IVI home screen / taskbar User Guide

The MeeGo IVI Home screen / taskbar is tested with a Contour ShuttleExpress Scrollweel.

• Contour ShuttleXpress infromation

Other Scroll Wheels

Other scrollwheels that have been used by the MeeGo IVI community

• 3Dconnexion SpaceNavigator

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.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

View the Roadmap

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com. Current MeeGo IVI feature requests can be found here

Submit new MeeGo IVI feature request

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 in the IVI roadmap.

Weekly Builds

Automated weekly MeeGo IVI repository and image builds are available on meego.com for testing and development baselining. Each build has a build version and date in its path. MeeGo Release Versioning explains the build version numbering scheme. For example 1.2.80.xx is a 1.3 Alpha build, 1.2.90.xx is a 1.3 Beta build, 1.2.99.x is a 1.3 Release Candidate.

• MeeGo weekly build repositories

The first MeeGo 1.2 release was named version 1.2.0 which allows an opportunity for some additional application and User Experience development to be released on MeeGo 1.2 core with future versions such as 1.2.1, and 1.2.2 etc. With this version naming 1.2.0.90 is the pre-cursor to MeeGo 1.2.1. Updates to MeeGo 1.2.0 will either be called 1.2.0 Update or perhaps 1.2.0.1. Each weekly build directory is named with a version number and date. IVI live .iso images are found under the images link in each weekly build directory. A list of every package included a live image is found in the same directory as the image. RPM packages are found under the oss and non-oss links under repos in the weekly build directory.

• MeeGo update repositories

Upcoming Releases

Meego 1.2.0 Update

Update release dates

Links

When the first MeeGo 1.2.0 update is released July 7, 2011, the updated packages will show up in the following repository:

• MeeGo 1.2.0 Update Repositories

• MeeGo IVI 1.2.0 Update approved bugs

• MeeGo IVI 1.2.0 Update proposed bugs

• IVI 1.2.0 Update bug fix status

Meego 1.3

MeeGo 1.3 milestones

Platforms

MeeGo IVI Platforms Supported in Releases

IA32

MeeGo IVI Trunk Prototype Platforms

IA32

ARM

Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.

The suggested reference platform is the Beagleboard xM. The PandaBoard and Snowball most likely will be supported in the future.

MeeGo IVI Development Boards

IA32

ARM

Per Stskeeps on meego-arm IRC on 6/2/2011, Nokia-provided N900 SGX530 drivers with hardfp extensions are known to work with SGX530 revisions 121 and 125. Which OMAP3 SoCs have revision 121 and 125 is not always straightforward to determine. dm8tbr reports problems with N900 hardfp drivers on Beagleboard xM. Stskeeps reports success with these drivers on Beagleboard C4. Tripzero reports success with hardfp drivers on old build of IGEPv2 that had the Cortex A8 processor.

IVI Ports to Consumer Devices

• ia32 Atom processors
  • ExoPC

• ARM v7 processors
  • Trimslice Tegra2

Releases

• MeeGo IVI 1.2
• MeeGo IVI 1.1
• MeeGo IVI 1.0

Resources

• IRC irc.freenode.org #meego-ivi
• Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
• Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
• Presentations and articles about meego-ivi
• IVI for users and developers
• Topics