Skip to main content

Eclipse Foundation Working Group Charter - openGENESIS

Mission

The mission of the openGENESIS Working Group is to provide methods and tools for the assessment of artificial intelligence (AI) used for autonomous driving. AI algorithms should be proved to be safe and roadworthy before deployed to public road.
The working group openGENESIS drives and supports the investigations of a verifiable, understandable and not least certifiable AI. The working group will supply public and regulation authorities with necessary approaches to deal with the challenges of approval and certification of AI.

openGENESIS provides a collaboration platform for knowledge exchange among members. The members can cooperate with each other efficiently and provide the results in an open access domain. openGENESIS enables research with direct access to practice and safety relevant challenges.

Scope and Objectives

The highly challenging task to enable assessing AI for the safety critical case of autonomous driving will be addressed by global collaboration among industry, research and regulators. To equip this collaboration with the necessary framework, the openGENESIS working group will coordinate and support the activities on the following topics:

  • Develop necessary methods, tools and metrics for verification and validation of AI
  • Support the evolution of functional safety approaches for AI
  • Establish an open accessible platform for AI training and validation data sets
  • Drive the aspects and discussion of reproducibility and explainability of AI
  • Encourage and support academic research efforts within the scope of openGENESIS
  • Support a global collaboration and drive a common understanding of quality of AI
  • Maintain the scope as well as the objectives of the openGENESIS working group
  • Coordinate the development of related Eclipse Foundation projects towards an openGENESIS objective.
  • Define and manage the specifications for interfaces and functions for the working group.

Governance and Precedence

Applicable Documents

All Members must be parties to the Eclipse Foundation Membership Agreement, including the requirement set forth in Section 2.2 to follow the Bylaws and then-current policies of the Eclipse Foundation, including but not limited to the Intellectual Property and Anti-Trust Policies.

In the event of any conflict between the terms set forth in this Working Group's Charter and the Eclipse Foundation Bylaws, Membership Agreement, Eclipse Development Process, Eclipse Industry Working Group Process, or any policies of the Eclipse Foundation, the terms of the Eclipse Foundation Bylaws, Membership Agreement, process, or policy shall take precedence.

Membership

In order to participate in the openGENESIS working group, an entity must have executed the openGENESIS Participation Agreement once defined, and adhere to the requirements set forth in this Charter.

The openGENESIS working group is open at any time to all new members who meet these conditions.

There are different classes of openGENESIS working group membership - Driver Member, Development Member and Guest Member. Each of these classes is described in detail below.

Classes of openGENESIS Membership

Driver Members

Driver Members are organizations that view the openGENESIS activities as strategic to their organization. These members will invest resources to sustain and shape the activities of this working group as well as maintain the scope of openGENESIS. Driver Members include users and strategic contributors related to the technologies and results provided by the openGENESIS working group. Driver members will lead the operation of the working group, support the "openGENESIS Spotlight Projects" ("GSLP") and will act as first contact of the working group. An openGENESIS WG Driver Member must be at least a Solutions Member of the Eclipse Foundation.

Development Members

Development Members are organizations that are interested to benefit from the openGENESIS community. They will lead or participate in "openGENESIS Spotlight Projects" ("GSLP") and investigate the technical questions. They will propose and execute the GSLPs according to the processes defined by the openGENESIS working group. Development members will invest efforts to the openGENESIS Spotlight Projects ("GSLP") as defined in the proposal. An openGENESIS WG Development Member must be at least a Solutions Member of the Eclipse Foundation.

Guest Members

Guest members are organizations who have been invited for one year by the Steering Committee of openGENESIS WG. Typical Guest Members include academic entities or non-profit organizations, who want to have a closer look before deciding on their strategy. Guest Members are allowed to participate in the openGENESIS WG within the scope of their invitation. Guest Members are not allowed to become a Steering Committee Member and they have no right to vote concerning the matters of the working group. Invitations may be renewed by the Steering Committee. Guest Members are required to sign the participation agreement. An openGENESIS WG Guest Member must be at least an Associate Member of the Eclipse Foundation.

Governance

This openGENESIS working group is designed as:

  • a member driven organization,
  • a means to foster a vibrant and sustainable ecosystem through the creation and execution of openGENESIS Spotlight Projects ("GSLP"),
  • a means to organize the community of each project or component so that users and developers define the roadmap collaboratively.

In order to implement these principles, the "Steering Committee" as the sole governance body for the working group has been defined.

Steering Committee

Powers and Duties

The Steering Committee is required to:

  • Define and maintain the scope and objectives of the working group
  • Define and maintain the roadmap of the working group
  • Define and maintain the life-cycle definition of the openGENESIS Spotlight Projects ("GSLP")
  • Approve proposals to become GSLPs
  • Monitor existing GSLPs
  • Define the working group budget and fees for all membership classes for each year
  • Contribute to the acquisition of new working group members by actively engaging in community development and evangelism
  • Define services to be executed from Eclipse Foundation Management Organization ("EMO") and allocate funding for such services
  • Review this charter regularly

Composition

  • Each Driver Member of the working group has one seat on the Steering Committee.
  • One seat is allocated for Development Members. An additional seat is allocated for each additional 5 Driver Members beyond the first Driver Member.

Common Dispositions

The dispositions below apply to all governance bodies for this working group, unless otherwise specified. For all matters related to membership action, including without limitation: meetings, quorum, voting, electronic voting action without meeting, vacancy, resignation or removal, the terms set forth in Section 6 of the Eclipse Foundation Bylaws apply.

Voting

For actions (i) approving specifications for adoption; (ii) amending the terms of the working group's Participation agreement; (iii) approving or changing the name of the working group; and (iv) approving changes to annual Member contribution requirements; any such actions must be approved by no less than two-thirds (2/3) of the representatives present at a steering committee meeting.

Term and Dates of Elections

This section only applies to the Steering Committee. All representatives shall hold office until their respective successors are appointed or elected, as applicable. There shall be no prohibition on re-election or re-designation of any representative following the completion of that representative's term of office.

Elected representatives shall each serve one-year terms and shall be elected to serve from January 1 to December 31 of each calendar year, or until their respective successors are elected and qualified.

Meetings Management

All meetings may be held at any place that has been designated by resolution of the corresponding body. All meetings may be held remotely using phone calls, video calls or any other means as designated by resolution of the corresponding body.

Infrastructure and Services

The openGENESIS Working Group uses the normal infrastructure provided to Eclipse projects, including, among others, mailing lists, forums, bug trackers, source code repositories, continuous integration servers, build servers, and web sites. Additional services may be requested by the Steering Committee of the working group on demand. Cost for such services shall be covered by membership fees as set forth in this working group charter.

Community Building

The Eclipse Foundation will provide access to its network of developers to facilitate the community building and the dissemination of the openGENESIS innovations. The Eclipse Foundation will use its communication channels such as its Newsletter, Twitter, or LinkedIn channels to promote key openGENESIS events and encourage its members to join and participate in the openGENESIS working group.

Membership Fee Structure

The following table lists the annual openGENESIS working group fees payable to the Eclipse Foundation Inc.

Annual Turnover WG Fees Driver Member WG Fees Development Member WG Fees Other Members
> $250 million € 30,0001 € 02 € 02
> $100 Million <= $250 million € 30,0001 € 02 € 02
> $50 million <= $100 million € 30,0001 € 02 € 02
> $10 million <= $50 million € 30,0001 € 02 € 02
< $10 million € 30,0001 € 02 € 02
< $1 million, < 10 employees € 30,0001 € 02 € 02

1 Alternative for research facilities only: annual fees can be provided in form of annual participation services of 150 person-days/year. (A minimum qualification of master degree or higher is required for a person-day.)
2 No additional WG feespayable to the EMO are set.

Back to the top