[MeeGo-ivi] What comprises IVI?
nasa01 at comcast.net
Thu Nov 18 09:51:15 PST 2010
----- "Joel Clark" <joel.clark at intel.com> wrote:
> > -----Original Message-----
> > From: meego-ivi-bounces at lists.meego.com [mailto:meego-ivi-
> > bounces at lists.meego.com] On Behalf Of Nasa
> > Sent: Thursday, November 18, 2010 5:42 AM
> > To: meego-ivi at lists.meego.com
> > Subject: [MeeGo-ivi] What comprises IVI?
> > I've had this long standing question/thoughts that I put up on the
> > forum but haven't gotten much of a response too and was wondering
> > what your (ie: people on the list) thoughts were:
> > I'm a little confused... I am somewhat unsure what the IVI platform
> > actually going to be.
> > I have seen (and run) the first 2 releases -- which have been
> > as *demo* of one sort
> > or another. I also noted the involvment of GENIVI, which had some
> > interesting things to say
> > about it on their FAQs:
> > What are GENIVI's goals?
> > BTW: Is there a project/program manager directing what requirements
> > is going to solve (ie: who's
> > driving the bus -- and does he know where we are heading)? I've
> > somewhat struggling with this
> > question for a while.
> > So, does anyone have any concrete idea on this? It somewhat
> > me given I an actually a System
> > Engineer in my real life...
> > Nasa
> The governance of MeeGo IVI is covered in these links:
> As you can see from these pages, I am the MeeGo IVI project team
> program manager.
Nice to meet you. From reading your response (which is very helpful)
I think I might have come off a little harsh -- which wasn't my
Hopefully you won't mind me taking your reply and adding it to a
thread on mp3car (one I started) to keep it members informed of
how things are progressing. Link here:
> I don't think this is the right place to speculate on GenIVI goals.
> There are some components included in the Meego releases that were
> previously included in Moblin releases that have been labeled as
> GenIVI components, but as far as we can tell nobody (in GenIVI or
> elsewhere) is using these components. They are being deprecated and
> we expect they will be replaced with well maintained components in the
I wasn't trying to speculate on GENIVI goals, I was using their stated
goals (from their website) to infere what Meego IVI would look like.
> Up to this point the MeeGo releases have focused on sample/demo
> applications and some coverage of target IVI boards. Resources have
> been limited and many gaps remain in all areas from platform support
> through middleware frameworks extending to applications. The MeeGo
> IVI working group has only been meeting for a few weeks. A few initial
> IVI specific features have been indentified, but specific development
> plans for these are still not firmed up.
This is information that has been missing for a number of us whom are
interested in the platform. We assumed that IVI was at the same level
of maturity as the other platforms, which is what is suggested by the
numbering scheme utilize for the major releases.
> You can see the log of
> features requested by this query:
> That said we are seeing increased interest from the open source
> community and from product vendors. We anticipate the IVI working
> group filling out the strategy and roadmap as well as increased
> developer activity in the months ahead.
> New features may be requested at any time (create new "Feature"
> entries in bugs.meego.com), but generally they won't be accepted until
> there is an implementation that is well maintained, packaged for the
> MeeGo build server, considered of strategic and technical value by the
> MeeGo IVI community (people can vote for a feature in bugs.meego.com),
> and shown to integrate well with existing MeeGo components.
> There are several pages on www.meego.com and wiki.meego.com on "how to
> add" components to meego.
I have been using bugs.meego.com for quite a while to both add bug reports
and vote on items listed within.
> The strategic direction for MeeGo IVI is determined by the MeeGo IVI
> working group, not by the program manager, but in general I believe
> MeeGo IVI is "driving the bus" to provide target platform support in
> MeeGo core (i.e. boots and runs robustly), Automotive enhanced or
> specific frameworks, and automotive hardened SW stacks with a sample
> or reference user experience based on industry BKMs.
> We have a lot to do to reach these goals. The fun is just starting.
> I'm curious what forum you put your questions to previously.
Again -- thanks for the reply.
> Joel Clark
> MeeGo IVI program manager
More information about the MeeGo-ivi