Skip to content

"Archive" merged repositories #104

Open

Description

@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:

Activity

  1. akurtakov commented on Mar 7, 2023

    @akurtakov
    Member

    +1 I am fine with that.

  2. tjwatson commented on Mar 7, 2023

    @tjwatson

    +1

  3. HannesWell commented on Mar 7, 2023

    @HannesWell
    Member

    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?

  4. akurtakov commented on Mar 20, 2023

    @akurtakov
    Member

    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?

  5. vogella commented on Dec 12, 2023

    @vogella
    Contributor
  6. merks commented on Dec 12, 2023

    @merks
    Contributor

    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?

  7. vogella commented on Dec 12, 2023

    @vogella
    Contributor

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

  8. merks commented on Dec 12, 2023

    @merks
    Contributor

    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

  9. vogella commented on Dec 12, 2023

    @vogella
    Contributor

    Thanks @merks for keeing in eye out for us.

  10. MohananRahul commented on Dec 13, 2023

    @MohananRahul

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

  11. merks commented on Dec 13, 2023

    @merks
    Contributor

    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.

  12. merks commented on Dec 13, 2023

    @merks
    Contributor
  13. merks commented on Dec 13, 2023

    @merks
    Contributor

    @MohananRahul

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

  14. MohananRahul commented on Dec 13, 2023

    @MohananRahul

    @MohananRahul

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

    Sure, Thanks

  15. JavaJoeS commented on Dec 13, 2023

    @JavaJoeS

    Im new here, so if I have misunderstood this discussion, please forgive me. I am currently in the middle
    of adding bundles in the eclipse-platform/teams/bundles; eclipse-platform/eclipse.platform#728
    Im assuming my issue/implementations will need a new location in the platform????

  16. mickaelistria commented on Dec 13, 2023

    @mickaelistria
    Contributor

    Im new here, so if I have misunderstood this discussion, please forgive me. I am currently in the middle
    of adding bundles in the eclipse-platform/teams/bundles; eclipse-platform/eclipse.platform#728
    Im assuming my issue/implementations will need a new location in the platform????

    No, it's all fine. Sticking to eclipse-platform/eclipse.platform#728 is best.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions