[MeeGo-ivi] What comprises IVI?
rudolf.streif at linuxfoundation.org
Tue Nov 23 08:05:06 PST 2010
MeeGo IVI will essentially a middleware stack and an API to facilitate the
development rich IVI user experiences. The UX is a differentiating factor
hence the the UI that is delivered with MeeGo IVI only serves as an example
for demo and test purposes. It is expected that implementers will create
their own UX.
Bug reports are still valuable because sometimes it is not necessarily clear
if the bug is purely related to the UI or if it is a problem within one of
the layers of the underlying software stack.
The IVI WG responsibility is putting a roadmap together for MeeGo IVI. That
is what we are working on. The feature requests in Bugzilla are an input to
this process. However, this is no magic code producing machine. A feature
requires resources to be implemented hence features that have a resource
commitment will most likely be realized.
I am not clear what you mean by "Are we expecting to get feedback on how the
kernel runs on a particular board?" Who will give feedback to whom? I would
expect that if the community is interested in having MeeGo IVI run on a
particular hardware the community will pick up the porting and the
maintenance and then that board can be added to the supported list of
hardware and built automatically by MeeGo's build system.
If the community has applications and use cases for IVI and needs support
for it from MeeGo IVI's software stack then this is valuable input. I would
start with a high-level top-down user-centric approach asking questions:
What do drivers expect from their IVI system? What do passengers expect from
it? What would kids/teenagers/adults in the rear seat be looking for? MeeGo
IVI will not necessarily solving all it but if you then decompose it to the
level of what data, functionality, connectivity, etc. does the IVI stack
need to provide to support these use cases you will get a list of features
that can be implemented in MeeGo IVI.
Does this make somewhat sense?
On Tue, Nov 23, 2010 at 6:33 AM, Nasa <nasa01 at comcast.net> wrote:
> Let's try this another way. Since the IVI hasn't been defined,
> what are we expecting to get out of the IVI *releases*? The UI
> is mostly based of the handset UI ported to the IVI image -- and I would
> hope it's not intended to be a solution for the car (because
> it won't work there). Bug reports on problems with those seem
> to be a waste of time, for all involved. Are we expecting to get
> feedback on what features are required/desired? Are we expecting
> to get feedback on how the kernel runs on a particular board?
> Additionally, are there things from the community we are looking
> for to help define what the IVI is going to be? If so, what?
> Hopefully, I'm sounding like a dork and the answer(s) is/are right
> in front of me -- just need the slap on the back of the head...
> ----- "Jeremiah Foster" <jeremiah.foster at pelagicore.com> wrote:
> > On Nov 23, 2010, at 14:22, Nasa wrote:
> > 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.
> > I was reviewing this and just wanted to ask, given where things are
> > at, what inputs/efforts would you like to see from the user community
> > at this point(beyond adding feature request to bugs.meego.com ).
> > Should
> > community members be testing the *releases* right now or wait until
> > things
> > become more firmed up? And how will they know when its time to jump
> > into
> > the fray (ie: check the wiki for a roadmap?)? Since the present
> > numbering
> > scheme won't convey that info...
> > There is always lots of garden variety testing to do as well as bug
> > fixing. If you have an ARM board handy for example you can begin by
> > trying MeeGo IVI on it. There has been some work done there but not a
> > lot. If you want to buy a board you might look at the Beagleboard.
> > You can of course download the current IVI sources and run them on an
> > average Atom equipped netbook, with the proviso that you have the
> > right graphics drivers. This is probably the fastest way to
> > contributing since you can get up and running quickly.
> > The community would also be quite welcome to participate in kernel
> > maintenance, at least on the ARM side. That is a void that needs to be
> > filled, though there is some work being done informally in that area.
> > This is a big commitment and one would have to have a bit of
> > experience with this sort of thing beforehand as it isn't trivial to
> > maintain a production quality kernel actively.
> > You can look on the MeeGo wiki in the IVI section for more information
> > about open positions.
> > Warm regards,
> > Jeremiah
> > _______________________________________________
> > MeeGo-ivi mailing list
> > MeeGo-ivi at lists.meego.com
> > http://lists.meego.com/listinfo/meego-ivi
> MeeGo-ivi mailing list
> MeeGo-ivi at lists.meego.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-ivi