Polarsys Industry Working Group Charter


June 12, 2012

Goals and Vision

In demanding engineering domains – such as aerospace, defense and security, transportation, energy, health care or telecommunications – safety-critical and embedded systems development must meet several important requirements.

  • Innovation: Ensuring the highest levels of safety, reliability, service, and performance implies a continuous effort of research and development, not only with the products themselves but also with the development methods and tools.
  • Computer Assistance and Automation: The numerous and complex operations required to develop and maintain industrial systems imply a high level of automation based on software tools.
  • Certification: From DO178 to ISO26262 and ECSS 40, the development of safety-critical and embedded systems has to comply with strict regulations impacting not only the final product, but also the development process and the tools used to build it.
  • Very Long Term Support: Typical products have life cycles from 30 to 70 years. During this time, the tool chains must remain operational.

The Polarsys Industry Working Group (IWG) aims at answering these needs by:

  • Providing a set of industry-friendly open source tools, frameworks, and components
  • Providing collaborative means to make open innovation easier
  • Fostering exchanges between academics and industry partners
  • Operating dedicated software repositories, build chains, test facilities, etc.
  • Managing the quality and maturity of tools and components from early research prototypes through obsolescence
  • Ensuring open innovation through the sharing of the research, development, and maintenance efforts as far as possible
  • Organizing sustainable commercial services and ecosystems around the components
  • Providing the documents and qualification kits required for certification
  • Recognizing project maturity and company know-how and commitment through a branding process that is available only to Polarsys IWG Member organizations

Core Domains

Polarsys focuses on techniques, frameworks and tools to fulfill its goal and vision, including

  • Modeling – systems, hardware and software Code analysis (static analysis)
  • Debugging, tracing and other integration tools
  • Lifecycle process support tools – configuration management, change tracking, technical facts management, project reporting
  • Test and verification frameworks and tools targeting embedded software methods, simulation, and early validation
  • Embedded components (RTOS, middleware, etc.)
  • SoC (System on Chip) simulation and hardware logic (VHDL, SystemC, etc.)

Other domain specific techniques and tools may be proposed for acceptance by the IWG Steering Committee.

Component Management

Polarsys does not intend to systematically re-develop components. A lot of very good solutions answering some Polarsys needs already exist in open source. But most of the time, specific issues like durability or certification are not taken into account. In this case, Polarsys plays its part by completing components assets, setting up specific support, and coordinating development and support. Two kinds of projects are therefore supported in Polarsys:

Hosted Projects

The technical artifacts are hosted by Polarsys.

Coordination Projects

Most of the technical artifacts are hosted elsewhere, and Polarsys focuses on user coordination and specific artifacts (patches, qualification kits, etc.).

Governance and Precedence

Applicable Documents

All Polarsys Members must be parties to the Eclipse Membership Agreement, including the requirement set forth in Section 2.2 to follow the Bylaws and then-current policies of the Eclipse Foundation. In the event of any conflict between the terms set forth in this Polarsys Industry Working Group 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.

IP Management

The Intellectual Property Policy of the Eclipse Foundation will apply to all Polarsys activities. Polarsys will follow the Eclipse Foundation's IP due diligence process in order to provide clean open source software released under EPL or any other licenses approved by the IWG and the Eclipse Foundation Board of Directors, such as BSD-like and LGPL.

Development Process

The Eclipse Foundation Development Process will apply to all Polarsys open source projects. In particular, the project lifecycle model and review process will be followed by all Polarsys open source projects.

Membership

In order to participate in Polarsys, an entity must be at least a Solutions Member of the Eclipse Foundation, have executed the IWG Participation Agreement, and adhere to the requirements set forth in this charter. The Eclipse Solutions Member fees appear in the tables below for convenience only; they are determined as described in the Eclipse Bylaws and detailed in the Eclipse Membership Agreement.

Classes of Membership

Steering Committee Members

Steering Committee members are organizations that view Polarsys as a strategic industry working group and are investing resources to sustain its activities. Typical Steering Committee members include industry users of the technologies and projects supported by Polarsys.

Polarsys Steering Committee Member Fees

Turnover

Eclipse Solutions
Membership

Polarsys
Membership

Total

>$250 million

$20,000

$30,000

$50,000

>$100 million <= $250 million

$15,000

$30,000

$45,000

>$50 million <= $100 million

$10,000

$30,000

$40,000

>$10 million <= $50 million

$7,500

$20,000

$27,500

<$10 million

$5,000

$20,000

$25,000

Participant Members

Participant members are organizations that view Polarsys as an important part of their corporate and product strategy and offer products and services based on, or with, Polarsys. These organizations want to participate in the development of the Polarsys ecosystem. Typical Participant members are services providers for the technologies and products supported by Polarsys.

Polarsys Participant Member Fees

Turnover

Eclipse Solutions
Membership

Polarsys
Membership

Total

>$250 million

$20,000

$10,000

$30,000

>$100 million <= $250 million

$15,000

$10,000

$25,000

>$50 million <= $100 million

$10,000

$10,000

$20,000

>$10 million <= $50 million

$7,500

$7,500

$15,000

<$10 million

$5,000

$5,000

$10,000

<$1 million & < 10 employees

$1,500

$1,500

$3,000

Guests

Guests are organizations who have been invited for one year by the Steering Committee of Polarsys to participate in some aspects of the activities of the Industry Working Group. Typical guests includes R&D partners, academic entities, and potential future full-fledged members who want to have an closer look before deciding on their strategy. When guests are invited to a Polarsys body for meetings, they have no right to vote. Invitations may be renewed by the Steering Committee. Guests are required to sign a participation agreement.

Committers

Committer members are individuals who through a process of meritocracy defined by the Eclipse Development Process are able to contribute and commit code to Polarsys projects for which they are responsible. Committers may be members by virtue of working for a member organization, or may choose to complete the membership process independently. For further explanation and details, see the Eclipse Committer Membership page.

Polarsys Membership Summary

Polarsys Steering Committee Member

Polarsys Solutions Member

Committer

Guest

Member of the Steering Committee

X

Elected

-

Invited

Member of the Architecture Committee

X

Elected

-

Invited

Quality and Branding Committee

X

Elected

-

Invited

Member of Project Planning Committees

X

X

-

Invited

Access to the open collaboration infrastructure

X

X

X

X

Write Access to open source code repositories

-

-

X

-

Access to the LTS Build Infrastructure

X

X

-

-

Access to LTS binary releases

X

X

-

-

Host custom build on IWG infrastructure

X

-

-

-

Maturity assessment program

X

X

-

-

Access to qualification kits

X

X

-

-

IP due diligence

X

X

X

X

Branding process

X

X

-

-

Host private R&D projects

X

X

-

X

Services are detailed in the Services section.

All matters related to membership in the Eclipse Foundation and the Polarsys IWG will be governed by the Eclipse Foundation Bylaws, Membership Agreement, and Eclipse Industry Working Group Process. These matters include, without limitation delinquency, payment of dues, termination, resignation, reinstatement, assignment, and the distribution of assets upon dissolution.

Members who resign or otherwise terminate their membership in the Polarsys IWG lose their rights to access and use the private assets and data of Polarsys after the date of the termination.

The private assets of terminated members, such as test cases or custom build chains, shall be archived and the archive returned to the terminated member. The private assets of members terminated can be removed from Polarsys storages forty-five (45) days after the termination. Nevertheless, the terminated member can request to the Steering Committee that their archived private assets be stored for two (2) years. This request shall be sent within thirty (30) days after the termination and is accepted at the sole discretion of the Steering Committee.

The survival of any licenses to Polarsys private assets acquired by a member during the period of membership shall be as specified in the license.

Services

Collaboration Infrastructure

The Polarsys IWG leverages the usual Eclipse open source collaboration infrastructure. As such, source code repositories, Bugzilla, wikis, forums, project mailing lists, and other services provided as the open source collaboration infrastructure are publicly visible. Committers have write access to this infrastructure, and as such have the rights and obligations as set forth in the Eclipse Development Process and the various Eclipse committer agreements. The catalog of Polarsys components is part of this collaboration infrastructure.

In addition, a private, members-only collaboration infrastructure for the exclusive use of Members of the Polarsys Industry Working Group will be provided. Access rights to, and the licensing terms for, this infrastructure will be determinted by the Steering Committee, with the approval of the EMO.

LTS Build and Test Infrastructure

Additionally, Polarsys aims to provide a specific build and test infrastructure for long term support. This infrastructure will enable build and test of specific long term releases for a duration of up to 10 years in a first version, and up to 40 years with an adequate usage of virtualization technologies.

Access to LTS Binary Releases

Polarsys will produce public binary releases modeled after the Eclipse release train process, including Service Releases SR1 and SR2.

Polarsys long term support releases (post SR2) are only accessible to Polarsys member companies. Such binary code may not be redistributed unless it is integrated into, or updates, a commercial software product or custom-developed software, and is distributed pursuant to an Object Code License.

Hosting Custom Build on the Polarsys Infrastructure

This service gives the capability of using the Polarsys test and build infrastructure in order to create member-specific bundles. These bundles can create another combination of Polarsys components and are private to the member who defines and uses them.

Maturity Assessment Program

Maturity assessment is at the core of the Polarsys IWG's goal of providing industrial quality tools. It consists of the evaluation of component maturity according to a classification similar to TRL levels. This evaluation is done collaboratively by component developers, component integrators, and component users.

Access to Qualification Kits

Many Polarsys components are used in the development of certified and qualified embedded software. As such, specific documentation is needed and is adapted in the context of a given certification process. These documents, like development plans and test plans, are part of the Polarsys qualification kits available for the components.

IP Due Diligence

IP due diligence is necessary for verifying that the committers have the right to open-source the code they put in Polarsys. It is also necessary to check that the different integrated components have compatible licenses. This is even more important in Polarsys, as we allow not only EPL licensed components, but also BSD-style licensed components and LGPL licensed components.

Branding Process

The branding process aims at rewarding the skills and investment of service providers. The brand recognizes that service providers are able to extend or provide long term support for a component.

Hosting Private Projects

In order to promote the maturation of research prototypes and to foster open innovation, Polarsys provides the ability to host members' time-limited private projects that may become new Polarsys components. Private projects may only be initiated by Steering Committee members. The Steering Committee, with the approval of the EMO, will establish the licensing requirements for private projects. Guests may participate in private projects at the request of the Steering Committee.

Governance

Polarsys is designed as

  • A user driven organization
  • A means to foster a vibrant and sustainable ecosystem of components and service providers
  • 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 following governance bodies have been defined (each a "body"):

  • The Steering Committee
  • The General Assembly
  • The Architecture Committee
  • The Quality and Branding Committee
  • Project Planning Committees
  • Project Management Committees

Common Dispositions

The dispositions below apply to all Polarsys bodies, 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.

Good Standing

A representative shall be deemed to be in good standing, and thus eligible to vote on issues coming before the body he in which he participates, if the representative has attended (in person or telephonically) a minimum of three (3) of the last four (4) body meetings (if there have been at least four meetings). Appointed representatives on the body may be replaced by the member organization they are representing at any time by providing written notice to the Steering Committee. In the event a body member is unavailable to attend or participate in a meeting of the body, he or she may send a representative and may vote by proxy, which shall be included in determining whether the representative is in good standing. As per the Eclipse Foundation Bylaws, a representative shall be immediately removed from the body upon the termination of the membership of such representative’s member organization.

Voting


Super Majority

For actions (i) requesting that the Eclipse Foundation Board of Directors approve an additional distribution license for Polarsys projects; (ii) amending the terms of the Polarsys Participation Agreement; (iii) approving or changing the name of Polarsys; (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 in good standing represented at a Steering Committee meeting at which a quorum is present.

Term and Dates of Elections

This section only applies to the Steering Committee, the Architecture Committee and the Quality and Branding 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.


Steering Committee Members

Steering Committee member representatives shall serve in such capacity until their removal by their respective appointing member organization or as otherwise provided for in this charter.


Elected Representatives

Elected representatives shall each serve one-year terms and shall be elected to serve from April 1 to March 31 of each calendar year, or until their respective successors are elected and qualified, or as otherwise provided for in this charter. Procedures governing elections of representatives may be established pursuant to resolutions of the Steering Committee provided that such resolutions are not inconsistent with any provision of this charter.

Meeting Management


Place of Meetings

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


Regular Meetings

No body meeting will be deemed to have been validly held unless a notice of same has been provided to each of the representative in good standing at least thirty (30) calendar days prior to such meeting, which notice will identify all potential actions to be undertaken by the body at the body meeting. No representative will be intentionally excluded from body meetings and all representatives shall receive notice of the meeting as specified above; however, body meetings need not be delayed or rescheduled merely because one or more of the representatives cannot attend or participate so long as at least a quorum of the body (as defined in the Common Dispositions section above) is represented at the body meeting. Electronic voting shall be permitted in conjunction with any and all meetings of the body, the subject matter of which requires a vote of the body to be delayed until each such representative in attendance has conferred with his or her respective member organization as set forth in the Voting section above.


Actions

The body may undertake an action only if it was identified in a body meeting notice or otherwise identified in a notice of special meeting.

Invitations

The body may invite any Polarsys member to any of its meetings. These invited attendees have no right of vote.

Steering Committee

Powers and Duties

Steering committee members are required to

  • Define the strategy of the IWG
  • Define the global roadmap
  • Discuss and amend the charter and the participation agreement
  • Define the budget and fees each year
  • Define and follow maketing and communication activities
  • Invite guest members

Composition

  • Each Steering Committee member of the IWG has a seat on the Steering Committee.
  • At least one seat is allocated to participant members. An additional seat on the committee shall be allocated to the participant members for every additional five (5) seats beyond one (1) allocated to Steering Committee members. Participant member seats are allocated following the Eclipse "single transferable vote", as defined in the Eclipse Bylaws.
  • The Steering Committee elects among its members a chairman who will represent the IWG. They will serve from April 1 to March 31 of each calendar year, or until their respective successors are elected and qualified, or as otherwise provided for in this charter.

Meeting Management

The Steering Committee meets at least twice a year.

General Assembly

Powers and Duties

Approve changing the name of Polarsys.

Composition

Each Steering Committee and Participant Member of the IWG has a seat on the General Assembly.

Meeting Management

The General Assembly meets at least once a year.

Architecture Committee

Powers and Duties

Architecture Committee members are required to

  • Ensure the technical consistency of Polarsys projects
  • Ensure that Polarsys projects achieve VLTS objectives
  • Recommend technologies
  • Establish technical guidelines
  • Validate new project proposals

Composition

  • Each Steering Committee Member of the IWG has a seat on the Architecture Committee.
  • Each Project Planning Committee elects one of its members to the Architecture Committee.
  • The Architecture Committee elects a chairman who reports to the Steering Committee. This chairman is elected among the members of the Architecture Committee. He will serves from April 1 to March 31 of each calendar year, or until his successor is elected and qualified, or as otherwise provided for in this charter.

Meeting Management

The Architecture Committee meets at least twice a year.

The Quality and Branding Committee

Powers and Duties

The Quality and Branding Committee members are required to

  • Ensure the consistency of the branding process and attribute maturity labels (see the Branding Charter Wiki Page)
  • Define the IWG quality kit and maturity process
  • Validate that the projects conform to the IWG quality kit
  • Validate that the projects apply the IP process

Composition

  • Each Steering Committee member of the IWG has a seat on the Quality and Branding Committee.
  • At least one seat is allocated to participant members. An additional seat on the committee shall be allocated to the participant members for every additional five (5) seats beyond one (1) allocated to Steering Committee members. Participant member seats are allocated following the Eclipse "single transferable vote", as defined in the Eclipse Bylaws.
  • The Quality and Branding Committee elects a chairman who reports to the Steering Committee. This chairman is elected among the members of the Quality and Branding Committee. He will serves from April 1 to March 31 of each calendar year, or until his successor is elected and qualified, or as otherwise provided for in this charter.

Meeting Management

The Quality and Branding Committee meets at least twice a year.

Project Planning Committees

Each component or release train (bundle) in the IWG is driven by a Project Planning Committee.

Powers and Duties

Project Planning Committee members are required to

  • Instantiate IWG global roadmaps for the project
  • Apply the Architecture Committee recommendations
  • Plan and arbitrate defects fixes and improvements implementation
  • Ensure the relationships with the technical team of the project

Composition

  • Each Steering Committee or participant member of the IWG can have a seat on the Project Planning Committee.
  • Each Project Planning Committee elects a chairman who will represent it to the Architecture Committee. This chairman is elected among the members of each Project Planning Committee. He will serves from April 1 to March 31 of each calendar year, or until his successor is elected and qualified, or as otherwise provided for in this charter.

Meeting Management

The Project Planning Committees meet at least twice a year.

Project Management Committees

Any Project Management Committee (PMC) established by Polarsys shall be governed by the Eclipse Development Process.