GENIVI Compliance

[Alison Chaiken]

The GENIVI Alliance Compliance web page appears to be 404:

http://genivi.org/ABOUT/ComplianceProgram/tabid/502/Default.aspx

My employer would like to learn more about how to ensure that a
MeeGo-Tizen product is GENIVI Compliant, but I'm not sure how we
should do so. Is it still possible to find out what Compliance
entails without joining as a Member? I thought that I had
previously seen the Compliance specification posted, perhaps at the
URL above.

Thanks,
Alison

[Hoffmann, Joel A]

This is the newest link: http://genivi.org/genivi-compliance-program will probably answer the questions.

-----Original Message-----
From: meego-ivi-bounces-***@public.gmane.org [mailto:meego-ivi-bounces-VVXm0OgCXj2zQB+***@public.gmane.orggo.com] On Behalf Of Alison Chaiken
Sent: Monday, November 14, 2011 4:30 PM
To: meego-ivi-***@public.gmane.org
Subject: [MeeGo-ivi] GENIVI Compliance

The GENIVI Alliance Compliance web page appears to be 404:

http://genivi.org/ABOUT/ComplianceProgram/tabid/502/Default.aspx

My employer would like to learn more about how to ensure that a MeeGo-Tizen product is GENIVI Compliant, but I'm not sure how we
should do so. Is it still possible to find out what Compliance
entails without joining as a Member? I thought that I had
previously seen the Compliance specification posted, perhaps at the URL above.

Thanks,
Alison

--
Alison Chaiken
[phone]  (cell)
             http://www.exerciseforthereader.org/
"If you're going to fight an uphill battle, pick a short hill." -- Larry Tesler _______________________________________________
MeeGo-ivi mailing list
MeeGo-ivi-***@public.gmane.org
http://lists.meego.com/listinfo/meego-ivi

[Rudolf Streif]

The GENIVI compliance specification was never public. A company has to be a
GENIVI member to access it and be able to submit a compliant distribution
to the compliance process. For MeeGo IVI the Linux Foundation entered into
an agreement with GENIVI allowing the MeeGo IVI Working Group to access the
compliance statement and to submit MeeGo IVI to GENIVI's compliance process.

Rudi

Post by Alison Chaiken
http://genivi.org/ABOUT/ComplianceProgram/tabid/502/Default.aspx
My employer would like to learn more about how to ensure that a
MeeGo-Tizen product is GENIVI Compliant, but I'm not sure how we
should do so. Is it still possible to find out what Compliance
entails without joining as a Member? I thought that I had
previously seen the Compliance specification posted, perhaps at the
URL above.
Thanks,
Alison
--
Alison Chaiken
[phone] (cell)
http://www.exerciseforthereader.org/
"If you're going to fight an uphill battle, pick a short hill." -- Larry Tesler
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi

[Alison Chaiken]

For MeeGo IVI the Linux Foundation entered into an
agreement with GENIVI allowing the MeeGo IVI Working Group to access the
compliance statement and to submit MeeGo IVI to GENIVI's compliance process.

As I understand it then, there is a Compliance Specification for MeeGo
Core and tools to check compliance, but there is not a separate
Compliance Specification for MeeGo-IVI? It seems reasonable to
*assume* by some Transitive Law of Compliance that, since MeeGo IVI is
GENIVI-compliant, then a hypothetical distribution that includes
MeeGo-IVI as a subset is GENIVI-compliant, assuming that the
hypothetical superset distribution is compliant with MeeGo Core.
However, the superset distribution cannot advertise itself as
GENIVI-compliant, as doing so would violate GENIVI's trademark.

If anyone followed that logic and believes I'm missing something,
please let me know!

[Clark, Joel]

GENIVI compliance and MeeGo IVI are a superset of MeeGo core.
In some cases GENIVI requires capabilities, in others it requires specific source code. Some requirements are optional, others are required. :-)

GENIVI compliance also requires registration of a specific system with documentation of which compliance requirements have been met with which components.

While Intel has registered a system as GENIVI compliant based on components available in MeeGo IVI repos, it is quite easy to build a MeeGo IVI (Core) compliant image that does not include all the required GENIVI components.

regards
Joel


-----Original Message-----
From: meego-ivi-bounces-***@public.gmane.org [mailto:meego-ivi-bounces-VVXm0OgCXj2zQB+***@public.gmane.orggo.com] On Behalf Of Alison Chaiken
Sent: Monday, November 14, 2011 4:27 PM
To: Rudolf Streif
Cc: meego-ivi-***@public.gmane.org
Subject: Re: [MeeGo-ivi] GENIVI Compliance

For MeeGo IVI the Linux Foundation entered into an
agreement with GENIVI allowing the MeeGo IVI Working Group to access the
compliance statement and to submit MeeGo IVI to GENIVI's compliance process.

As I understand it then, there is a Compliance Specification for MeeGo
Core and tools to check compliance, but there is not a separate
Compliance Specification for MeeGo-IVI? It seems reasonable to
*assume* by some Transitive Law of Compliance that, since MeeGo IVI is
GENIVI-compliant, then a hypothetical distribution that includes
MeeGo-IVI as a subset is GENIVI-compliant, assuming that the
hypothetical superset distribution is compliant with MeeGo Core.
However, the superset distribution cannot advertise itself as
GENIVI-compliant, as doing so would violate GENIVI's trademark.

If anyone followed that logic and believes I'm missing something,
please let me know!

[Wichmann, Mats D]

Post by Alison Chaiken
As I understand it then, there is a Compliance Specification for MeeGo
Core and tools to check compliance, but there is not a separate
Compliance Specification for MeeGo-IVI?

To complement what Joel said... there was some talk of an IVI profile for
MeeGo,
which would presumably get a lot *closer *to the required bits for GENIVI
(I haven't seen GENIVI's spec, but why else would there be an IVI profile?)
but it was not pushed to completion. As I recall there was also a dispute
about some components that MeeGo compliance didn't allow to be
replaced, but which IVI needed to replace anyway. In principle I think
that would have ended up okayed but work on MeeGo compliance went
on hiatus.

[Jeremiah Foster]

On Tue, Nov 15, 2011 at 1:55 AM, Wichmann, Mats D

Post by Alison Chaiken
As I understand it then, there is a Compliance Specification for MeeGo
Core and tools to check compliance, but there is not a separate
Compliance Specification for MeeGo-IVI?

To complement what Joel said...  there was some talk of an IVI profile for
MeeGo,
which would presumably get a lot closer to the required bits for GENIVI
(I haven't seen GENIVI's spec, but why else would there be an IVI profile?)
but it was not pushed to completion.   As I recall there was also a dispute
about some components that MeeGo compliance didn't allow to be
replaced, but which IVI needed to replace anyway.    In principle I think
that would have ended up okayed but work on MeeGo compliance went
on hiatus.

If there is to be a Tizen IVI group we can take up this work again
since it should be fairly easy to create a Tizen IVI profile that
would be GENIVI compliant assuming that Tizen is at least MeeGo-like.
The real stumbling blocks are things like btrfs which are in MeeGo
Core but don't get used in the MeeGo IVI profile. If there is clarity
regarding profile independence then I think that will provide the
greatest flexibility for customers developing products on MeeGo/Tizen.

The current MeeGo Core compliance scheme is draconian and ties one to
a build system as well as a set of packages that are not designed for
anything but small laptops, a segment of computing devices that is
disappearing. The single most important improvement that can be done
is to not base MeeGo compliance on md5 hashsums. I've heard this was a
Nokia idea and if so I'm glad they're no longer involved in the
project.

Regards,

Jeremiah

[Jeremiah Foster]

Post by Alison Chaiken

For MeeGo IVI the Linux Foundation entered into an
agreement with GENIVI allowing the MeeGo IVI Working Group to access the
compliance statement and to submit MeeGo IVI to GENIVI's compliance process.

As I understand it then, there is a Compliance Specification for MeeGo
Core and tools to check compliance, but there is not a separate
Compliance Specification for MeeGo-IVI?    It seems reasonable to
*assume* by some Transitive Law of Compliance that, since MeeGo IVI is
GENIVI-compliant, then a hypothetical distribution that includes
MeeGo-IVI as a subset is GENIVI-compliant, assuming that the
hypothetical superset distribution is compliant with MeeGo Core.
However, the superset distribution cannot advertise itself as
GENIVI-compliant, as doing so would violate GENIVI's trademark.

There is only one path to GENIVI compliance; become a member and
submit your compliance spec.

You can get a long way towards compliance using a compliant distro,
and MeeGo is a compliant distro, everything you need to be compliant
is there. If you're feeling ambitious you can reverse engineer
compliance by looking at the package set and checking out maintainer
email addresses and using a little guesswork. But you'll not be able
to claim compliance since there are trademark issues.

Regards,

Jeremiah