[MeeGo-ivi] What comprises IVI?

[Clark, Joel]

> -----Nasa [mailto:nasa01 at comcast.net] wrote:
> 
> ----- "Joel Clark" <joel.clark at intel.com> wrote:
> > As you can see from these pages, I am the MeeGo IVI project team
> > program manager.
> 
> Hi Joel,
> 
> 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
> intention.

I had no impression that you were harsh.

> 
> 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. 

That's fine

> >
> > 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
> > future.
> 
> 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.

The GenIVI goals are specific to GenIVI.  The MeeGo IVI working group is very interested in work done by GenIVI and any opportunities to provide mutual alignment and support.  However GenIVI and MeeGo IVI are not one entity and GenIVI goals should not be interpreted as the sum total of MeeGo IVI goals. The MeeGo IVI working group will define "what MeeGo IVI would look like" 

For example if you look at the charter of MeeGo working groups, the focus is on the user experience

> 
> 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.

We utilize a single numbering scheme across all device segments of MeeGo.
 
> 
> Again -- thanks for the reply.
> 

Thanks for the discussion.