"Archive" merged repositories

[iloveeclipse]

We've merged few repos in platform/pde/equinox but the "old" repositories are still there in github and still allow users to create PR's and bugs. Github provides "Archive this repository" action in settings, which makes interactions with archived repo not possible.

We should adk foundation to perform this for the obsoleted repos below.

See https://github.com/iloveeclipse/bytecodeoutline for an example of archived repo.

To be archived:

• https://github.com/eclipse-platform/eclipse.platform.team
• https://github.com/eclipse-platform/eclipse.platform.resources
• https://github.com/eclipse-platform/eclipse.platform.runtime
• https://github.com/eclipse-platform/eclipse.platform.ui.tools
• https://github.com/eclipse-equinox/equinox.bundles
• https://github.com/eclipse-equinox/equinox.framework
• https://github.com/eclipse-pde/eclipse.pde.build
• TBC

[akurtakov]

+1 I am fine with that.

[tjwatson]

+1

[HannesWell]

In the past it was argued that the old repos will maybe be used for maintenance work (see for example eclipse-pde/eclipse.pde.build#10 (comment)).
Personally I have no intended to do that and would therefore be fine to archive them, but I don't know if others have plans in the area. AFAIK IBM had interest in that in the past, but I don't know if this is still the case. Maybe @vik-chand or Tom can tell?

[akurtakov]

As no one objected I think the proper thing to do is subproject PLs to open helpdesk issues as I believe this is not within our powers.

@iloveeclipse Would you please handle Platform?

[vogella]

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4071

[merks]

This can be achieved self-serve, but the last time I tried that we decided not to do that:

eclipse-platform/.eclipsefdn#3

Did something change in the meantime?

[vogella]

I only saw the pmc approval in this issue and don't know anything more

[merks]

I discussed with Alex just now. It's easy to mark a repository as archived and it's easy to undo it in the future if necessary. I'm personally happier to see things marked archived because it's much more clean that the repository is not of interest.

The otterdog stuff is really quite easy to manage ourselves:

https://github.com/eclipse-platform/.eclipsefdn/blob/main/otterdog/eclipse-platform.jsonnet

[vogella]

Thanks @merks for keeing in eye out for us.

[MohananRahul]

Can we undo archive https://github.com/eclipse-platform/eclipse.platform.runtime repos , we are using this repo for our maintenance work.

[merks]

Because it appears the changes were not done by modifying the otterdog file, I don't see the changes reflected in that file so I don't know how to undo what was done simply by editing this:

https://github.com/eclipse-platform/.eclipsefdn/commits/main/otterdog/eclipse-platform.jsonnet

In the future, please let's learn to use this file so we can do things ourselves. Information about this has been shared with everyone:

https://www.eclipse.org/lists/cross-project-issues-dev/msg19715.html

I know it's unrealistic to expect folks to read what I post.

[merks]

Because I cannot reopen

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4071

I've opened this issue:

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4072

[merks]

@MohananRahul

Please make clear on https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4072 what exactly all needs to be undone.

[MohananRahul]

@MohananRahul

Please make clear on https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4072 what exactly all needs to be undone.

Sure, Thanks