|
|
| (155 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| − | == Goals and Vision ==
| + | This page was used to collaboratively work on the Polarsys Charter. |
| − | 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.
| + | Please go to the [http://www.eclipse.org/org/industry-workgroups/polarsys_charter.php official page for the Polarsys charter] |
| − |
| + | |
| − | 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.
| + | |
| − | | + | |
| − | == Membership ==
| + | |
| − | | + | |
| − | An entity must be at least a [http://www.eclipse.org/membership/become_a_member/membershipTypes.php#solutions 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 [http://www.eclipse.org/org/documents/Eclipse%20BYLAWS%202011_08_15%20Final.pdf Eclipse bylaws] and detailed in the [http://www.eclipse.org/org/documents/Eclipse%20MEMBERSHIP%20AGMT%202010_01_05%20Final.pdf 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 & products supported by Polarsys.
| + | |
| − | | + | |
| − | ===== Polarsys Strategic Member Fees =====
| + | |
| − | {|cellspacing="0" cellpadding="5"
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | !Turnover!! style="text-align: center" | Eclipse Solution<br>Membership!! style="text-align: center" |Polarsys<br>Membership!! style="text-align: center" |Total!!
| + | |
| − | |-
| + | |
| − | |>$250 million|| style="text-align: center" | $20.000 || style="text-align: center" | $30.000 || style="text-align: center" | $50.000||
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |>$100 million <= $250 million || style="text-align: center" | $15.000 || style="text-align: center" | $30.000 || style="text-align: center" | $45.000||
| + | |
| − | |-
| + | |
| − | |>$50 million <= $100 million || style="text-align: center" | $10.000 || style="text-align: center" | $30.000 || style="text-align: center" | $40.000||
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |>$10 million <= $50 million || style="text-align: center" | $7.500 || style="text-align: center" | $20.000 || style="text-align: center" | $27.500||
| + | |
| − | |-
| + | |
| − | |<$10 million || style="text-align: center" | $5.000 || style="text-align: center" | $20.000 || style="text-align: center" | $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 & products supported by Polarsys.
| + | |
| − | | + | |
| − | ===== Polarsys Solution Member Fees =====
| + | |
| − | {|cellspacing="0" cellpadding="5"
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | !Turnover!! style="text-align: center" | Eclipse Solution<br>Membership!! style="text-align: center" |Polarsys<br>Membership!! style="text-align: center" |Total!!
| + | |
| − | |-
| + | |
| − | |>$250 million|| style="text-align: center" | $20.000 || style="text-align: center" | $10.000 || style="text-align: center" | $30.000||
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |>$100 million <= $250 million || style="text-align: center" | $15.000 || style="text-align: center" | $10.000 || style="text-align: center" | $25.000||
| + | |
| − | |-
| + | |
| − | |>$50 million <= $100 million || style="text-align: center" | $10.000 || style="text-align: center" | $10.000 || style="text-align: center" | $20.000||
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |>$10 million <= $50 million || style="text-align: center" | $7.500 || style="text-align: center" | $7.500 || style="text-align: center" | $15.000||
| + | |
| − | |-
| + | |
| − | |<$10 million || style="text-align: center" | $5.000 || style="text-align: center" | $5.000 || style="text-align: center" | $10.000||
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |<$1 million & < 10 employees || style="text-align: center" | $1.500 || style="text-align: center" | $1.500 || style="text-align: center" | $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. Invitiations 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 [http://www.eclipse.org/membership/become_a_member/committer.php Eclipse Committer Membership] page.
| + | |
| − | | + | |
| − | === Polarsys Membership Summary ===
| + | |
| − | | + | |
| − | {|cellspacing="0" cellpadding="5" style="text-align: center"
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | ! !! | Polarsys Strategic Member !! Polarsys Solution Member !! Committer !! Guest !!
| + | |
| − | |-
| + | |
| − | |Member of the Steering Committee|| X ||Elected|| - || Invited
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |Member of the Architecture Board|| X ||Elected|| - ||Invited
| + | |
| − | |-
| + | |
| − | |Quality & Labelling Committee|| X ||Elected|| - ||Invited
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |Member of the Change Control Board|| X || X || - ||Invited
| + | |
| − | |-
| + | |
| − | |Host custom build on IWG infra|| X || - || - || -
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |Access to the LTS Build Infra|| X || X || - || -
| + | |
| − | |-
| + | |
| − | |IWG test and certification program|| X || X || - || -
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |Access to binary releases|| X || X || - || -
| + | |
| − | |-
| + | |
| − | |Access to qualification kits|| X || X || - || -
| + | |
| − | |- style="background:lightgrey"
| + | |
| − | |Legal review of non EPL projects|| X || X || - || X
| + | |
| − | |-
| + | |
| − | |Labelling process|| X || X || - || -
| + | |
| − | |}
| + | |
| − | | + | |
| − | === Membership qualification ===
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | === Delinquency and non payment of dues ===
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | === Termination of membership ===
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | === Reinstatment after Termination ===
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | === Assignment ===
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | === Distribution of assets upon dissolution ===
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | == 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
| + | |
| − | | + | |
| − | === 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.
| + | |
| − | | + | |
| − | === General Assembly ===
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | === 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.
| + | |
| − | | + | |
| − | === Project Management Committees ===
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | === Applicable documents ===
| + | |
| − | *As an Industrial Working Group, Polarsys follows the [http://www.eclipse.org/org/documents/Eclipse%20BYLAWS%202011_08_15%20Final.pdf Eclipse bylaws].
| + | |
| − | *Polarsys strategic & solutions members have to fulfill and accept the [http://www.eclipse.org/org/documents/Eclipse%20MEMBERSHIP%20AGMT%202010_01_05%20Final.pdf Eclipse Membership agreement].
| + | |
