Eclipse EBR restructuring and Termination review
The EMO is using this issue to track the progress of a project restructuring and termination review.
Eclipse Orbit restructuring review & EBR Termination review PMI record: https://projects.eclipse.org/projects/rt.ebr/reviews/termination-review-and-eclipse-orbit-restructuring-review
After discussion with EMO and the Eclipse Orbit project this review will combine a restructuring review that moves the resources for EBR to Eclipse Orbit and a termination review for EBR. Orbit would like to continue using the EBR Maven plug-in.
When EBR was created many years ago there was a huge demand for OSGi bundles. The EBR project came up with a solution to make Maven artifacts easily consumable from p2-enabled OSGi applications. However, it never really fulfilled the role of becoming a rich source for recipes. Today the primary customer of EBR is Orbit and Eclipse (via Orbit).
Project
Project: Eclipse Bundle Recipes Restructuring and Termination Review
Restructuring checklist (for Orbit)
- EMO(ED) approval
- Email sent to the community using MLs and other communication channels (TBD by the project team)
Pre-Termination Review Checklist
To be completed by the EMO
- PMC has been notified
- Project team has been notified via dev-list
- Project team has been notified via email
Post-Termination Checklist
To be completed by EMO
- Retire committers and project leads relationships (PMI)
- Retire Mentor relationships (Database)
- Archive the project (PMI)
- Archive the project (Database)
To be completed by Webmaster
Shutdown/archive:
- Website
- Git repositories
- Mailing list
- Forum
- Bugzilla product
Your comments, feedback, and pushback are welcome.
Activity
added Review Request Termination review labels
assigned to @wbeaton and @mdelgado624
added restructuring label
@mmilinkovich we need your approval for this restructuring review:
After discussion with EMO and the Eclipse Orbit project this review will combine a restructuring review that moves the resources for EBR to Eclipse Orbit and a termination review for EBR. Orbit would like to continue using the EBR Maven plug-in.
added Successful label
This termination/restructuring review has concluded successfully.
@webmaster please proceed to move the relevant project resources from EBR to the Eclipse Orbit project and archive the rest. All committers from EBR are already committers of the Orbit project, so nothing to do there AFAICT.
/cc @gunnar
assigned to @webmaster
@webmaster I am not sure if there is an explicit list of which resources to move, but as a minimum the Orbit project would like the following migrated:
- git repo: https://github.com/eclipse/ebr (this can be moved to eclipse-orbit organization at a time convenient to you as the rest of Orbit is scheduled to move to github in March, see #2438)
- jenkins: there is only one job on EBR's Jenkins instance, if possible moving that to Orbit's instance would be great https://ci.eclipse.org/ebr/job/ebr-maven-plugins/ (this job deploys to nexus, so may need secrets migrating/updating?)
- nexus: if possible we want to maintain the existing EBR names and publishing location https://repo.eclipse.org/content/groups/ebr/
These resources are not used and can be archived:
- website: https://www.eclipse.org/ebr/
- downloads: https://download.eclipse.org/ebr/
- dev mailing list: https://accounts.eclipse.org/mailing-list/ebr-dev
Let me know if there are other parts of the project that need decisions made.
Thanks for your support!
added team:releng label
So one roadblock is that the eclipse-orbit organization already exists on Github, and isn't controlled by the Foundation. I've reached out to the listed contact to see if they're willing to either transfer or rename it.
The second is that the notification I received about this was kicked off when EBR no longer had any committers, and so it was treated as a standard project archive. Which is a fancy way of saying that project resources were archived/shutdown via our standard process, which makes transferring them a bit tricky at this time.
The releng team and I will need to discuss the options.
Apologies if I’ve caused this confusion. I thought it was clear that EBR resources needed to be transfer to Orbit before creating the tarball. Let me know if there is anything I can do to help here @webmaster.
Hi @mward, I am currently blocked on completing IP process updates in Bug 581504. At the moment it isn't critical, but it can easily become critical in the next week or two as we prepare for the final builds of 2023-03.
Therefore while we are waiting on getting the eclipse-orbit org on GitHub can the eclipse/ebr repo have its permissions corrected so that I can commit to it (as an Orbit committer). (Or can you create a different org name and rename it if you get ownership?)
I also need the https://ci.eclipse.org/ebr/job/ebr-maven-plugins/ job so that I can build and deploy what is part of Bug 581504
Please let me know what I can do to unlock this.
I've updated the PMI to set github.com/eclipse/ebr as part of the Orbit project so committers that have added their Github IDs to their Eclipse.org accounts should receive access the next time the sync tool runs.
@fgurr were you able to make any headway in restoring the EBR JIRO instance?
Thank you @mward - my permissions are working now.
@fgurr yes please, this is what I was originally thinking:
jenkins: there is only one job on EBR's Jenkins instance, if possible moving that to Orbit's instance would be great https://ci.eclipse.org/ebr/job/ebr-maven-plugins/ (this job deploys to nexus, so may need secrets migrating/updating?)
@fgurr any update on restoring this job?
The job has been migrated:
=> https://ci.eclipse.org/orbit/job/ebr-maven-plugins
You might want to tweak the job configuration slightly (e.g. do not send emails to the ebr-dev mailing list).
Thank you Fred. The job looks great and I have removed the email notification. The permissions/etc all look good to because the job published successfully to repo.eclipse.org the new 2.0 snapshots (https://repo.eclipse.org/service/local/repositories/ebr-snapshots/content/org/eclipse/ebr/ebr-maven-plugin/2.0.0-SNAPSHOT/).
So one roadblock is that the eclipse-orbit organization already exists on Github,...
@mward - the above roadblock looks like it is progressing as https://github.com/eclipse-orbit now does a 404.
Yes, rather than transfer it the previous owner chose to delete it, which will free it up for us to claim in the future(roughly 4 months from now according to Github support when I asked why I couldn't 're-create' the organzation at this time). I've added a calendar event to try and create it in the future.
Thanks @mward.
@mdelgado624 AFAIK the eclipse-orbit GitHub org was the only thing left to do for the restructuring review. As that isn't a requirement and it will take months for it to happen I think this restructuring review is complete now.
