Skip to main content
Jump to: navigation, search

Difference between revisions of "Polarsys/Charter"

(Hosting private R&D projects)
(Powers and Duties)
Line 483: Line 483:
 
*Ensure the technical consistency of Polarsys projects  
 
*Ensure the technical consistency of Polarsys projects  
 
*Ensure that Polarsys projects achieve VLTS objectives  
 
*Ensure that Polarsys projects achieve VLTS objectives  
*Recommand technologies  
+
*Recommend technologies  
 
*Establish technical guidelines  
 
*Establish technical guidelines  
 
*The Architecture Board validates new project proposals
 
*The Architecture Board validates new project proposals

Revision as of 05:41, 14 March 2012

FINAL DRAFT UNDER REVIEW


Contents

Goals and Vision

In demanding engineering domains - such as aerospace, defense and security, transportation, energy, healthcare or telecommunications - safety-critical and embedded system 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 system 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.

Polarsys aims at answering these needs by:

  • Providing a set of industry-friendly open source tools and components
  • Providing collaborative means to make open innovation easier
  • Fostering exchanges between academics and industrial 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
  • Mutualizing the research, development and maintenance efforts as far as possible
  • Organizing sustainable commercial services and ecosystems around those components
  • Providing the documents required to cope with certification issues
  • Recognizing projects maturity and company know-how and commitment through a Labeling process

Core domains

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

  • Modeling - systems, dardware and software
  • Code analysis (static 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, 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.

Components Management

Polarsys does not intend at re-developing components. A lot of very good solutions answering to some Polarsys needs already exist in open source. But most of the time, some 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. 2 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 users coordination and specific artifacts (patches, qualification kits, etc.).

IP Management

Following the spirit of the Eclipse Foundation, Polarsys will proceed to IP due diligence in order to provide clean open source software released under EPL or any other licenses validated by the IWG, like BSD-like and LGPL.

Membership

An entity must be at least a Solutions Member of the Eclipse Foundation and adhere to the IWG to participate to Polarsys. The Eclipse Solution Member fees appear in the tables below for convenience only: they are decided as described in the Eclipse bylaws and detailed in the Eclipse membership agreement.

Classes of membership

Strategic members

Strategic Members are organizations that view Polarsys as a strategic industrial working group and are investing resources to sustain its activities. Typical strategic members includes industrial users of the technologies and products supported by Polarsys.

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

Solution members

Solutions 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 Solution members includes services providers for the technologies and products supported by Polarsys.

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

Guests

Guests are organizations or people who have been invited for one year by the steering committee of Polarsys to participate to some aspects of the activities of the Industrial Working Group. Typical guests includes R&D partners, academic entities and potential future full fledged members who want to have an inner look before deciding of their strategy. Even if guests can be invited to a Polarsys body for some meetings, they have no right to vote. Invitations may be renewed by the steering committee.

Committers

Committer Members are individuals who through a process of meritocracy are able to contribute and commit code to their Polarsys projects. Committers may be members by virtue of working for a member organization, or may choose to complete the membership process independantly if they are not. For further explanation and details, see the Eclipse Committer Membership page.

Polarsys Membership Summary

Polarsys Strategic Member Polarsys Solution Member Committer Guest
Member of the Steering Committee X Elected - Invited
Member of the Architecture Board X Elected - Invited
Quality & Labelling Committee X Elected - Invited
Member of Change Control Boards X X - Invited
Access to the Open Source collaboration infrastructure X X X 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
Labelling process X X - -
Host private R&D projects X X - X


Services are detailed in section #Services

Delinquency and non payment of dues

In the event that a Member does not pay its annual membership dues and all compounded late fees within ninety (90) days of the invoice due date (“Dues Delinquent”), the membership of such Member shall, without further action by the Steering Committee or the General Assembly, be terminated.

Termination of membership

The membership of any Member shall terminate upon the occurrence of any one or more of the following:

Resignation
Any Member may resign from Polarsys in writing filed with the Secretary of the Eclipse Foundation. The resignation of a Member shall not relieve the Member from any payment obligations the Member may have to Polarsys as a result of obligations incurred or commitments made prior to resignation. Except as otherwise set forth in these Charter, a resigning Member shall not be entitled to receive any refund, pro rata or otherwise, of any membership fee, dues or assessments for the balance of the calendar year in which the resignation is effective. Within ten (10) days of resigning from Polarsys, a Member may appeal in writing to the Steering Committee for a pro rata refund of its annual membership dues. The appeal will specifically set forth any circumstances that the Member believes justify a refund in its case. The Steering Comittee shall decide by simple majority upon the appeal in its sole discretion at its first meeting following the appeal scheduled under Steering Committee Meetings Management.
Expulsion, Termination or Suspension
The membership of any Member may be terminated “For Cause” upon the affirmative vote of two-thirds (2/3) of the members of the Steering Committee after a hearing duly held in accordance with this Section. As used in this Section, two-thirds (2/3) vote means two-thirds (2/3) of the members of the Steering Committee exclusive of such Member’s representative on the Steering Committee only if the representative is also a representative of the Member facing expulsion or suspension (any such representative , an “Affected Representative ”). For purposes of this Section, “For Cause” shall mean the Member has materially breached the Membership Agreement or Charter and/or other related Polarsys agreements or policies, and has not cured such breach within thirty (30) days of receipt of written notice from the Eclipse Foundation.

Such determination shall be made in the sole and absolute discretion of the Steering Committee (excluding the Affected Representative). Following the determination by the Steering Committee a Member should be terminated the following procedures shall apply:

  1. A notice shall be sent by mail by prepaid, first-class or certified mail to the most recent address of such Member as shown on the Eclipse Foundation’s records, setting forth the termination and the reasons therefore. Such notice shall be sent at least fifteen (15) days before the proposed effective date of the termination.
  2. The Member being terminated shall be given an opportunity to be heard, either orally or in writing, at a hearing to be held no fewer than five (5) days before the effective date of the proposed termination. The hearing shall be held by the Steering Committee. The notice to the Member of its proposed termination shall state that such Member is entitled, upon request, to such hearing, shall state that a date, time and place of the hearing will be established upon receipt of request therefore, and shall state, that in the absence of such request, the effective date of the proposed termination.
  3. In the event that a hearing is held, then following such hearing the Steering Committee (excluding the Affected Representative) shall decide whether such Member should in fact be terminated, or sanctioned via written reprimand as determined by the Steering Committee; provided, that, any such decision to terminate or sanction such Member must be approved by a vote of two-thirds (2/3) of the Steering Committee (excluding the Affected Representative). The decision of the Steering Committee shall be final.
  4. Any action challenging a termination of membership of a Member, including any claim alleging defective notice, must be commenced within fifteen (15) days after the date of the termination.
Termination of the Eclipse Foundation Membership
The Termination of the Eclipse Foundation Membership of a Polarsys Member automatically leads to the Termination of its Polarsys Membership.

Rights on Polarsys private assets after Termination

Members terminated pursuant to Section Termination of membership loose their rights to access and use the private means and data of Polarsys after the date of the Termination. Private data of Members terminated, like test cases or custom build chains are archived & the archive sent back to their copyright holders. The private data of Members terminated can be removed from Polarsys storages fourty five (45) days after the Termination. Nevertheless, the Members terminated can request to the Steering Committee to store for two (2) years their archived private data. This request shall be sent within thirty (30) days after the Termination and can be accepted or not, on the sole discretion of the Steering Committee.

The licenses on Polarsys private assets acquired during the period of Membership of the Members terminated survives the Termination of Membership.

Reinstatment after Termination

Members terminated pursuant to Section Termination of membership may only be reinstated upon the affirmative vote of at least two-thirds (2/3) of the Steering Committee Representatives in Good Standing represented at a Steering Committee meeting at which a quorum is present.

Assignment

Upon the completion of any acquisition or merger involving a Member in which the Member is not the surviving entity, the Steering Committee, in its sole discretion, may permit such Member’s membership to be transferred to the surviving entity.

Distribution of assets upon dissolution

TBD (Trademarks, logos, private assets like qualification kits)

Services

Open Source Collaboration infrastructure

The Polarsys IWG leverages the usual Eclipse 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.

The catalog of Polarsys components is part of this collaboration infrastructure.

LTS build and test infrastructure

Additionally, Polarsys provides a specific build and test infrastructure for Long Term Support. This infrastructure enables 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 according to the Eclipse release train planning, including Service Releases SR1 and SR2.

Polarsys Long Term Support releases (post SR2) are only accessible to Polarsys member companies.

Hosting custom builds 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 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 collaborativelly 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 to check 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.

Labelling process

The Labelling process aims at rewarding the skills and investment of service providers.

The Label recognizes that service providers are able to extend or provide Long Term Support for a component.

Hosting private R&D projects

In order to promote the maturation of research prototypes and to foster open innovation, Polarsys provides the facility for hosting members' private R&D projects that may become new Polarsys components.

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 General Assembly
  • The Architecture Board
  • The Quality & Labelling Committee
  • Change Control Boards
  • Project Management Committees

Common Dispositions

The dispositions below apply to all Polarsys bodies, unless precised.

Good Standing

A representative shall be deemed to be in Good Standing, and thus eligible to vote on issues coming before the Body he participates to, 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 Secretary of the Eclipse Foundation. 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. A representative shall be immediately removed from the Body upon the termination of the membership of such representative’s Member organization in accordance with Section Termination of membership.

Voting

Super Majority

For actions (i) amending the terms of the Charter of Polarsys; (ii) amending the terms of the Polarsys Membership 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 General Assembly meeting at which a quorum is present.

Simple Majority

For all other actions not specified by the section Super Majority above, such actions must be approved by no less than a simple majority of those representatives in Good Standing represented at a Body meeting at which a quorum is present.

Quorum

Unless otherwise provided herein, a simple majority of the representatives in Good Standing shall be necessary to constitute a quorum for the transaction of business, except that when the number of representatives constituting the Body shall be an even number, one-half of the representatives in Good Standing shall constitute a quorum. Vacant seats count in the quorum.

Electronic Voting

Electronic voting may be used in both meetings of the Body and the sollicitation of written consents as follows:

  1. Meetings: For purposes of soliciting electronic votes in connection with a meeting of the Body at which a quorum was present, the requisite number of votes that would have been required at such meeting to pass an action shall be required to pass an action via this electronic voting provision. Only those representatives in attendance of the meeting shall be permitted to vote with respect to this Section. The deadline for receipt of electronic votes with respect to any such vote shall be no sooner than two (2) weeks from the date of the meeting, as announced prior to adjournment of such meeting.
  2. Action without meeting: For purposes of taking action without a meeting, solicitation via electronic balloting and voting shall be permitted hereunder. Such procedure shall be initiated by the electronic distribution of ballots and all related materials for consideration by the Body to all of the representatives in Good Standing at the time of such distribution. Thereafter, such representatives shall be permitted to cast their votes electronically in response to the distributed ballots. The deadline for receipt of such electronic votes cast by the representatives shall be no less than two (2) weeks from the date of mailing of the balloting materials, as set forth therein.

Vacancies

This section only applies to the Steering Committee, the Architecture Board and the Quality and Labelling Committee.

A vacancy or vacancies shall be deemed to exist (i) in the case of the death or the resignation or removal of any representative (ii) if the authorized number of representative is increased without election or appointment, as applicable, of the additional representative so provided for; or (iii) in the case of failure at any time to elect or appoint, as applicable, the full number of authorized representative. Any vacancy of a Body seat appointed shall be filled within three (3) weeks of the vacancy by the Member whose Body seat has been vacated. A vacancy of a Body seat held by an elected representative shall be filled by the Body appointing a representative from nominees proffered by the members of such class until the next annual election. In no event shall the failure of any Member or class of members to elect or appoint, as applicable, a new representative to such vacant Body seat prohibit the Body from meeting and conducting business.

Term and Dates of elections

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

Strategic Members

Strategic Members Representatives shall serve in such capacity until the earlier of 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.

Resignation and Removal

Resignation

Any representative may resign at any time by giving written notice to the Body in which he sits. A resignation is effective upon the date provided for in the notice. Once delivered, a notice of resignation is irrevocable unless permitted to be withdrawn by the Body prior to its effectiveness.

Removal

Any elected representative, as applicable, may be removed without cause at a special meeting called for that purpose by the members of the class that appointed such representative. Such representative(s) may be removed hereunder only by the affirmative vote of two-thirds (2/3) of the members of the class that appointed such representative represented at a special meeting at which a quorum is present. Appointed representatives may only be removed without cause by their respective appointer Member organizations.

In the event the Member appointing a representative is in Default or Dues Delinquent (as set forth in Section Delinquency and non payment of dues), such representative shall be removed from the Body, without further action by the Body.

Meetings 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 mean 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 Section #Quorum 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 thereat has conferred with his or her respective Member organization as set forth in Section #Voting 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 the charter and propose updates to the General Assembly
  • Propose the budget and fees each year to the General Assembly
  • Define & Follow maketing and communication activities
  • Invite guest members

Composition

  • 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 among its members a chairman and a spokeperson 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.

Meetings Management

The Steering Committee meets at least twice a year.

General Assembly

Powers and Duties

  • Approve changing the name of Polarsys.
  • Vote amendments to the Polarsys Membership agreement as proposed by the Steering Committee.
  • Vote amendments to the charter as proposed by the Steering Committee.
  • Vote the budget and fees each year as proposed by the Steering Committee.

Composition

Each Strategic and Solution Member of the IWG has a seat on the General Assembly.

Meetings Management

The General Assembly meets at least once a year.

Architecture Board

Powers and Duties

Architecture Board members are required to:

  • Ensure the technical consistency of Polarsys projects
  • Ensure that Polarsys projects achieve VLTS objectives
  • Recommend technologies
  • Establish technical guidelines
  • The Architecture Board validates new project proposals

Composition

  • 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. This chairman is elected among the members of the Architecture Board. 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.

Meetings Management

The Architecture Board meets at least twice a year.

The Quality and Labelling Committee

Powers and Duties

The Quality and 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

Composition

  • Each strategic member of the IWG has a seat on the Quality and 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. This chairman is elected among the members of the Quality & Labelling 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.

Meetings Management

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

Change Control Boards

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

Powers and Duties

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.
  • Ensure the relationships with the technical team of the project.

Composition

  • Each strategic or solution member of the IWG can have a seat on the Change Control Board.
  • Each Change Control Board elects a chairman who will represent it to the Architecture Board. This chairman is elected among the members of each Change Control Board. 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.

Meetings Management

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

Project Management Committees

Polarsys PMC follows the same rules than plain Eclipse PMC.

Applicable documents

Back to the top