EMO issueshttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues2024-01-18T16:44:45Zhttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/659iot.keyple 2024.122024-01-18T16:44:45ZMaria Teresa Delgadoiot.keyple 2024.12<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse Keyple® 2024.12 Progress Review](https://projects.eclipse.org/projects/iot.keyple/reviews/2024.12-progress-review)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [ ] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [ ] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [ ] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [ ] License files in all repository roots
- [ ] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [ ] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [ ] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [ ] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [ ] The project description starts with a single paragraph that can serve as an executive summary
- [ ] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [ ] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!--~"Progress Review"-->Maria Teresa DelgadoMaria Teresa Delgado2024-12-04https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/657automotive.sphinx 2024.122024-01-10T17:45:10ZMaria Teresa Delgadoautomotive.sphinx 2024.12<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse Sphinx 2024.12 Progress Review](https://projects.eclipse.org/projects/automotive.sphinx/reviews/2024.12-progress-review)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [ ] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [ ] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [ ] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [ ] License files in all repository roots
- [ ] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [ ] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [ ] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [ ] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [ ] The project description starts with a single paragraph that can serve as an executive summary
- [ ] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [ ] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!--~"Progress Review"-->Maria Teresa DelgadoMaria Teresa Delgado2024-12-04https://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/645ecd.theia 2024.112023-11-28T19:43:29ZMaria Teresa Delgadoecd.theia 2024.11<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse Theia 2024.11 Progress Review](https://projects.eclipse.org/projects/ecd.theia/reviews/2024.11-progress-review)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [ ] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [ ] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [ ] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [ ] License files in all repository roots
- [ ] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [ ] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [ ] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [ ] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [ ] The project description starts with a single paragraph that can serve as an executive summary
- [ ] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [ ] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!--~"Progress Review"-->Maria Teresa DelgadoMaria Teresa Delgado2024-11-27https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/637Where has the IP log generator gone?2023-11-22T09:00:07ZEd WillinkWhere has the IP log generator gone?Trying to prepare info for a release review ...
Can't find IP Log generator under Eclipse portal.
Can't find IP Log generator under PMI committer tools or under Legal Document Generator.
Is the IP log now obsolete?Trying to prepare info for a release review ...
Can't find IP Log generator under Eclipse portal.
Can't find IP Log generator under PMI committer tools or under Legal Document Generator.
Is the IP log now obsolete?https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/636technology.store 2024.112023-11-20T23:09:08ZMaria Teresa Delgadotechnology.store 2024.11<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse Store 2024.11 Progress Review](https://projects.eclipse.org/projects/technology.store/reviews/2024.11-progress-review)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [ ] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [ ] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [ ] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [ ] License files in all repository roots
- [ ] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [ ] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [ ] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [ ] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [ ] The project description starts with a single paragraph that can serve as an executive summary
- [ ] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [ ] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
~"Progress Review"Maria Teresa DelgadoMaria Teresa Delgado2024-11-20https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/635tools.ptp Termination Review2024-03-23T20:49:10ZMaria Teresa Delgadotools.ptp Termination Review<!--
This template is used by the EMO to track the termination of a project.
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the project_name
You can delete the comments (or not).
-->
The E...<!--
This template is used by the EMO to track the termination of a project.
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the project_name
You can delete the comments (or not).
-->
The EMO is using this issue to track the progress of a project termination review.
We have cited lack of development activity as the reason for the termination. Project leads and committers can add more to the review documentation if desired.
The purpose of a Termination Review is to provide a final opportunity for the Committers and/or Eclipse Membership at Large to discuss the proposed archiving of a Project. The desired outcome is to find sufficient evidence of renewed interest and resources in keeping the Project active.
## Project
<!-- Project name and termination review link from the PMI -->
Project: [Eclipse Parallel Tools Platform (PTP) Termination Review](https://projects.eclipse.org/projects/tools.ptp/reviews/termination-review)
## Pre-Termination Review Checklist
_To be completed by the EMO_
- [x] PMC has been notified
- [x] Project team has been notified via dev-list
- [x] Project team has been notified via email
## Post-Termination Checklist
_To be completed by EMO_
- [x] Retire committers and project leads relationships (PMI)
- [x] Retire Mentor relationships (Database)
- [x] Archive the project (PMI)
- [ ] Archive the project (Database)
_To be completed by Webmaster_
Shutdown/archive:
- [x] CI instance (https://github.com/eclipse-cbi/jiro/tree/master/instances, https://ci.eclipse.org/)
- [ ] Website
- [ ] Git repositories
- [ ] Mailing list
- [ ] Forum
- [ ] Bugzilla product
Your comments, feedback, and pushback are welcome.
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project termination must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
<!-- Quick actions will configure the state of the issue. Leave these. -->Eclipse WebmasterMaria Teresa DelgadoWayne BeatonEclipse Webmaster2023-11-29https://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/6322023.11 tools.linuxtools2023-11-22T22:49:03ZMaria Teresa Delgado2023.11 tools.linuxtools<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse Linux Tools 2023.11 Progress Review](https://projects.eclipse.org/projects/tools.linuxtools/reviews/2023.11-progress-review)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [x] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [x] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [x] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [x] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [x] License files in all repository roots
- [x] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [x] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [x] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [x] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [x] The project description starts with a single paragraph that can serve as an executive summary
- [x] Source code repository references are up-to-date
- [x] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [x] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!--~"Progress Review"-->Maria Teresa DelgadoMaria Teresa Delgadohttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/630iot.ditto 2024.112023-11-18T16:07:25ZMaria Teresa Delgadoiot.ditto 2024.11<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse Ditto 2024.11 Progress Review](https://projects.eclipse.org/projects/iot.ditto/reviews/2024.11-progress-review)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [ ] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [ ] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [ ] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [ ] License files in all repository roots
- [ ] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [ ] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [ ] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [ ] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [ ] The project description starts with a single paragraph that can serve as an executive summary
- [ ] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [ ] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!--~"Progress Review"-->Maria Teresa DelgadoMaria Teresa Delgado2024-11-20https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/629technology.xfsc 2024.022024-03-12T16:11:03ZMaria Teresa Delgadotechnology.xfsc 2024.02<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse XFSC (Cross Federation Services Components) 2024.01 Progress Review](https://projects.eclipse.org/projects/technology.xfsc/reviews/2024.01-progress-review)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [x] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [ ] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [x] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [ ] License files in all repository roots
- [x] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [ ] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [x] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [x] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [x] The project description starts with a single paragraph that can serve as an executive summary
- [x] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [x] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
~"Progress Review"Maria Teresa DelgadoFlorent ZaraMaria Teresa Delgado2024-03-27https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/627automotive.ecal 2024.102023-11-10T19:15:38ZMaria Teresa Delgadoautomotive.ecal 2024.10<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse eCAL (enhanced Communication Abstraction Layer) 2024.10](https://projects.eclipse.org/projects/automotive.ecal/reviews/2024.10)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [ ] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [ ] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [ ] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [ ] License files in all repository roots
- [ ] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [ ] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [ ] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [ ] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [ ] The project description starts with a single paragraph that can serve as an executive summary
- [ ] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [ ] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
~"Progress Review"Maria Teresa DelgadoMaria Teresa Delgado2024-10-30https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/623iot.hawkbit 2024.102023-11-09T17:34:51ZMaria Teresa Delgadoiot.hawkbit 2024.10<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to th...<!--
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/#release-review
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash"
You can delete the comments (or not).
-->
## Project
[Eclipse hawkBit 2024.10 Progress Review
](https://projects.eclipse.org/projects/iot.hawkbit/reviews/2024.10-progress-review)
The EMO is using this issue to track this progress review. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#release-review).
## What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
<!--
This being a specification project, you'll also need to follow some extra guidelines, usually you'll need to run a Specification Committee Ballot before the release review date. Please make sure to check your Working group guidelines regarding Specification releases.
-->
The following image shows the workflow for a Progress/Release review at the Eclipse Foundation.
![Review Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_releases.png)
<!--
Only for specification projects
![Review Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [3rd party dependencies provided (i.e. notice file, SBOM, etc. )]({IPzilla link})
- [ ] [PMC approval requested]({mailing list message link})
<!--
Only for specification projects
- [ ] [WG ballot initiated]({mailing list message link})
-->
## Intellectual Property Management
_To be completed by the EMO._
- [ ] All project code has [copyright and license headers](https://www.eclipse.org/projects/handbook/#ip-copyright-headers) correctly applied. ** EMO will scan the code at their discretion **
- [ ] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
## Open Source Rules of Engagement
_To be completed by the PMC in the case of Progress Reviews._
- [ ] PMC approval [on the mailing list]({link to the message})
General:
- [ ] Project is operating within the mission and scope defined in its top-level project’s charter
- [ ] Project is operating within the bounds of its own scope
- [ ] Project is operating in an open and transparent manner
- [ ] Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
## Branding and Trademarks
_To be completed by the EMO and PMC._
The following applies when the project has a custom website.
To the best of our knowledge:
- [ ] Project content correctly uses Eclipse Foundation trademarks
- [ ] Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the [project's formal name](https://www.eclipse.org/projects/handbook/#trademarks-website-name) in first and all prominent references
- Project website includes a [trademark attribution statement]((https://www.eclipse.org/projects/handbook/#trademarks-website))
- Project website footers contain all [necessary elements](https://www.eclipse.org/projects/handbook/#trademarks-website-footer)
<!--## Security
_To be completed by the EMO._
The following are EF recommendations to improve the security of your Open Source Project.
- [ ] Implement 2-factor authentication to login into your GitLab/GitHub accounts.
- [ ] Enabling Security health metrics for Open Source ([OSSF Scorecard](https://github.com/ossf/scorecard#readme))
You can also request a personalized security assessment from the EF Security Team of your project repositories and related resources.
- [ ] Request Security Team assessment
-->
## Legal Documentation
Required files:
- [ ] License files in all repository roots
- [ ] README
- [ ] CONTRIBUTING (or equivalent)
Recommended files:
- [ ] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [ ] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for [Security file](https://gitlab.eclipse.org/security/best-practices/-/blob/main/templates/SECURITY.md) and [Code of Conduct](https://github.com/eclipse/.github/blob/master/CODE_OF_CONDUCT.md).
Required elements:
- [ ] ECA is referenced/described
Recommended elements:
- [ ] Build instructions provided
- [ ] [Security policy](https://www.eclipse.org/security/policy.php) is described
## Metadata (PMI)
_To be completed by the EMO and PMC._
- [ ] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [ ] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [ ] The project description starts with a single paragraph that can serve as an executive summary
- [ ] Source code repository references are up-to-date
- [ ] Download links and information are up-to-date (see [EF handbook for more information on how-to do this](https://www.eclipse.org/projects/handbook/#resources-downloads))
- [ ] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!--~"Progress Review"-->Maria Teresa DelgadoMaria Teresa Delgado2024-10-30https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/608ee4j.cdi Restructuring Review2024-03-27T16:05:28ZMaria Teresa Delgadoee4j.cdi Restructuring Review<!--
The EMO is using this template to track the status of Restrucring reviews.
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/
Parts of this issue can initially be left blank to be fi...<!--
The EMO is using this template to track the status of Restrucring reviews.
There's help in the Eclipse Foundation Project Handbook https://www.eclipse.org/projects/handbook/
Parts of this issue can initially be left blank to be filled in during the review.
Set the title of this issue to the project's id, e.g., "technology.dash Restructuring Review"
You can delete the comments (or not).
-->
## Restructuring rationale
The project team wants to break up the current 4.0 specification into two specifications.
They have updated the [CDI 4.1](https://projects.eclipse.org/projects/ee4j.cdi/releases/cdi-4.1) plan review to include the 'Breaking up spec/TCK to remove circular dependencies' item which encapsulates the restructuring related element. The restructured pieces are being moved into the new [CDI EE 4.](https://projects.eclipse.org/projects/ee4j.cdi/releases/cdi-ee-4.1)1 release.
PMI link: [Jakarta Contexts and Dependency Injection™ Restructuring Review](https://projects.eclipse.org/projects/ee4j.cdi/reviews/restructuring-review)
## Expected infrastructure changes
<!--
The project team should list the expected infrastructure changes in thsi section, e.g. new project name and shortname, which repositories to move, repositories that need to be archived, committer's databases to be merged/splitted, etc.
-->
The following infrastructure changes are requested by the project team:
- Project name
- Committers
- Project repositories
- CI instance
- Mailing list
- Other(s)
## Restructuring To-Do list
In order to implement the proposed changes, we need to complete the following:
- [ ] EMO (ED) approval
- [ ] PMC approval
- [ ] Project community informed using public channels (i.e. dev mailing list and/or forums)
- [ ] Infrastructure changes implemented
<!--
If the restructuring review is related to a specification project you'll need the Specification committee approval
- [ ] Spec committee approval
-->Maria Teresa DelgadoMaria Teresa Delgado2023-11-08https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/607Code Contributions from jetty-project2024-01-04T16:49:32ZJesse McConnellCode Contributions from jetty-project
We have had a large amount of repositories at https://github.com/jetty-project for years. The pre-eclipse jetty source is in there and other ancient things as well.
However, we also have a lot of small, one-off repositories for example...
We have had a large amount of repositories at https://github.com/jetty-project for years. The pre-eclipse jetty source is in there and other ancient things as well.
However, we also have a lot of small, one-off repositories for examples and things like that.
One such example:
https://github.com/jetty-project/jetty-helloworld-webapp
All of the commits are from Jetty committers, so this should be a formality, but I would like to understand the best way for us to contribute this to the new github.com/jetty organization.
Our current plan is to create a jetty-cookbook repository and do a many-to-one migration of this example content, but we presume you will need to vet it somehow.
Should we list every repo we want to migrate and let you loose on it? Or do you have a preferred approach?
<!-- Quick actions will configure the state of the issue. Leave these. -->https://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-25