Eclipse XFSC (Cross Federation Services Components)

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 and will define the "state" of this ticket. 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 XFSC

Top level project: Eclipse Technology

Basic Information

• License: Apache License, Version 2.0

Pre-creation Checklist

To be completed by the EMO

• GitLab ticket state set to Community Review
• Project scope is well-defined
• Top-level Project selected
• PMC accepts the project (PMC has replied with +1)
• License(s) approved
• Project name -nor similar names- has NOT been previously used by the team
• 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: xfsc
• 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

GitLab

• Project repository group: https://gitlab.eclipse.org/eclipse/eclipse-xfsc
• Project mailing list: https://accounts.eclipse.org/mailing-list/xfsc-dev

Post-creation Checklist

To be completed by the EMO

EMO internal tasks:

• Project DB entry created
• Project lead(s) designated (DB)
• Architecture Council mentor designated (DB)

Milestones:

• Project created
• Project provisioned (including at least one committer)
• 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.

To be completed by the EMO

• GitLab ticket state set to Provisioning

After provisioning

Following provisioning, the project will be ready for initial contribution review. An initial contribution is basically the first set of project code contributions to the new Eclipse project. An initial contribution typically takes the form of an entire existing source code repository or some snapshot of an existing code base.

At this point, the project team might proceed to push their code into the requested repositories or coordinate with Webmaster and EMO to transfer existing ones. Once you've completed this process please notify EMO using this ticket.

To be completed by the EMO

• Provide project PMI link to start the IP check
  Project: Eclipse XFSC
• GitLab ticket state set to Initial Contribution

IP-check

To be completed by the EMO

Once the project has provided their initial contribution:

• IP check completed
• GitLab ticket state set to Fully Operational