Hi, I don't know if you are aware of the QtonPi project but they have a team > which is going to focus on IVI applications for the eagerly awaited > Raspberry Pi. Some initial information can be found at > http://wiki.qt-project.org/QtonPi/Device_program/Accepted#IVI
Yep, I am aware of the project. However I am not sure how it is developing at the moment. I think the first think to say is that Mer is, and intends to remain, an > excellent choice for those working in the IVI space :) > The Mer project and Core is not planning to offer a complete IVI stack but > it > makes perfect sense to have an IVI interest group around Mer. At this project stage this is perfectly understandable, that no IVI stack is planned. What is more, at this point I would like clarify what IVI means, at least from my point of view. Many of us, when thinking of IVI, think about automotive vendors automatically. It is obvious because they brought this up in the past and they first created IVI Groups like GENIVI that set IVI standards for car manufacturers. On the other hand IVI means In-Vehicle Infotainment, no restriction to the owner of this domain whatsoever. So an 'owner' might be indeed a car manufacturer producing a OEM IVI system (hardware AND software) for one of his car models, trying to sell this system(with the car) to the end customer for many thousands of Euros(I am particularly thinking here of one of the bavarian car manufacturers ;) ). Another 'owner', IMHO, is the same end customer who brings his IVI System into the car and plugs it in. I am talking about Tablet integration for instance, which is reusable in different vehicles, at home, at work etc. It is cheaper for the end customer, more transparent, easily extendable. In this case IVI is only an interface between the vehicle and the user. Of course there are issues. Car manufacturers have their constraints like, system has to start in less than 200ms, audio, navigation etc. have to be present in next 500ms, and so on. However those are the issues of the car manufacturers ;) Any comments on this are more than welcome of course! Simon, we'd be happy for such a group to incubate in the merproject area > and to > discuss what special needs IVI has from Mer. That may include creating > shared > IVI specific software areas in the OBS and working up QA processes with > Mer Core. Yes exactly, let us start collecting various information about IVI needs on the wiki page Martin created and see how it evolves. Than we can decide how OBS needs to be extended to fulfill those needs. cheers simon :) mit freundlichem Gruss / best regards / pozdrawiam / atentamente Simon P. Bolek ------------------------------------------------------ Dipl. Inf. Simon P. Bolek SAP Consultant Business Mobile and IVI Solutions Cell: +49 (177) 67 36 556 mailto: [email protected] http://www.arcom-ivi.de/ XING: https://www.xing.com/profile/SimonP_Bolek On Thu, Feb 16, 2012 at 7:15 PM, David Greaves <[email protected]> wrote: > Hi Simon, Martin > > I think the first think to say is that Mer is, and intends to remain, an > excellent choice for those working in the IVI space :) > > The Mer project and Core is not planning to offer a complete IVI stack but > it > makes perfect sense to have an IVI interest group around Mer. > > Simon, we'd be happy for such a group to incubate in the merproject area > and to > discuss what special needs IVI has from Mer. That may include creating > shared > IVI specific software areas in the OBS and working up QA processes with > Mer Core. > > David > > > On 16/02/12 17:26, martin brook wrote: > > Simon Hi, > > > > I am also interested in IVI applications in my work and as Carsten says > there is > > also interest from others, I don't know if you are aware of the QtonPi > project > > but they have a team which is going to focus on IVI applications for the > eagerly > > awaited Raspberry Pi. Some initial information can be found > > at http://wiki.qt-project.org/QtonPi/Device_program/Accepted#IVI > > > > I've created a wiki page for interested parties to contribute > > to. http://wiki.merproject.com/wiki/IVI > > > > BR > > > > Martin > > > > > > On Sun, Jan 22, 2012 at 7:13 PM, Simon Bolek <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hello there! > > > > My name is Simon, I am a founder of www.arcom-ivi.de > > <http://www.arcom-ivi.de> an IVI UX successfully built on top of > MeeGo-IVI :-) > > Since MeeGo is not maintained anymore and Tizen is not really an > option at > > the moment, > > I am very happy to see this community building up and growing, keep > up great > > work! > > At the moment I am building the UX on top of Mer and hope that it > would work > > just fine. > > > > Carsten actually just answered one of my questions - about IVI Mer - > that > > there is NOT going to be such vertical in the future, which is well > > explained why in his post here: > > http://lists.meego.com/pipermail/meego-dev/2011-October/484281.html > > nevertheless I would like to ask if: > > - maybe there is an interest for an IVI group in the Mer community? > Is Mer > > Wiki the right place for such a group at all? > > > > I am not an automotive vendor and do not know any at the moment, but > an IVI > > group IMHO would help canalizing ideas, point out reference devices, > test > > sample UXs, etc. > > I could offer my know-how in requirement engineering to help > building up > > such group. > > > > Any thoughts and comments on this are more than welcome! > > > > cheers > > simon :-) > > > > mit freundlichem Gruss / best regards / pozdrawiam / atentamente > > Simon P. Bolek > > ------------------------------------------------------ > > Dipl. Inf. Simon P. Bolek > > SAP Consultant > > Business Mobile and IVI Solutions > > Cell: +49 (177) 67 36 556 <tel:%2B49%20%28177%29%2067%2036%20556> > > mailto: [email protected] <mailto:[email protected]> > > http://www.arcom-ivi.de/ > > XING: https://www.xing.com/profile/SimonP_Bolek > > > > > > > -- > "Don't worry, you'll be fine; I saw it work in a cartoon once..." > > >
