EMO issueshttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues2024-03-27T15:27:14Zhttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/714Eclipse Trust Protocol2024-03-27T15:27:14ZMaria Teresa DelgadoEclipse Trust Protocol<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
![Onboarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Trust Protocol](https://projects.eclipse.org/proposals/eclipse-trust-protocol)
Top level project: Technology
## Basic Information
- License: Eclipse Public License 2.0
- Patent License: Implementation Patent License
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [ ] PMC accepts the project (PMC has replied with +1)
- [x] 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](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [ ] Two weeks of community review completed
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [ ] The project lead has confirmed the project shortname: dspace-trust
- [ ] 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 organization: https://github.com/eclipse-dspace-trust
- [ ] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/dspace-trust-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [ ] Project DB entry created
- [ ] Project lead(s) 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](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoMaria Teresa Delgado2024-04-03https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/713Eclipse Dataspace Identity and Trust Protocol2024-03-28T17:56:01ZMaria Teresa DelgadoEclipse Dataspace Identity and Trust Protocol<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
![Onboarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Dataspace Identity and Trust Protocol](https://projects.eclipse.org/proposals/eclipse-dataspace-identity-and-trust-protocol)
Top level project: Technology
## Basic Information
- License: Apache License, Version 2.0
- Patent License: Implementation Patent License
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [ ] Top-level Project selected
- [ ] PMC accepts the project (PMC has replied with +1)
- [x] 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](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [ ] Committers have Eclipse Foundation Accounts
- [ ] Two weeks of community review completed
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [ ] The project lead has confirmed the project shortname: dspace-idtrust
- [ ] 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 organization: https://github.com/eclipse-dspace-idtrust
- [ ] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/dspace-idtrust-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [ ] Project DB entry created
- [ ] Project lead(s) 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](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoMaria Teresa Delgado2024-04-10https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/695Eclipse Dataspace Protocol2024-03-27T16:10:58ZMaria Teresa DelgadoEclipse Dataspace Protocol<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Dataspace Protocol](https://projects.eclipse.org/proposals/eclipse-dataspace-protocol)
Top level project: Technology
## Basic Information
- License: Apache License, Version 2.0
- Patent License: Compatible Patent License
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [ ] Committers have Eclipse Foundation Accounts
- [ ] Two weeks of community review completed
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [ ] The project lead has confirmed the project shortname: **dspace-protocol**
- [ ] 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 organization: https://github.com/eclipse-dspace-protocol
- [ ] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/dspace-protocol-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [ ] Project DB entry created
- [ ] Project lead(s) 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](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoMaria Teresa Delgado2024-03-27https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/694Eclipse Zenoh-Flow2024-03-27T16:20:55ZMaria Teresa DelgadoEclipse Zenoh-Flow<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Zenoh-Flow](https://projects.eclipse.org/proposals/eclipse-zenoh-flow)
Eclipse Zenoh-Flow Creation Review: https://projects.eclipse.org/reviews/eclipse-zenoh-flow-creation-review
Top level project: IoT
## Basic Information
- License:
- Apache License, Version 2.0
- Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [ ] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [ ] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [ ] Committers have Eclipse Foundation Accounts
- [ ] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [ ] The project lead has confirmed the project shortname: zenoh-flow
- [ ] 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 organization: https://github.com/eclipse-zenoh-flow
- [ ] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/zenoh-flow-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [ ] Project DB entry created
- [ ] Project lead(s) 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](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoMaria Teresa Delgado2024-03-20https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/664Eclipse WattAdvisor2024-03-19T16:21:36ZMaria Teresa DelgadoEclipse WattAdvisor<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse WattAdvisor](https://projects.eclipse.org/proposals/eclipse-wattadvisor)
Top level project: Technology
## Basic Information
- License: Eclipse Distribution License 1.0 (BSD)
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: **wattadvisor**
- [x] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
- Project organization: https://github.com/eclipse-wattadvisor
- [x] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/wattadvisor-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [ ] Project lead(s) 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](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoPawel StankiewiczEclipse Webmaster2024-03-06https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/654Eclipse Daanse2024-03-26T18:15:13ZMaria Teresa DelgadoEclipse Daanse<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse daanse - Data and Analysis Services](https://projects.eclipse.org/proposals/eclipse-daanse-data-and-analysis-services)
Top level project: Technology
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [ ] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: **daanse**
- [x] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
- Project organization: https://github.com/eclipse-daanse
- [x] The project Lead has requested EF team to enable the self-service [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/daanse-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
Milestones:
- [x] Project created
- [ ] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoEclipse Webmaster2024-03-27https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/652Eclipse Common Security Infrastructure2024-03-19T16:25:09ZMaria Teresa DelgadoEclipse Common Security Infrastructure<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Common Security Infrastructure](https://projects.eclipse.org/proposals/eclipse-common-security-infrastructure)
Top level project: Technology
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: **csi**
- [x] The project lead has confirmed the following project resources are correct in the comment's section
- Dedicated project GitHub Organization: https://github.com/eclipse-csi
- The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/csi-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
Milestones:
- [x] Project created
- [ ] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [x] 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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoEclipse Webmaster2024-03-20https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/649Eclipse Corinthian2024-03-19T16:25:48ZMaria Teresa DelgadoEclipse Corinthian<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Corinthian](https://projects.eclipse.org/proposals/eclipse-corinthian)
Top level project: Technology
## Basic Information
- License:
- Apache License, Version 2.0
- BSD Zero Clause License
- Creative Commons Attribution 4.0 (International) License
- Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: **corinthian**
- [x] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
- Project repository: https://github.com/eclipse/corinthian
- The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/corinthian-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
Milestones:
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [x] 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_
- [x] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoEclipse Webmaster2024-03-20https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/646Eclipse FA³ST2024-03-19T16:26:13ZMaria Teresa DelgadoEclipse FA³ST<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse FA³ST](https://projects.eclipse.org/proposals/eclipse-fa%C2%B3st)
Top level project: Digital Twin
## Basic Information
- License: Apache License, Version 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] 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](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [ ] The project lead has confirmed the project shortname: **fa3st**
- [ ] 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
- [x] Project repository: The project team has requested a dedicated GitHub organization
- [ ] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/fa3st-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [ ] Project lead(s) 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](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoEclipse Webmaster2024-03-27https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/634Eclipse Vhant2024-03-19T16:26:29ZMaria Teresa DelgadoEclipse Vhant<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Vhant](https://projects.eclipse.org/proposals/eclipse-vhant)
Top level project: Technology
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: vhant
- [x] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
- Project repository group: https://gitlab.eclipse.org/eclipse/vhant
- Project repository: https://gitlab.eclipse.org/eclipse/vhant/vhant
- Project mailing list: https://accounts.eclipse.org/mailing-list/vhant-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
Milestones:
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [x] 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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoEclipse Webmaster2024-04-03https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/633Eclipse ThreadX2024-03-12T02:27:49ZMaria Teresa DelgadoEclipse ThreadX<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse ThreadX](https://projects.eclipse.org/proposals/eclipse-threadx)
Top level project: Eclipse IoT
## Basic Information
- License: The MIT License (MIT)
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [ ] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: **threadx**
- [ ] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
- Project repository or Project organization **(TBD)**: https://github.com/eclipse/threadx
- Project mailing list: https://accounts.eclipse.org/mailing-list/threadx-dev
- [ ] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
Milestones:
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoEclipse Webmasterhttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/604Eclipse OS-Gov2024-03-27T15:32:19ZMaria Teresa DelgadoEclipse OS-Gov<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse OS-Gov](https://projects.eclipse.org/proposals/eclipse-os-gov)
Top level project: Technology
## Basic Information
- License: Apache License, Version 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to approve the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: **os-gov**
- [ ] The project lead has requested a project website repository in the comments
- [x] 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/os-gov
- Project repository: https://gitlab.eclipse.org/eclipse/os-gov/os-gov
<!--
GitHub
- Project repository: https://github.com/eclipse/os-gov
- Downloads: http://download.eclipse.org/os-gov
- Archives: http://archive.eclipse.org/os-gov
-->
- Project mailing list: https://accounts.eclipse.org/mailing-list/os-gov-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
- [ ] Architecture Council mentor designated (DB)
Milestones:
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [x] 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_
- [x] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoMaria Teresa Delgado2024-03-25https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/534Eclipse OpenXilEnv2024-03-04T07:47:43ZBoris BaldassariEclipse OpenXilEnv<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse OpenXilEnv](https://projects.eclipse.org/proposals/eclipse-openxilenv)
Top level project:
## Basic Information
- License: Apache License, Version 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] GitLab ticket state set to Community Review
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: openxilenv
- [x] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
GitHub
- Project repository: https://github.com/eclipse-openxilenv
- Downloads: http://download.eclipse.org/openxilenv
- Archives: http://archive.eclipse.org/openxilenv
- Mailing list: https://accounts.eclipse.org/mailing-list/openxilenv-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
- [x] Architecture Council mentor designated (DB)
Milestones:
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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_
- [x] 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_
- [x] Provide project PMI link to start the IP check <br>
Project: [Eclipse OpenXilEnv](https://projects.eclipse.org/projects/automotive.openxilenv)
- [ ] 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
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoWayne BeatonBoris BaldassariMaria Teresa Delgado2024-03-18https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/447Eclipse SCM2024-02-12T16:13:58ZBoris BaldassariEclipse SCM
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows...
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse SCM](https://projects.eclipse.org/proposals/eclipse-scm) \
Creation review: https://projects.eclipse.org/reviews/eclipse-scm-creation-review \
Top level project: Automotive
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [ ] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to approve the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: scm
- [x] The project lead has requested a project website repository in the comments
- [x] 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/scm
- Project repository: https://gitlab.eclipse.org/eclipse/scm/scm
- Project mailing list: https://accounts.eclipse.org/mailing-list/scm
- Project mailing list: https://accounts.eclipse.org/mailing-list/scm-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
- [x] Architecture Council mentor designated (DB)
Milestones:
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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](https://www.eclipse.org/projects/handbook/#ip-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](https://www.eclipse.org/projects/handbook/#ip-cq)).
More information is available in the [Eclipse Handbook](https://www.eclipse.org/projects/handbook/#starting-after-provisioning).
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
## Post-provisioning Checklist
_To be completed by the EMO_
These are the last few things needed to close this issue:
- [ ] [Initial Contribution](link) submitted for review by the IP Team
- [ ] IP team checkin granted
<!-- Quick actions will configure the state of the issue. Leave these. -->Maria Teresa DelgadoWayne BeatonBoris BaldassariMaria Teresa Delgado2024-03-12https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/391Eclipse ArchE2024-03-04T07:46:37ZMaria Teresa DelgadoEclipse ArchE<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse ArchE](https://projects.eclipse.org/proposals/eclipse-arche)
Project creation review: https://projects.eclipse.org/reviews/eclipse-arche-creation-review
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [ ] The project lead has confirmed the project shortname: **arche**
- [ ] 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/{project_name}
- Project repository: https://gitlab.eclipse.org/eclipse/{project_name}/{project_name}
GitHub
- Project repository: https://github.com/eclipse/{project_name}
- Downloads: http://download.eclipse.org/{project_name}
- Archives: http://archive.eclipse.org/{project_name}
-->
- Project mailing list: https://accounts.eclipse.org/mailing-list/arche-dev
- Project: [Eclipse ArchE](https://projects.eclipse.org/projects/automotive.arche)
## Post-creation Checklist
_To be completed by the EMO_
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [x] Project lead(s) designated (DB) **--> Andreas Looft still needs to be designated**
- [x] Architecture Council mentor designated (DB)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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](https://www.eclipse.org/projects/handbook/#ip-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](https://www.eclipse.org/projects/handbook/#ip-cq)).
More information is available in the [Eclipse Handbook](https://www.eclipse.org/projects/handbook/#starting-after-provisioning).
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
## Post-provisioning Checklist
_To be completed by the EMO_
These are the last few things needed to close this issue:
- [ ] [Initial Contribution](link) submitted for review by the IP Team
- [ ] IP team checkin granted
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoWayne BeatonBoris BaldassariEclipse Webmaster2024-03-18https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/390Eclipse DROPS2024-01-09T19:02:30ZMaria Teresa DelgadoEclipse DROPS<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
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
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse DROPS](https://projects.eclipse.org/proposals/eclipse-drops)
Project: [Eclipse DROPS](https://projects.eclipse.org/projects/technology.drops)
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## 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](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] 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_
- [x] Project created
- [ ] Project provisioned (including at least one committer)
- [x] Project lead(s) designated (DB)
- [x] Architecture Council mentor designated (DB)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) 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](https://www.eclipse.org/projects/handbook/#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](https://www.eclipse.org/projects/handbook/#ip-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](https://www.eclipse.org/projects/handbook/#ip-cq)).
More information is available in the [Eclipse Handbook](https://www.eclipse.org/projects/handbook/#starting-after-provisioning).
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
## Post-provisioning Checklist
_To be completed by the EMO_
These are the last few things needed to close this issue:
- [ ] [Initial Contribution](link) submitted for review by the IP Team
- [ ] IP team checkin granted
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoWayne BeatonEclipse Webmasterhttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/319Eclipse SommR2024-01-18T18:36:21ZMaria Teresa DelgadoEclipse SommR<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse SommR](https://projects.eclipse.org/proposals/eclipse-sommr)
## Basic Information
- License: Apache License, Version 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
- [x] The project lead has confirmed the following project resources are correct in the comment's section
- [x] The project lead has requested a project website repository in the comments
- Project repository: https://github.com/eclipse/sommr
- Project mailing list: https://accounts.eclipse.org/mailing-list/sommr-dev
## Post-creation Checklist
_To be completed by the EMO_
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [x] Project lead(s) designated - missing Gerd Schaefer
- [x] Architecture Council mentor designated
- [ ] [Initial Contribution](https://www.eclipse.org/projects/handbook/#ip-initial-contribution) submitted for review by the IP Team
- [ ] Committer orientation completed
Project: [Eclipse SommR](https://projects.eclipse.org/projects/automotive.sommr)
## 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](https://www.eclipse.org/projects/handbook/#starting-after-provisioning).
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoBoris BaldassariMaria Teresa Delgado2024-05-15https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/311Eclipse ADAAA (Adaptive Cruise Control Demo Application for Adaptive AUTOSAR)2024-01-18T18:37:06ZMaria Teresa DelgadoEclipse ADAAA (Adaptive Cruise Control Demo Application for Adaptive AUTOSAR)<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse ADAAA](https://projects.eclipse.org/proposals/eclipse-adaaa-adaptive-cruise-control-demo-application-adaptive-autosar)
Project: [Eclipse ADAAA](https://projects.eclipse.org/projects/automotive.adaaa)
## Basic Information
- License: The MIT License (MIT)
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
- [ ] The project lead has confirmed the following project resources are correct in the comment's section
- [ ] The project lead has requested a project website repository in the comments
- Project repository: https://github.com/eclipse/adaaa
- Project mailing list: https://accounts.eclipse.org/mailing-list/adaaa-dev
## Post-creation Checklist
_To be completed by the EMO_
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [x] Project lead(s) designated
- [x] Architecture Council mentor designated
- [ ] [Initial Contribution](https://www.eclipse.org/projects/handbook/#ip-initial-contribution) submitted for review by the IP Team
- [ ] Committer orientation completed
## 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](https://www.eclipse.org/projects/handbook/#starting-after-provisioning).
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoBoris BaldassariMaria Teresa Delgado2024-05-15https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/189Eclipse Novamoon2023-08-21T14:44:51ZMaria Teresa DelgadoEclipse Novamoon<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Novamoon](https://projects.eclipse.org/proposals/eclipse-novamoon)
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
- [ ] The project lead has confirmed the following project resources are correct in the comment's section
- Project repository: https://github.com/eclipse/novamoon
- Downloads: http://download.eclipse.org/novamoon
- Archives: http://archive.eclipse.org/novamoon
- Project mailing list: https://accounts.eclipse.org/mailing-list/novamoon-dev
- [ ] The project lead has requested a project website repository in the comments
## Post-creation Checklist
_To be completed by the EMO_
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [x] Project lead(s) designated
- [x] Architecture Council mentor designated
- [ ] [Initial Contribution](https://www.eclipse.org/projects/handbook/#ip-initial-contribution) submitted for review by the IP Team
- [ ] Committer orientation completed
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
<!-- Quick actions will configure the state of the issue. Leave these. -->Eclipse WebmasterMaria Teresa DelgadoWayne BeatonEclipse Webmaster2023-09-13https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/19Eclipse Austen2023-12-01T20:02:54ZMaria Teresa DelgadoEclipse Austen<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
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](https://www.eclipse.org/projects/handbook/#starting).
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Austen](https://projects.eclipse.org/proposals/eclipse-austen)
## Basic Information
- License: Eclipse Public License 2.0
## Pre-creation Checklist
_To be completed by the EMO._
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name trademark approved
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
## Post-creation Checklist
_To be completed by the EMO._
- [x] Project created
- [ ] Project provisioned (including at least one committer)
- [x] Project lead(s) designated
- [x] Architecture Council mentor designated
- [ ] [Initial Contribution](https://www.eclipse.org/projects/handbook/#ip-initial-contribution) submitted for review by the IP Team
- [ ] Committer orientation completed
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
<!-- Quick actions will configure the state of the issue. Leave these. -->Eclipse WebmasterMaria Teresa DelgadoWayne BeatonEclipse Webmaster