Skip to content

Moving Indy repos to a new GitHub organization -- hyperledger-indy #3

@swcurran

Description

@swcurran

LFDT has requested that all projects move from the Hyperledger GitHub Organization to one that is specific to the project. In the case of Hyperledger Indy, the new organization is Hyperledger Indy GitHub Organization.

I propose the following process:

  1. Identify and immediately move the repos with no associated GHAs that will have to be migrated -- anything that doesn't need to be fixed after the move.
  2. Identify and plan any relevant GHActions to make sure all of the tests and publishing workflows will still work for the remaining repos after migration.
    • Plan is as much as possible to keep publishing the artifacts to the same locations as now so downstream projects don't need to change.
    • If needed, we can publish artifacts to a second/new location to begin a migration to that -- e.g. GHCR images
  3. Move the repos that have GHActions.
  4. Update the relevant GHActions to make sure all of the tests and publishing workflows still work.
  5. Update documentation in the repos. Check each for changes required by the move.
  6. Update any gh-pages publications so they still work. - This could (for some repos) include replacing the old repo and gh-pages with a redirect to the new location, since gh-pages redirects are not automagic like repos.
  7. Update the impacted LFDT Webpages, calendar invites, wiki pages, etc.

@ryjones @WadeBarnes @SeanBohan @jwagantall @KimEbert42 @lynnbendixsen

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