EMO issueshttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues2022-08-30T15:06:22Zhttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/343Investigate potential to use Microsoft's open source SBOM tool2022-08-30T15:06:22ZWayne BeatonInvestigate potential to use Microsoft's open source SBOM toolInvestigate the potential to use the Microsoft SBOM tool to generate SBOMs for Eclipse content.
Based on claims in the tool's documentation, there's some overlap with ORT (in that it purports to dig into build files to identify dependen...Investigate the potential to use the Microsoft SBOM tool to generate SBOMs for Eclipse content.
Based on claims in the tool's documentation, there's some overlap with ORT (in that it purports to dig into build files to identify dependencies). AFAICT, it doesn't scan content for license or copyright information.
- [Blog post](https://devblogs.microsoft.com/engineering-at-microsoft/microsoft-open-sources-salus-software-bill-of-materials-sbom-generation-tool/)
- [GitHub repository](https://github.com/microsoft/sbom-tool)
I've done some initial investigation with version 0.1.3 of the tool. It generates an SBOM, but with some deficiencies.
- No licenses captured;
- No copyrights captured;
- Includes content from `.git` directory and from ephemeral build artifact directories (e.g., `node_modules`, `target`) (see [Issue 63](https://github.com/microsoft/sbom-tool/issues/63));
- Apparently misses Maven `pom.xml` files (see [Issue 64](https://github.com/microsoft/sbom-tool/issues/64));
It does appear to do a good job of capturing content from NPM `package-lock.json` and `yarn.lock`. I haven't investigated how deeply it interrogates the dependency tree (i.e., does it deal with transitive dependencies?)
/cc @skilpatrick @mdelgado624Wayne BeatonWayne Beaton2022-10-31https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/388modeling.efm 2022.112023-05-29T14:59:23ZMaria Teresa Delgadomodeling.efm 2022.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 Formal Modeling Project 2022.11 Progress Review](https://projects.eclipse.org/projects/modeling.efm/reviews/2022.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 Soecification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/EDP_release_specification.png)
-->
## Requisites
- [ ] [IP log submitted]({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)
## 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://github.com/eclipse-ee4j/.github/blob/main/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
- [ ] 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. -->Maria Teresa DelgadoWayne BeatonMaria Teresa Delgado2023-03-22https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/392Jakarta Security Restructuring Review2023-09-11T23:08:29ZMaria Teresa DelgadoJakarta Security Restructuring ReviewPMI link: [Jakarta Security™ Restructuring Review](https://projects.eclipse.org/projects/ee4j.es/reviews/restructuring-review)
There are 3 specification projects related to security in Jakarta:
- https://projects.eclipse.org/projects/e...PMI link: [Jakarta Security™ Restructuring Review](https://projects.eclipse.org/projects/ee4j.es/reviews/restructuring-review)
There are 3 specification projects related to security in Jakarta:
- https://projects.eclipse.org/projects/ee4j.authentication
- https://projects.eclipse.org/projects/ee4j.authorization
- https://projects.eclipse.org/projects/ee4j.es
There has been discussion that these should be three specifications under a single specification project under Jakarta Security. This restructuring review covers the relevant aspects to implement these changes.
## Restructuring To-Do list
In order to implement the proposed changes, we need to complete the following:
- [x] EMO (ED) approval
- [x] EE4J PMC +1
- [x] Spec committee approval
- [ ] Infrastructure changesEclipse WebmasterMaria Teresa DelgadoJakub MazanekEclipse Webmaster2023-04-05https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/415Migrating the EMO Wiki to GitLab2023-04-19T18:05:02ZMaria Teresa DelgadoMigrating the EMO Wiki to GitLabThere is some useful information in the "old" [Eclipse Wiki](https://foundation.eclipse.org/wiki/index.php?title=EMO_Processes) regarding some of the main EMO processes (e.g. project creation, releases, elections, etc.).
With the recent...There is some useful information in the "old" [Eclipse Wiki](https://foundation.eclipse.org/wiki/index.php?title=EMO_Processes) regarding some of the main EMO processes (e.g. project creation, releases, elections, etc.).
With the recent migration to GitLab and retirement of old project resources like Bugzilla and IPzilla, we should move the relevant contents -and create new ones- directly in the [EMO GitLab wiki](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/wikis/home).
In my mind, the result would be a "recipe book" that allows basically anyone to complete any EMO task.
This is a collaborative task that we'll carry out and hopefully complete by the end of Q2 2023.
/cc @wbeatonMaria Teresa DelgadoBoris BaldassariMaria Teresa Delgado2023-04-30https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/474Create a high-level overview of onboarding, including prerequisites2023-04-24T06:26:19ZBoris BaldassariCreate a high-level overview of onboarding, including prerequisitesAs discussed today, it would be helpful to create a short summary of what onboarding a new project at the EF means, its basic prerequisites (e.g. one knows they can push their code) and main stages.
The goal is to help people understan...As discussed today, it would be helpful to create a short summary of what onboarding a new project at the EF means, its basic prerequisites (e.g. one knows they can push their code) and main stages.
The goal is to help people understand what it implies to submit a project to the EF, from the proposal to the project running. The target is now really the committers, bur rather the people in charge of submitting the projects (who may, or may not, be the same).Boris BaldassariBoris Baldassari2023-05-02https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/557ecd.che.che4z 2023.082023-10-25T20:04:55ZMaria Teresa Delgadoecd.che.che4z 2023.08<!--
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 Che4z 2023.08 Progress Review](https://projects.eclipse.org/projects/ecd.che.che4z/reviews/2023.08-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._
- [ ] 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:
- [x] Project content correctly uses Eclipse Foundation trademarks
- [x] 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
- [x] CONTRIBUTING (or equivalent)
Recommended files:
- [x] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [x] CODE_OF_CONDUCT
- [x] SECURITY
See examples for [Security file](https://github.com/eclipse-ee4j/.github/blob/main/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:
- [x] 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. -->Maria Teresa DelgadoMaria Teresa Delgado2023-09-06https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/189Eclipse Novamoon2023-08-21T14:44:51ZMaria Teresa DelgadoEclipse Novamoon<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#starting).
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Novamoon](https://projects.eclipse.org/proposals/eclipse-novamoon)
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
- [ ] The project lead has confirmed the following project resources are correct in the comment's section
- Project repository: https://github.com/eclipse/novamoon
- Downloads: http://download.eclipse.org/novamoon
- Archives: http://archive.eclipse.org/novamoon
- Project mailing list: https://accounts.eclipse.org/mailing-list/novamoon-dev
- [ ] The project lead has requested a project website repository in the comments
## Post-creation Checklist
_To be completed by the EMO_
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [x] Project lead(s) designated
- [x] Architecture Council mentor designated
- [ ] [Initial Contribution](https://www.eclipse.org/projects/handbook/#ip-initial-contribution) submitted for review by the IP Team
- [ ] Committer orientation completed
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
<!-- Quick actions will configure the state of the issue. Leave these. -->Eclipse WebmasterMaria Teresa DelgadoWayne BeatonEclipse Webmaster2023-09-13https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/563Implement a committer badging programme2023-11-21T16:53:22ZWayne BeatonImplement a committer badging programmeWe're going to implement a committer badging programme. The basic idea is that we'll use an existing badging system to grant a "Committer" badge to our committers.
We'll keep this simple: anybody who has committer status on at least one...We're going to implement a committer badging programme. The basic idea is that we'll use an existing badging system to grant a "Committer" badge to our committers.
We'll keep this simple: anybody who has committer status on at least one Eclipse open source project is entitled to the badge.
* When somebody gets committer status (either by being elected to committer status on an existing project via committer election, or as an initial committer on a new project), we enter them into the badge system. When an individual who is a committer on an existing project, gets committer status on another project, they will be offered a committer badge only if they do not already have one.
* Existing committers will be given an opportunity to request a badge (e.g., we use the mailing list to tell committers to contact emo-records to request the badge).
* Legacy committers (that is, folks who have previously held committer status, but do not currently have an active committer role) will be treated as existing committer (except that they won't be necessarily be notified that the programme exists, and so will have to find us themselves).
Initially, we do this manually; after we get experience with the service provider, we'll explore automation options.
By way of background… we’d considered making this more complex, but the corner cases/grey area will kill us. We could, for example, make creating some number of commits be a requirement, but then we’d have to distinguish between commits made while establishing merit before becoming a committer and those created after getting status. This distinction is arbitrary and will undoubtedly be challenged. At some point, we should consider “activeness” badges, but let’s keep that as a separate consideration.
/cc @skilpatrick @karlafbWayne BeatonWayne Beaton2023-09-29https://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/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/139Projects without activity that should be considered for termination by EMO2024-03-11T21:37:01ZFrederic Gurrfrederic.gurr@eclipse-foundation.orgProjects without activity that should be considered for termination by EMOWe will use this ticket to track projects identified by @fgurr and @webmaster that have shown none or little activity for some time.
Google sheet with some notes: https://docs.google.com/spreadsheets/d/1rhQrNxInky7nD1NdYj7Pyn02WQJSj3T...We will use this ticket to track projects identified by @fgurr and @webmaster that have shown none or little activity for some time.
Google sheet with some notes: https://docs.google.com/spreadsheets/d/1rhQrNxInky7nD1NdYj7Pyn02WQJSj3TKRsPBIGDZVx8/edit#gid=0
If you wish to nominate a project for consideration please use the following template:
```
- Project Name:
- URL:
- Last commit:
- Last release:
- Reason for nomination:
```
EMO will review the nominated projects based on the following criteria:
- Last commit date and reason for nomination
- Presence of active Project Leads and Committers
- Communication channels activity
- Engagement and responsiveness to EMO and IT teams
- Project status (i.e. incubation/mature)
If the proposed project is found to be "inactive" by EMO we will
- Reach out to PMC and PLs to ask for more information about the project status
- EMO will schedule a termination review
If the proposed project is determined to be stable
- EMO will schedule a progress review
EMO will post a link to the corresponding review ticket in this same issue.Maria Teresa DelgadoMaria Teresa Delgado2023-11-29https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/678soa Terminate SOA2024-03-26T23:42:18ZWayne Beatonsoa Terminate SOAAFAICT, the Eclipse SOA PMC has ceased to function as an effective PMC and the SOA top level project is no longer active or viable.
The PMC has not responded to emails sent to the mailing list (mostly from the EMO) in more than one year...AFAICT, the Eclipse SOA PMC has ceased to function as an effective PMC and the SOA top level project is no longer active or viable.
The PMC has not responded to emails sent to the mailing list (mostly from the EMO) in more than one year. There is no evidence to suggest that the PMC has been providing any oversight for the projects operating under their purview.
Steps:
- [x] Inform the PMC/community via the soa-pmc mailing list
- [x] Restructure remaining subprojects (find replacement top level projects)
- [x] Petition the Eclipse Foundation Board of Directors to revoke the TLP charter
- [x] Retire PMC Leads and PMC Members, committers, and council representatives
- [ ] Archive project resources (e.g., the soa-pmc mailing list)
- [ ] Terminate the project2024-02-28https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/687ee4j.ca 3.02024-03-27T16:02:11ZMaria Teresa Delgadoee4j.ca 3.0<!--
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
[Jakarta Annotations™ 3.0 Release Review](https://projects.eclipse.org/projects/ee4j.ca/reviews/3.0-release-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 **
- [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
- [x] CONTRIBUTING (or equivalent)
Recommended files:
- [x] NOTICES or equivalent (you can use the [Legal Documentation generator](https://www.eclipse.org/projects/tools/documentation.php) available under committer tools)
- [x] CODE_OF_CONDUCT
- [x] 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:
- [x] Build instructions provided
- [x] [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 Delgado2024-03-06https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/664Eclipse WattAdvisor2024-03-19T16:21:36ZMaria Teresa DelgadoEclipse WattAdvisor<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
We are using scoped labels to identify where a project proposal is at any time during the onboarding process. These labels are mapped to the stages shown in the previous image and will define the "state" of this ticket. If you have doubts, just ask.
We'll use the due date of this issue to provide an estimation of the next date the EMO team will checkin with the project team. Sometimes, e.g. during the project creation time, the due date will coincide with the Project Creation date.
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse WattAdvisor](https://projects.eclipse.org/proposals/eclipse-wattadvisor)
Top level project: Technology
## Basic Information
- License: Eclipse Distribution License 1.0 (BSD)
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
Open source projects at the Eclipse Foundation are required to make use of certain Eclipse Foundation services. See the [Handbook](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: **wattadvisor**
- [x] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
- Project organization: https://github.com/eclipse-wattadvisor
- [x] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/wattadvisor-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [ ] Project lead(s) designated (DB)
Milestones:
- [ ] Project created
- [ ] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) starts with an email message being sent to each of the committers listed on the project proposal with instructions on how to engage in the [committer paperwork](https://www.eclipse.org/projects/handbook/#paperwork) process.
Committers should check their emails and complete the paperwork at their earliest convenience. **No project resources are created until at least one committer is fully provisioned.**
_To be completed by the EMO_
- [ ] GitLab ticket state set to Provisioning
## After provisioning
Following provisioning, the project will be ready for initial contribution review. An initial contribution is basically the first set of project code contributions to the new Eclipse project. An initial contribution typically takes the form of an entire existing source code repository or some snapshot of an existing code base.
At this point, the project team might proceed to push their code into the requested repositories or coordinate with Webmaster and EMO to transfer existing ones. Once you've completed this process please notify EMO using this ticket.
_To be completed by the EMO_
- [ ] GitLab ticket state set to Initial Contribution
## IP-check
_To be completed by the EMO_
Once the project has provided their initial contribution:
- [ ] IP check completed
- [ ] GitLab ticket state set to Fully Operational
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoPawel StankiewiczEclipse Webmaster2024-03-06https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/447Eclipse SCM2024-02-12T16:13:58ZBoris BaldassariEclipse SCM
The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#starting).
The following image shows...
The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
We are using scoped labels to identify where a project proposal is at any time during the onboarding process. These labels are mapped to the stages shown in the previous image. If you have doubts, just ask.
We'll use the due date of this issue to provide an estimation of the next date the EMO team will checkin with the project team. Sometimes, e.g. during the project creation time, the due date will coincide with the Project Creation date.
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse SCM](https://projects.eclipse.org/proposals/eclipse-scm) \
Creation review: https://projects.eclipse.org/reviews/eclipse-scm-creation-review \
Top level project: Automotive
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [ ] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to approve the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
Open source projects at the Eclipse Foundation are required to make use of certain Eclipse Foundation services. See the [Handbook](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: scm
- [x] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
GitLab
- Project repository group: https://gitlab.eclipse.org/eclipse/scm
- Project repository: https://gitlab.eclipse.org/eclipse/scm/scm
- Project mailing list: https://accounts.eclipse.org/mailing-list/scm
- Project mailing list: https://accounts.eclipse.org/mailing-list/scm-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
- [x] Architecture Council mentor designated (DB)
Milestones:
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) starts with an email message being sent to each of the committers listed on the project proposal with instructions on how to engage in the [committer paperwork](https://www.eclipse.org/projects/handbook/#paperwork) process.
Committers should check their emails and complete the paperwork at their earliest convenience. **No project resources are created until at least one committer is fully provisioned.**
## After provisioning
Before pushing any code into an official Eclipse project repository, the project team must submit the project’s [initial contribution](https://www.eclipse.org/projects/handbook/#ip-initial-contribution) of project code and wait for the Eclipse Intellectual Property (IP) Team to grant checkin of that contribution.
Project teams interact with the Eclipse IP Team via the IPZilla system using Contribution Questionnaires ([CQs](https://www.eclipse.org/projects/handbook/#ip-cq)).
More information is available in the [Eclipse Handbook](https://www.eclipse.org/projects/handbook/#starting-after-provisioning).
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
## Post-provisioning Checklist
_To be completed by the EMO_
These are the last few things needed to close this issue:
- [ ] [Initial Contribution](link) submitted for review by the IP Team
- [ ] IP team checkin granted
<!-- Quick actions will configure the state of the issue. Leave these. -->Maria Teresa DelgadoWayne BeatonBoris BaldassariMaria Teresa Delgado2024-03-12https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/534Eclipse OpenXilEnv2024-03-04T07:47:43ZBoris BaldassariEclipse OpenXilEnv<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
We are using scoped labels to identify where a project proposal is at any time during the onboarding process. These labels are mapped to the stages shown in the previous image and will define the "state" of this ticket. If you have doubts, just ask.
We'll use the due date of this issue to provide an estimation of the next date the EMO team will checkin with the project team. Sometimes, e.g. during the project creation time, the due date will coincide with the Project Creation date.
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse OpenXilEnv](https://projects.eclipse.org/proposals/eclipse-openxilenv)
Top level project:
## Basic Information
- License: Apache License, Version 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] GitLab ticket state set to Community Review
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
Open source projects at the Eclipse Foundation are required to make use of certain Eclipse Foundation services. See the [Handbook](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [x] The project lead has confirmed the project shortname: openxilenv
- [x] The project lead has requested a project website repository in the comments
- [x] The project lead has confirmed the following project resources are correct in the comment's section
GitHub
- Project repository: https://github.com/eclipse-openxilenv
- Downloads: http://download.eclipse.org/openxilenv
- Archives: http://archive.eclipse.org/openxilenv
- Mailing list: https://accounts.eclipse.org/mailing-list/openxilenv-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [x] Project DB entry created
- [x] Project lead(s) designated (DB)
- [x] Architecture Council mentor designated (DB)
Milestones:
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) starts with an email message being sent to each of the committers listed on the project proposal with instructions on how to engage in the [committer paperwork](https://www.eclipse.org/projects/handbook/#paperwork) process.
Committers should check their emails and complete the paperwork at their earliest convenience. **No project resources are created until at least one committer is fully provisioned.**
_To be completed by the EMO_
- [x] GitLab ticket state set to Provisioning
## After provisioning
Following provisioning, the project will be ready for initial contribution review. An initial contribution is basically the first set of project code contributions to the new Eclipse project. An initial contribution typically takes the form of an entire existing source code repository or some snapshot of an existing code base.
At this point, the project team might proceed to push their code into the requested repositories or coordinate with Webmaster and EMO to transfer existing ones. Once you've completed this process please notify EMO using this ticket.
_To be completed by the EMO_
- [x] Provide project PMI link to start the IP check <br>
Project: [Eclipse OpenXilEnv](https://projects.eclipse.org/projects/automotive.openxilenv)
- [ ] GitLab ticket state set to Initial Contribution
## IP-check
_To be completed by the EMO_
Once the project has provided their initial contribution:
- [ ] IP check completed
- [ ] GitLab ticket state set to Fully Operational
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoWayne BeatonBoris BaldassariMaria Teresa Delgado2024-03-18https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/391Eclipse ArchE2024-03-04T07:46:37ZMaria Teresa DelgadoEclipse ArchE<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
We are using scoped labels to identify where a project proposal is at any time during the onboarding process. These labels are mapped to the stages shown in the previous image. If you have doubts, just ask.
We'll use the due date of this issue to provide an estimation of the next date the EMO team will checkin with the project team. Sometimes, e.g. during the project creation time, the due date will coincide with the Project Creation date.
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse ArchE](https://projects.eclipse.org/proposals/eclipse-arche)
Project creation review: https://projects.eclipse.org/reviews/eclipse-arche-creation-review
## Basic Information
- License: Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [x] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [x] Committers have Eclipse Foundation Accounts
- [x] Eclipse Architecture Council mentor identified
- [x] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
Open source projects at the Eclipse Foundation are required to make use of certain Eclipse Foundation services. See the [Handbook](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [ ] The project lead has confirmed the project shortname: **arche**
- [ ] The project lead has requested a project website repository in the comments
- [ ] The project lead has confirmed the following project resources are correct in the comment's section
<!--
GitLab
- Project repository group: https://gitlab.eclipse.org/eclipse/{project_name}
- Project repository: https://gitlab.eclipse.org/eclipse/{project_name}/{project_name}
GitHub
- Project repository: https://github.com/eclipse/{project_name}
- Downloads: http://download.eclipse.org/{project_name}
- Archives: http://archive.eclipse.org/{project_name}
-->
- Project mailing list: https://accounts.eclipse.org/mailing-list/arche-dev
- Project: [Eclipse ArchE](https://projects.eclipse.org/projects/automotive.arche)
## Post-creation Checklist
_To be completed by the EMO_
- [x] Project created
- [x] Project provisioned (including at least one committer)
- [x] Project lead(s) designated (DB) **--> Andreas Looft still needs to be designated**
- [x] Architecture Council mentor designated (DB)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) starts with an email message being sent to each of the committers listed on the project proposal with instructions on how to engage in the [committer paperwork](https://www.eclipse.org/projects/handbook/#paperwork) process.
Committers should check their emails and complete the paperwork at their earliest convenience. No project resources are created until at least one committer is fully provisioned.
## After provisioning
Before pushing any code into an official Eclipse project repository, the project team must submit the project’s [initial contribution](https://www.eclipse.org/projects/handbook/#ip-initial-contribution) of project code and wait for the Eclipse Intellectual Property (IP) Team to grant checkin of that contribution.
Project teams interact with the Eclipse IP Team via the IPZilla system using Contribution Questionnaires ([CQs](https://www.eclipse.org/projects/handbook/#ip-cq)).
More information is available in the [Eclipse Handbook](https://www.eclipse.org/projects/handbook/#starting-after-provisioning).
Approximately three months after successful completion of this creation review, the EMO will initiate a [progress review](https://www.eclipse.org/projects/handbook/#release-review).
## Post-provisioning Checklist
_To be completed by the EMO_
These are the last few things needed to close this issue:
- [ ] [Initial Contribution](link) submitted for review by the IP Team
- [ ] IP team checkin granted
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Eclipse WebmasterMaria Teresa DelgadoWayne BeatonBoris BaldassariEclipse Webmaster2024-03-18https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/694Eclipse Zenoh-Flow2024-03-27T16:20:55ZMaria Teresa DelgadoEclipse Zenoh-Flow<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be lef...<!--
This template is used by the EMO to track the creation of a project.
If you want to create a new Eclipse open source project start here: https://www.eclipse.org/projects/handbook/#starting
Parts of this issue can initially be left blank.
Set the title of this issue to the name of the proposal
You can delete the comments (or not).
-->
The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#starting).
The following image shows the workflow for [Starting a Project](https://www.eclipse.org/projects/handbook/#starting) at the Eclipse Foundation.
<!--For SPEC projects
![Onbarding Process for Specification Projects](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF_spec.png)
-->
![Onbarding Process](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/raw/main/Template%20Images/Starting_a_project_EF.png)
We are using scoped labels to identify where a project proposal is at any time during the onboarding process. These labels are mapped to the stages shown in the previous image and will define the "state" of this ticket. If you have doubts, just ask.
We'll use the due date of this issue to provide an estimation of the next date the EMO team will checkin with the project team. Sometimes, e.g. during the project creation time, the due date will coincide with the Project Creation date.
## Project
<!-- Proposed project name and proposal link from the PMI -->
Project proposal: [Eclipse Zenoh-Flow](https://projects.eclipse.org/proposals/eclipse-zenoh-flow)
Eclipse Zenoh-Flow Creation Review: https://projects.eclipse.org/reviews/eclipse-zenoh-flow-creation-review
Top level project: IoT
## Basic Information
- License:
- Apache License, Version 2.0
- Eclipse Public License 2.0
<!-- Specification projects only
- Patent License {Patent license}
-->
## Pre-creation Checklist
_To be completed by the EMO_
- [x] Project scope is well-defined
- [x] Top-level Project selected
- [ ] PMC accepts the project (PMC has replied with +1)
- [x] License(s) approved
- [ ] Project name -nor similar names- has NOT been previously used by the team
- [x] Project name trademark approved. [Trademark transfer agreement available here](https://www.eclipse.org/legal/Trademark_Transfer_Agreement.pdf) in case you need it.
- [x] Project lead(s) identified
- [x] Committers identified
- [ ] Committers have Eclipse Foundation Accounts
- [ ] Two weeks of community review completed
<!-- Specification projects only
Being this a specification project, a Spec Committee ballot to aprove the project creation must run for at least one week
- [ ] Specification Committee ballot initiated
- [ ] Specification Committee ballot concluded successfully
-->
## Project resources to be created
_Project Lead involvement needed_
Open source projects at the Eclipse Foundation are required to make use of certain Eclipse Foundation services. See the [Handbook](https://www.eclipse.org/projects/handbook/#project-resources-and-services) for more information on this subject.
- [ ] The project lead has confirmed the project shortname: zenoh-flow
- [ ] The project lead has requested a project website repository in the comments
- [ ] The project lead has confirmed the following project resources are correct in the comment's section
- Project organization: https://github.com/eclipse-zenoh-flow
- [ ] The project Lead has requested to enable the [OtterDog tool](https://gitlab.eclipse.org/eclipsefdn/security/otterdog) to manage their GitHub project.
- Project mailing list: https://accounts.eclipse.org/mailing-list/zenoh-flow-dev
## Post-creation Checklist
_To be completed by the EMO_
EMO internal tasks:
- [ ] Project DB entry created
- [ ] Project lead(s) designated (DB)
Milestones:
- [ ] Project created
- [ ] Project provisioned (including at least one committer)
- [ ] Committer orientation completed (upon request)
## After creation
Once the project is created the [provisioning process](https://www.eclipse.org/projects/handbook/#starting-provisioning) starts with an email message being sent to each of the committers listed on the project proposal with instructions on how to engage in the [committer paperwork](https://www.eclipse.org/projects/handbook/#paperwork) process.
Committers should check their emails and complete the paperwork at their earliest convenience. **No project resources are created until at least one committer is fully provisioned.**
_To be completed by the EMO_
- [ ] GitLab ticket state set to Provisioning
## After provisioning
Following provisioning, the project will be ready for initial contribution review. An initial contribution is basically the first set of project code contributions to the new Eclipse project. An initial contribution typically takes the form of an entire existing source code repository or some snapshot of an existing code base.
At this point, the project team might proceed to push their code into the requested repositories or coordinate with Webmaster and EMO to transfer existing ones. Once you've completed this process please notify EMO using this ticket.
_To be completed by the EMO_
- [ ] GitLab ticket state set to Initial Contribution
## IP-check
_To be completed by the EMO_
Once the project has provided their initial contribution:
- [ ] IP check completed
- [ ] GitLab ticket state set to Fully Operational
<!-- Quick actions will configure the state of the issue. Leave these. -->
<!-- Specification projects only
/label~"ballot
-->Maria Teresa DelgadoMaria Teresa Delgado2024-03-20https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/685automotive.bluechi 2024.022024-03-28T15:00:04ZMaria Teresa Delgadoautomotive.bluechi 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 BlueChi Graduation Review 2024.02](https://projects.eclipse.org/projects/automotive.bluechi/reviews/graduation-review-2024.02)
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:
- [x] Project is operating within the mission and scope defined in its top-level project’s charter
- [x] Project is operating within the bounds of its own scope
- [x] Project is operating in an open and transparent manner
- [x] 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
- [x] 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-03-20https://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-20