blob: e61101c4b1f1b6404520475726855244d66db06a [file] [log] [blame]
This document is provided as a template along with some guidance for creating
your project proposal. This is just a template. Feel free to change it as
you see fit (add sections, remove section). We feel, however, that the
suggestions represented in this document represent the reasonable minimum
amount of information to move forward.
Please keep the formatting in this document simple. Please do not edit
this document in Microsoft Word as it adds huge piles of markup that make
it difficult to restyle.
More information is available here:
Direct any questions about this template to
Include the title here. We will parse it out of here and include it on the
rendered webpage. Do not duplicate the title within the text of your page.
<title>3P - PolarSys Packaging Project</title>
We make use of the 'classic' HTML Definition List (dl) tag to specify
committers. I know... you haven't seen this tag in a long while...
dt {
display: list-item;
list-style-position: outside;
margin-left: 16px;
dd {
margin-left: 25px;
margin-bottom: 5px;
The PolarSys Packaging Project, or 3P for short, is a proposed open
source project under the <a
Top-Level Project</a>.
The communication channel must be specified. Typically, this is the
"Proposals" forum. In general, you don't need to change this.
This proposal is in the Project Proposal Phase (as defined in the
Eclipse Development Process) and is written to declare its intent and
scope. We solicit additional participation and input from the PolarSys
and Eclipse communities. Please send all feedback to the <a
Proposals</a> Forum.
Optionally provide the background that has lead you to creating this project.
<p>PolarSys is an Industry Working Group aiming to fulfill the
embedded / critical system industries' requirements on tools and
components. While its industrial users are interested in individual
technological components as building blocks, the main value for them
is in integrated packages gathering complete stacks of functions for
given activities (e.g. System Modeling, Requirement Management, etc.).</p>
All projects must have a well-defined scope. Describe, concisely, what
is in-scope and (optionally) what is out-of-scope. An Eclipse project
cannot have an open-ended scope.
<p>3P provides packages, platforms, and installers for
functional stacks identified as required by the Polarsys Architecture
Committee. Those stacks will be based on components originating from
Eclipse and PolarSys projects.</p>
Describe the project here. Be concise, but provide enough information that
somebody who doesn't already know very much about your project idea or domain
has at least a fighting chance of understanding its purpose.
<p>The objectives of 3P are to:</p>
<li>Provide Polarsys-specific packages which address requirements
of embedded / critical software and system development. The initial
bundle is a Model Driven configuration of Eclipse covering most
development stages (specification, design, implementation). More
packages will come later.</li>
<li>Provide installers that improves the install experience.</li>
<li>Provide platforms that keep packages building simple. These
building platforms cover Eclipse packages - as far as possible using
CBI or EPP - but also packages based on other technologies like C/C++,
CAML, etc.</li>
<li>Provide build platforms compatible with Very Long Term
As for PolarSys domains identified in the Top-Level project, 3P
belongs to <em>Build Continuous Integration</em> of the Polarsys
Service Framework.
<h2>Why PolarSys?</h2>
Answer these two questions: What value does this project bring to the Eclipse
community? What value do you expect to obtain from hosting your project at Eclipse?
What value do you get by having your project at Eclipse over and above the value
of hosting at Eclipse Labs?
<p>This project is a basement of PolarSys infrastructure. As such,
it needs to be hosted by the IWG.</p>
<h2>Initial Contribution</h2>
<h2>Legal Issues</h2>
<p>Each package, installer and build platform provided by 3P has
its own licensing policy, complying with the PolarSys rules.</p>
List any initial committers that should be provisioned along with the
new project. Include affiliation, but do not include email addresses at
this point.
<p>The following individuals are proposed as initial committers to
the project:</p>
<dt>Pierre Gaufillet, Airbus</dt>
Pierre is experienced in building Eclipse packages within Airbus for
years. He is also involved in <a href="">TOPCASED</a>
since 2005. He participates in defining and maintaining 3P building
platforms and PolarSys packages. Pierre is a member of PolarSys
Architecture Committee, and is proposed as Project lead.
<dt>Matthieu Helleboid, Thales</dt>
<dd>Matthieu is a committer on the EGF project. He participates
in defining and maintaining 3P building platforms and PolarSys
<dt>Benoit Langlois, Thales</dt>
<dd>Benoit is a committer on the EGF project where he has made
significant contributions. He participates in defining and
maintaining 3P building platforms and PolarSys packages. Benoit is a
member of PolarSys Architecture Committee.</dd>
<dt>Mélanie Bats, Obeo</dt>
<dd>Mélanie will contribute to the smooth integration of Obeo projects
in the Polarsys bundles,</dd>
<p>We welcome additional committers and contributions.</p>
Describe any initial contributions of code that will be brought to the
project. If there is no existing code, just remove this section.
New Eclipse projects require a minimum of two mentors from the Architecture
Council. You need to identify two mentors before the project is created. The
proposal can be posted before this section is filled in (it's a little easier
to find a mentor when the proposal itself is public).
<p>The following Architecture Council members mentor this project:</p>
<li>C&eacute;dric Brun, Obeo</li>
<li>Benjamin Cab&eacute;, Sierra Wireless</li>
<h2>Interested Parties</h2>
Provide a list of individuals, organisations, companies, and other Eclipse
projects that are interested in this project. This list will provide some
insight into who your project's community will ultimately include. Where
possible, include affiliations. Do not include email addresses.
<p>The following individuals, organisations, companies and projects
have expressed interest in this project:</p>
<li>Pierre Gaufillet, Airbus</li>
<li>Alain Rossignol, Astrium</li>
<li>Dominique Toupin, Ericsson</li>
<li>Benoit Langlois, Thales</li>
<li>Rapha&euml;l Faudou, ATOS</li>
<h2>Project Scheduling</h2>
Describe, in rough terms, what the basic scheduling of the project will
be. You might, for example, include an indication of when an initial contribution
should be expected, when your first build will be ready, etc. Exact
dates are not required.
<li>End of 2012: basic building platform based on Eclipse CBI for
PolarSys IDE 0.1, based on Juno SR1</li>
<li>April 2013: releasing PolarSys IDE milestone 1.0M1</li>
<li>July 2013: releasing PolarSys IDE milesonte 1.0M2</li>
<li>Oct 2013: PolarSys IDE 1.0, aligned on Kepler, platforms:
Windows (64 bits), Linux (64 bits), MAC, Solaris</li>
Forthcoming releases of PolarSys IDE will be aligned on the planning of
the Eclipse release train.
<h2>Changes to this Document</h2>
List any changes that have occurred in the document here.
You only need to document changes that have occurred after the document
has been posted live for the community to view and comment.
<td>Added Obeo as an interested party, and Mélanie Bats as a committer.</td>
<td>Document created</td>
<p />