Eclipse DROPS

The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the Eclipse Foundation Project Handbook.

The following image shows the workflow for Starting a Project at the Eclipse Foundation.

We are using scoped labels to identify where a project proposal is at any time during the onboarding process. These labels are mapped to the stages shown in the previous image. If you have doubts, just ask.

We'll use the due date of this issue to provide an estimation of the next date the EMO team will checkin with the project team. Sometimes, e.g. during the project creation time, the due date will coincide with the Project Creation date.

Project

Project proposal: Eclipse DROPS

Project: Eclipse DROPS

Basic Information

• License: Eclipse Public License 2.0

Pre-creation Checklist

To be completed by the EMO

• Project scope is well-defined
• Top-level Project selected
• PMC accepts the project (PMC has replied with +1)
• License(s) approved
• Project name trademark approved. Trademark transfer agreement available here in case you need it.
• Project lead(s) identified
• Committers identified
• Committers have Eclipse Foundation Accounts
• Eclipse Architecture Council mentor identified
• Two weeks of community review completed

Project resources to be created

Project Lead involvement needed Open source projects at the Eclipse Foundation are required to make use of certain Eclipse Foundation services. See the Handbook for more information on this subject.

• The project lead has confirmed the project shortname: drops

• The project lead has requested a project website repository in the comments

• The project lead has confirmed the following project resources are correct in the comment's section

  • Project repository: https://github.com/eclipse/eclipse-drops
  • Project mailing list: https://accounts.eclipse.org/mailing-list/drops-dev

Post-creation Checklist

To be completed by the EMO

• Project created
• Project provisioned (including at least one committer)
• Project lead(s) designated (DB)
• Architecture Council mentor designated (DB)
• Committer orientation completed (upon request)

After creation

Once the project is created the provisioning process starts with an email message being sent to each of the committers listed on the project proposal with instructions on how to engage in the committer paperwork process.

Committers should check their emails and complete the paperwork at their earliest convenience. No project resources are created until at least one committer is fully provisioned.

After provisioning

Before pushing any code into an official Eclipse project repository, the project team must submit the project’s initial contribution of project code and wait for the Eclipse Intellectual Property (IP) Team to grant checkin of that contribution.

Project teams interact with the Eclipse IP Team via the IPZilla system using Contribution Questionnaires (CQs). More information is available in the Eclipse Handbook.

Approximately three months after successful completion of this creation review, the EMO will initiate a progress review.

Post-provisioning Checklist

To be completed by the EMO

These are the last few things needed to close this issue:

• Initial Contribution submitted for review by the IP Team
• IP team checkin granted