Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Polarsys/Charter"

(Polarsys Governance and Member Participation)
m
Line 180: Line 180:
 
* Each Change Control Board elects one of its members to the Architecture Board.
 
* Each Change Control Board elects one of its members to the Architecture Board.
 
* The Change Control Board elects a chairman who represents the projects.
 
* The Change Control Board elects a chairman who represents the projects.
 
 
[[Category:Eclipse IWG]]
 

Revision as of 11:24, 13 December 2011

Goals and Vision

The goal of the Polarsys group is to collaboratively define, build and maintain open source tools for safety-critical and embedded system development in demanding engineering domains, such as aerospace, defense and security, transportation, energy, healthcare, telecommunications.

These domains typically require maintenance of tool chains for the very long term – from 30 to up to 50 to 70 years in some cases – which create some very unique issues. Another characteristic of the working group is to address material for qualification processes – like in the DO 178 for Aircraft or ISO 26262 for Automotive.

Additionally, Polarsys intends to foster exchanges between academics and industrial partners in these domains and manage the maturity of tools from early research prototypes to the obsolescence of tools.

To implement this vision, the IWG group and the Eclipse Foundation will collaborate to provide services and to:

  • Maintain the infrastructure required for the hosting of IWG projects, including software repositories, software build and test facilities.
  • Proceed to IP due diligence in order to provide clean open source software released under EPL or other licenses validated by the IWG like BSD-like and LGPL.
  • Define the software tools to be contained in each release of the tool chains (with specific roadmaps and release trains).
  • Create a labelling process to recognize projects maturity and companies know-how and commitment .
  • Create a software quality assessment kit to define the maturity level of each component.
  • Digitally sign certified software releases made available under the IWG banner.
  • Make those binary software releases available only to the members of IWG.

Core domains

Polarsys focuses on techniques and tools to fulfill the Polarsys goal and vision, and mainly on:

  • System, Hardware and Software Modeling
  • Code analysis (static code analysis)
  • Debugging, tracing and other integration tools
  • Transversal process support tools : Configuration Management, Change tracking, Technical facts management, Project reporting
  • Test and verification tools targeting embedded software methods, simulation and early validation
  • Embedded components (RTOS, Middleware, ...)
  • System on Chip simulation and Hardware logic (VHDL, SystemC, ...)

Other domain specific techniques and tools can be proposed for acceptance by the IWG steering committee.

Connections with other Eclipse Working Groups

The Polarsys IWG may have connections with Modeling working Group and Auto IWG

Additionaly, Polarsys shares the Long Term Support Infrastructure with the LTS IWG

Connections with other standards and industry groups

The working group includes processes to follow, improve and propose standards in coordination with standardization bodies.

Connections already exist with OMG on standards like UML, SysML, OCL, ...

Membership

An entity must be at least Solutions Members of the Eclipse Foundation and adhere to the IWG to participate to the Polarsys IWG.

Here is a proposal for the Polarsys IWG fee structure. Polarsys IWG Solutions member fees follow the same size categories than the Eclipse Solution Membership.

Polarsys Strategic Member Fees

Turnover Eclipse Solution 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

Polarsys Solution Member Fees

Turnover Eclipse Solution 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

Polarsys Governance and Member Participation

Polarsys Strategic Member Polarsys Solution Member Academics
Member of the Steering Committee X Elected Invited
Member of the Architecture Board X Elected Invited
Quality & Labelling Committee X Elected Invited
Member of the Change Control Board X X Invited
Host custom build on IWG infra X - -
Access to the LTS Build Infra X X -
IWG test and certification program X X X
Access to binary releases X X -
Access to qualification kits X X X
Legal review of non EPL projects X X X
Labelling process X X -

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:

  • The Steering Committee
  • The Architecture Board
  • The Quality & Labelling Committee
  • Change Control Boards

Steering Committee

Steering committee members are required to:

  • Define the strategy of the IWG
  • Define the global roadmap
  • Discuss and update the charter
  • Vote fees amount each year
  • Define & Follow maketing and communication activities
  • Invite guest members
  • Each strategic member of the IWG has a seat on the Steering Committee.
  • At least one seat is allocated to Solutions Members. An additional seat on the Committee shall be allocated to the Solutions Members for every additional five (5) seats beyond one (1) allocated to Strategic Members. Solutions Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.
  • The Steering Committee elects a chairman and a spokeperson who will represent the IWG each year.
  • The Steering Committee meets twice a year.

Architecture Board

Architecture Board members are required to:

  • Ensure the technical consistency of Polarsys projects
  • Ensure that Polarsys projects achieve VLTS objectives
  • Recommand technologies
  • Establish technical guidelines
  • The Architecture Board validates new project proposals
  • Each strategic member of the IWG has a seat on the Architecture Board.
  • Each Change Control Board elects one of its members to the Architecture Board.
  • The Architecture Board elects a chairman who reports to the Steering Committee.
  • The Architecture Board meets at least twice a year.

The Quality & Labelling Committee

The Quality & Labelling Committee members are required to:

  • Ensure the consistency of Labelling process and attribute maturity labels (see Labelling 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
  • Each strategic member of the IWG has a seat on the Quality & Labelling Committee.
  • At least one seat is allocated to Solutions Members. An additional seat on the Committee shall be allocated to the Solutions Members for every additional five (5) seats beyond one (1) allocated to Strategic Members. Solutions Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.
  • The Quality & Labelling Committee elects a chairman who reports to the Steering Committee.
  • The Quality & Labelling Committee meets at least twice a year.

Change Control Boards

Each component or release train (bundle) in the IWG are led by a Change Control Board.

Change Control Boards members are required to:

  • Instantiate IWG global roadmaps for the project
  • Apply the Architecture Board recommendations
  • Plan and arbitrate defects fixes and improvements implementation.
  • Manage the daily life of the projects or ensure the relationships with the technical team of the project when this one is managed outside of the IWG.
  • Manage technical infrastructure and rights for the project
  • Each strategic member of the IWG has a seat on the Change Control Board.
  • Each Change Control Board elects one of its members to the Architecture Board.
  • The Change Control Board elects a chairman who represents the projects.

Back to the top