Archive retired repos

[vogella]

Would it be possible to archive the outdated repos? I think we did not so in the past to enable maintenance builds but they are unused since a while, so maybe we can do this now?

Example: https://github.com/[eclipse-platform/eclipse.platform.ui.tools](https://github.com/eclipse-platform/eclipse.platform.ui.tools)

cc @HeikoKlare @akurtakov

[HeikoKlare]

Sounds reasonable to me to mark those repositories as archived. I actually thought they were already marked as such, but apparently they are not. If allowing maintenance builds was the reason for not doing it, it is probably not that relevant anymore as their merges into other repositories have been quite a while in the past.

[HannesWell]

I was about to suggest the same and it can be done easily in the otterdog self-service of each organization by the project leads.
Specifically I suggest to archive the following repositories:

• for eclipse-platform (PL: @akurtakov, @iloveeclipse, @HeikoKlare)
  • eclipse.platform.releng
  • eclipse.platform.swt.binaries
  • eclipse.platform.common
  • eclipse.platform.runtime
  • eclipse.platform.ua
  • eclipse.platform.text
  • eclipse.platform.debug
  • eclipse.platform.ui.tools
  • eclipse.platform.resources
  • eclipse.platform.team
• for eclipse-equinox (PL: @tjwatson, @laeubi)
  • equinox.framework
  • equinox.bundles
• for eclipse-pde (PL: myself)
  • eclipse.pde.build
• eclipse-jdt doesn't have inactive repositories

Most of them had their last commit two or even three years ago, only very few had activity about one and a half year ago.

The main question is if anybody is still intending to add back-ports to the maintenance branches. I know that some people from IBM do that occasionally. @MohananRahul or @gireeshpunathil, can you tell for what period you are going back?
If it's unlikely that you will have to update any of the repositories mentioned above, I suggest to archive them now (to make it clear for everyone looking at them and also to speed-up some releng tasks).
In case, nevertheless an update is unexpectedly necessary, we can also unarchive the repositories at that point and just hope in between that it won't be necessary:
https://docs.github.com/en/repositories/archiving-a-github-repository/archiving-repositories

[gireeshpunathil]

@MohananRahul or @gireeshpunathil, can you tell for what period you are going back?

Usually 3 years (for example 4.23 is still in use with our consumers), rarely a little longer for some releases.

I agree to the proposal (archiving now and unarchiving if required).

[HannesWell]

Thanks for sharing your insights.

I agree to the proposal (archiving now and unarchiving if required).

Unless there are objections, I'll create PRs in the next days, when I find time, to archive the listed repos.

[HannesWell]

Just created the following PRs to archive the repos suggested above:

• Archive retired repositories .eclipsefdn#21
• Archive retired equinox.framework and equinox.bundles repositories eclipse-equinox/.eclipsefdn#5
• Archive retired eclipse.pde.build repository eclipse-pde/.eclipsefdn#8