Eclipse Muto
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.
Project
Project proposal: Eclipse Muto (originally Chameleon)
Basic Information
- License: Eclipse Public License 2.0
Pre-creation Checklist
To be completed by the EMO
-
Project scope is well-defined -
Top-level Project selected -
PMC accepts the project (PMC has replied with +1) -
License(s) approved -
Project name trademark approved. Trademark transfer agreement available here in case you need it. -
Project lead(s) identified -
Committers identified -
Committers have Eclipse Foundation Accounts -
Eclipse Architecture Council mentor identified -
Two weeks of community review completed
Project resources to be created
Project Lead involvement needed
Comments from the PL regarding project resources:
- We need multiple repositories under an organisation, so a github organization for github.org/eclipse-muto (we have multiple components which will need their repositories under this group. i.e. eclipse-muto/agent, eclipse-muto/composer, eclipse-muto/f1tenth, eclipse-muto/liveui etc. Are we able to create these repositories ourselves or should we request them separately?
- Mailing list https://accounts.eclipse.org/mailing-list/muto-dev is ok.
- We also need a website for eclipse-muto
Post-creation Checklist
To be completed by the EMO
-
Project created -
Project provisioned (including at least one committer) -
Project lead(s) designated -
Architecture Council mentor designated -
Initial Contribution submitted for review by the IP Team -
Committer orientation completed
After creation
Once the project is created the provisioning process starts with an email message being sent to each of the committers listed on the project proposal with instructions on how to engage in the committer paperwork process.
Committers should check their emails and complete the paperwork at their earliest convenience. No project resources are created until at least one committer is fully provisioned.
After provisioning
Before pushing any code into an official Eclipse project repository, the project team must submit the project’s initial contribution of project code and wait for the Eclipse Intellectual Property (IP) Team to grant checkin of that contribution.
Project teams interact with the Eclipse IP Team via the IPZilla system using Contribution Questionnaires (CQs). More information is available in the Eclipse Handbook.
Approximately three months after successful completion of this creation review, the EMO will initiate a progress review.