Eclipse Mission Control
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 Mission Control
Basic Information
- License: Apache License, Version 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
-
The project lead has confirmed the following project resources are correct in the comment's section
-
The project lead has requested a project website repository in the comments
-
Project repository: https://github.com/Adoptium/missioncontrol
-
Project mailing list: https://accounts.eclipse.org/mailing-list/missioncontrol-dev
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
Approximately three months after successful completion of this creation review, the EMO will initiate a progress review.
Activity
changed title from {-https://projects.eclipse.org/proposals/a-}doptium-mission-control to Adoptium Mission Control
Thanks for creating this @mdelgado624
Very exciting to see this project proposal. I'm very happy to see the work that has been underway at AdoptOpenJDK come to the Eclipse Foundation.
A couple of points come to mind.
- The proposal states:
JDK Mission Control is built using source from https://github.com/openjdk/jmc. While we don't need to to mirror this repo to the Adoptium project, the builds of Eclipse Mission Control that we ship will be shipped under the The Universal Permissive License (UPL), Version 1.0 (see https://github.com/openjdk/jmc/blob/master/license/LICENSE.txt)
Adoptium is working towards a secure engineering practice that manages third-party dependencies quite closely. Having a mirror would be beneficial in this regard by ensuring that the builds are reproducible and identifiable, since local builds will not depend upon the upstream repository being immutable in perpetuity. This would follow the same model for Eclipse Temurin builds.
- What resources does the project predict will be required? The Adoptium Working Group manages a budget for the Adoptium TLP projects expenses in infrastructure (builds, website, distributions sites etc), licenses and logos, marketing, and so on. It would be helpful to have an idea of the Eclipse Mission Control expectations for this support over the near term.
Thank you for raising this proposal!
@shmacdonald please initiate trademark search for the Eclipse Mission Control project.
@mmilinkovich the Eclipse Mission Control needs your your approval for the selected licensing scheme: Apache License, Version 2.0.
marked the checklist item Project name trademark approved. Trademark transfer agreement available here in case you need it. as completed
I'll add myself as mentor. With that, the requirements have been met, and I declare this creation review successful. I will initiate the project provisioning process shortly.
Can I get the project leads to confirm the resources that you'll need for the project?
Do you need any new Git repositories, or will you be transferring existing content into the project?
Does the project need a website (e.g.
eclipse.org/missioncontrol)?We're using "mc" as the short name for the project; following our usual practices, the project mailing list would therefore be
mc-dev@eclipse.org. Does this work, or do you have another preference?You can work out CI/build with the CBI team after the project is up-and-running.
Regarding Git repositories, I assume that the repos for the build overrides will be transferred from AdoptOpenJDK. Patrick Reinhart (https://github.com/reinhapa) will know more.
A website to replace https://adoptopenjdk.net/jmc would be good, and also a good place to host the update sites for additional content, but I'm not 100% sure what the thoughts are with AdoptOpenJDK vs Adoptium/Eclipse JMC here.
The mailing-list sounds good; I assume it will be mostly about branding and building.
Some binary release projects of Mission Control (like Zulu Mission Control, Liberica Mission Control) override some things like splash screen, icons and certain strings. If Eclipse Mission Control will do that, then that content will need to be produced.
@wbeaton from my point of view the suggested website and mailing list names are ok from my side.
I think that we may need to see where what an optimal place for later mission control eclipse optional plugins will be. But this has not the topmost priority right now.
removed Trademark Approval Request label
added EDPProvisioning label and removed EDPCommunityReview label
The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project:
Source Code Management:
As your project's main Git repository is hosted at GitHub, we will need to move it to an Eclipse organization. This work can begin as soon as you have check in permission from EMO legal.
Issue Tracker:
Github issues will remain enabled for your project.
Outbound Communication:
Mailing list: https://accounts.eclipse.org/mailing-list/mc-dev
Project Website repository:
ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/mc.git
Commits will be published to www.eclipse.org/mc within 5 minutes
Downloads: http://download.eclipse.org/mc
Archives: http://archive.eclipse.org/mc
Builds: You can upload releases to mc via SFTP or SCP from a CI instance at Eclipse.org
Older builds should be moved to the archives area when they are no longer required
added EDPInitial Contribution label and removed EDPProvisioning label
removed Review Request label
added Successful label
@preinhartw2s it has been a while since this project was provisioned. Can you provide a status update of the project initial contribution?
Hey @preinhartw2s we still haven't received any updates on the project's initial contribution. Is there anything we can do to support you in the process?
Hi @mdelgado624 sorry for the delay. Since the provision we have already made a initial release of Mission Control 8.2.0
So in that regard the transition was successful so far. The next steps would involve one or more of the following points, where additional help would be appreciated:
- Optional branding of the Mission Control for Eclipse
- Update the splash screen for Eclipse Mission Control
- Provide Eclipse Marketplace integration
- Provide Eclipse Update Site for the released and future Versions
I hope this answers your questions so far...
Hey @preinhartw2s I think there has been a misunderstanding of the Eclipse Development Process regarding the Initial Contribution and Project Release
You were supposed to make an initial contribution (IC) before any code was committed to the repository. The IC review process starts by creating a CQ. The IP Team reviews the initial contribution to ensure that it hasn’t been copied inappropriately, that licenses are being used correctly, and so forth. There is more information in the Eclipse Handbook.
After that, when the project has been cleared to checkin their code and is ready to make a release, the PLs need to get in touch with the EMO to schedule one. There is also a process there that we need to follow.
I'll discuss with @wbeaton to see how we can solve this. I think it would be a good idea to organize a Progress Review to bring the project up-to-speed regarding the EDP.
/cc @wbeaton
@mdelgado624 we both missed the initial contribution. It's here and it's been approved.
I'll wrestle the repository into EF management.
So let's move on from this issue. Can you please initiate a progress review?
@preinhartw2s apologies for missing your IC. At this point I believe we can close this issue.
I've scheduled a progress review for the Eclipse Mission Control Project.
- Here is the review record: https://projects.eclipse.org/projects/adoptium.mc/reviews/2022.06-progress-review
- and the GitLab issue we'll be using to track the status of the review: #324 (closed)
added EDPOperational label and removed EDPInitial Contribution label
