Community
Participate
Working Groups
The PolarSys Top Level Project charter needs a refresh. Specifically: * Update to reference version 1.2 of the Standard Charter [1]; * Review and revise the mission and scope. Revision of a Top Level Project charter requires board approval. [1] https://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.2.php
I recommend that we keep this simple. e.g. The Technology TLP Charter: https://projects.eclipse.org/projects/technology/charter Let's start here: -- = Eclipse PolarSys Top-level Project Charter == Overview This charter was developed in accordance with the Eclipse Development Process and will outline the mission, scope, organization, and development process for the Eclipse PolarSys Project. This document extends the Eclipse Standard Top-Level Charter 1.2, and includes the required content and overrides which follow. It is anticipated that as the standard charter is updated, this charter will incorporate the changes and make adjustments as seen fit by the PMC, and with approval from the EMO and board of directors. == Mission Due to its strong emphasis on safety, reliability and quality, the development of embedded and critical systems is based since the beginning of its history on numerous software tools. But while the life cycle of critical and embedded systems goes from 10 years up to 80 years in the case of aircraft, the tools frequently become obsolete or disappear after less than 15, 10 or even 5 years. The Eclipse PolarSys Top-level Project has been created to take advantage of open source to bridge this gap and to foster innovation in this domain. == Scope Eclipse Polarsys covers critical and embedded systems development activities, from the early specification stage, down to the implementation and then up to verification and validation, including: * Modeling - systems, hardware and software * Code analysis - static analysis * Debugging, tracing and other integration tools * Life cycle process support tools - configuration management, change tracking, technical facts management, project reporting * Test and verification frameworks, tools targeting embedded software methods, simulation, and early validation * SoC (System on Chip) simulation and hardware logic (VHDL, SystemC, etc.) Embedded components like RTOS, middleware, etc. == Licensing All contributions to Projects under this Charter must be done according to 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 Steering Committee and the Eclipse Foundation Board of Directors. Eclipse PolarSys Projects may use the following licenses alone or in combination: EPL-2.0, BSD-3clause and Apache-2.0, and LGPL-2.1. -- I've adapted the existing mission and scope; is there anything here that needs to be changed or augmented? I've also tweaked the licensing section to make it explicit that the licenses may be used along or combined.
+1. Benoit
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
The charter updates were approved by the board of directors on December 16/2020. I've updated the charter on the website.
