This document outlines a proposal for an Eclipse project called AGILE. The proposal discusses establishing an open source IoT platform hosted by the Eclipse Foundation. The first year would involve formalizing the platform's scope and connections to other projects, and creating the initial AGILE open source project. Subsequent time would be spent publishing new components, improving existing ones, and growing the community. The document reviews Eclipse's development process phases and provides a template for project proposals, highlighting what should be included such as background, scope, description, licensing, and key people involved.

1. T7.2 – Eclipse Project Proposal
LEADER: ECLIPSE FOUNDATION EUROPE
INVOLVED PARTNERS: CREATE-NET, CANONICAL
AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany

2. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Eclipse Development Process
https://www.eclipse.org/projects/dev_process/development_process.php
Provide an Open Source platform hosted by the Eclipse Foundation, inside the IoT
working group. This task will coordinate and contribute to the creation and
development of the open source community.
• First year will be dedicated:
• to the formalization of the perimeter of the open source platform including
connections with other existing open source projects,
• to create the AGILE open source project to publish the initial contribution.
• The remaining time of the project will be dedicated:
• to publish new component,
• to improve the existing components and
• to grow the community through the project.
All the necessary actions to prepare for long term sustainability of the AGILE
project (including Intellectual Property analysis for the code and dependencies,
best practices for build and test, …) will be also be addressed and coordinated by
this task.
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review
Eclipse
Development Process

3. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Eclipse Development Process
- 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.
è We are in this phase, for now…
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

4. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Eclipse Development Process
- Proposal phase
◦ The proposers, in conjunction with the destination Project
Management Committee (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.
è We are delayed. We should be there!
è The D7.1 (: Eclipse IoT Proposal) is due for M12
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

5. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Eclipse Development Process
- Incubation phase
◦ The purpose of the incubation phase is to 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: new projects
may be incubated under any existing project.
◦ A project in the incubation phase can (and should) make
releases;
◦ Top-level projects skip incubation and are immediately
put into the mature phase;
◦ 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.
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review
End of the
EU Project

6. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Eclipse Development Process
- 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.
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

7. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Eclipse Development Process
- Archived phase
◦ 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.
Pre-
Proposal
Proposal
Incubation
Mature
Archived
Declaration
Creation
Review
Graduation
Review
Termination
Review
Release
Review
Release
Review

8. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Eclipse Proposal
Clear, Concise and Understandable Proposal
◦ Use plain non-technical English.
◦ Describe all acronyms.
◦ Provide urls where appropriate to direct reader for further
information.

9. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Eclipse Proposal template
◦ Background:
◦ Describe where the project came from. What is the historical journey of the project;
◦ Scope:
◦ Provide an introductory paragraph describing what the project aims to be followed by several bullet points.
◦ Description:
◦ The introductory paragraph should clearly explain what the is and does. Think of this as an expanded elevator
pitch.
◦ Why Here:
◦ Why does this project want to host at Eclipse? What do you expect to gain by having your project at Eclipse?
What value does the project provide to the Eclipse community and ecosystem?
◦ Licenses:
◦ Check the licenses that apply to the project.
◦ Legal Issues:
◦ Describe any legal issues around the project and/or code. List the current licenses of the main code. List the 3rd
party dependencies and associated licenses.
◦ Initial Contribution:
◦ Where is the code coming from? Current Eclipse project/GitHub repository or other.
◦ Future Work:
◦ How is the project going to grow its community (users/adopters/committers)? What are the major items to be
developed?

10. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Who’s involved
◦ Project leads
◦ Initial Committers:
◦ Need to already have committer status at Eclipse.
◦ Committers:
◦ These are folks who will be working on the project but are not currently Eclipse committers.
◦ Mentors:
◦ Members from the Architecture Council.
◦ Interested Parties:
◦ Who is interested in this project? This could be individuals or companies.

11. AGILE Plenary MEETING, 20-21 July 2016, Berlin, Germany
Thanks !