The document describes the Eclipse development process. Projects go through distinct phases including pre-proposal, proposal, incubation, mature, and archived. Transitions between phases involve public reviews. The incubation phase focuses on developing the project's process, community, and technology. Projects graduate to the mature phase by demonstrating an open source process, active community, and quality technology. Projects are archived if they become inactive through lack of resources or completion.

1. Eclipse Development Process
Philippe Krief
Director, Research Relations
Eclipse Foundation Europe
Philippe.krief@eclipse-foundation.org

2. Eclipse Development Process
2017 Copyright (c) 2017, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 2
https://www.eclipse.org/projects/dev_process/development_process.php
https://www.eclipse.org/projects/handbook/
https://wiki.eclipse.org/Development_Resources

3. Project Lifecycle
• Projects go through distinct phases.
• The transitions from phase to phase are
open and transparent public reviews.
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 3
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

4. Create Project Proposal
An individual or group of individuals declares their
interest in, and rationale for, establishing a project.
• Project Name / Parent Project
• Background (Why)
• Scope
• Description:
– The introductory paragraph should clearly explain what
the is and does. Think of this as an expanded elevator
pitch.
• Why Here
• Licenses
• Initial Contribution
– Where is the code coming from?
• Project Scheduling
• Future Work (next features)
• Source Repository Type (Git / GitHub)
• People (Project lead, Committers)
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 4https://projects.eclipse.org/node/add/project-proposal

5. Project Pre-Proposal Phase
• An individual or group of individuals
declares their interest in, and rationale for,
establishing a project.
– The Eclipse Management Organization
(EMO) will assist such groups in the
preparation of a project proposal.
• The pre-proposal phase ends when the
proposal is published by EMO and
announced to the membership by the
EMO.
• Duration: 1 month
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 5

6. Proposal phase
• The proposers, in conjunction with the destination
PMC and the community, collaborate in public to
enhance, refine, and clarify the proposal.
– Mentors for the project must be identified during
this phase.
• The proposal phase ends with a creation review, or
withdrawal.
– The proposal may be withdrawn by the proposers at
any point before the start of a creation review.
– The EMO will withdraw a proposal that has been
inactive for more than six months.
• Duration: 1 month
• Followed by an IP review: 6 months 1-2 months
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 6
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

7. Initial Contribution
1. Name the initial copyright owner; this
must be a legal entity (e.g. a company
or individual). If other organizations
have contributed, include "and
others".
2. List project licenses.
3. Optionally list the names of the
contributors and the nature of their
contribution.
Your project is not a legal entity and so it is
inappropriate to list it as the copyright
owner.
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 7
• Third-Party Libraries
– All third-party libraries required by project code will have to be
checked and approved by the IP Team.
– Eclipse Orbit Project
• This project will provide a repository of bundled versions of third party
libraries that are approved for use in one or more Eclipse projects.
• Ownership
– The author of a contribution (or their employer) retains
ownership of the intellectual property contained in the
contribution.
• Naming, Branding, and Trademarks
– The Eclipse Foundation holds the trademark for all Eclipse
Projects. All project names must be approved by the Eclipse
Management Organization (EMO) either before a project is
created or before an existing project is renamed.
All source files must include a file header that
describes the copyright and license terms of the
software.

8. D5.* Deliverables
• D5.1: Project Proposals for APPSTACLE Open Source Results
– Has to be delayed until M12
– We must agree on the architecture
– We must agree on the Open Source part è Platform scope
• The Open Source part must be self-sufficient
• D5.2: First Release (0.8) of the APPSTACLE Open Source
Components
– Will be our initial contribution to the open source
– We must agreed on the brand asap è It will impact the code
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 8

9. Incubation phase
• Establish a fully-functioning open-source project.
• In this context, incubation is about developing the
process, the community, and the technology.
• Incubation is a phase rather than a place:
– A project in the incubation phase can (and should) make
releases;
– The incubation phase ends with a graduation review or a
termination review.
– Designated permanent incubator projects remain
perpetually in the incubation phase; they do not create
releases, so no reviews are required.
• Only projects that are properly identified as being in the
incubation phase may use the Parallel IP Process to
reduce IP clearance process for new contributions.
• Duration: For EU project, the duration of the project.
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 9
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

10. Committer Elections
• Meritocracy
– Define Trust.
– Nominations such as "we all know Bob, vote for him" may
work within the team, but actually harm the project’s
reputation in the larger Eclipse community: that larger
community does not know Bob and does not understand why
the project team trusts him with the source code.
• Openness
– Employment Neutral.
• Transparency
– Public and Archival Election
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 10

11. Committer Paperwork
• The Member Committer Agreement (MCA) is used
by organizations that are members of the Eclipse
Foundation to cover all of their employees who
participate in Eclipse Foundation projects as
committers.
• The Individual Committer Agreement (ICA) is used
by committers who are not covered by a Member
Committer Agreement.
• Committers covered by an Individual Committer
Agreement must document the consent of their
employer when participating in Eclipse Foundation
projects by providing an Eclipse Committer
Employer Consent Form (ECECF).
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 11

12. Mature phase
• The project team has demonstrated that they are
an open-source project with:
– an open and transparent process;
– an actively involved and growing community;
– and Eclipse-quality technology.
• The project is now a mature member of the Eclipse
community.
• Major releases continue to go through release
reviews.
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 12
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

13. Archived
• Projects that become inactive, either through
dwindling resources or by reaching their natural
conclusion, are archived.
• Projects are moved to archived status through a
termination review.
• If there is sufficient community interest in
reactivating an archived project, the project can
start again with a creation review.
• As there must be good reasons to have terminated
a project, the creation review provides a
sufficiently high bar to prove that those reasons
are no longer valid.
<date> Copyright (c) 2016, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 13
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

14. Questions?
Philippe Krief
Research Relations Director
philippe.krief@eclipse.org