Skip to content
GitLab
Open
Issue created by Bruno de Paula Kinoshita@bdepaulaMaintainer

[discussion] Plan for the transition to GitHub

This is an issue to document the steps to be taken, any possible risks and mitigations, responsibilities, etc., for the transition from GitLab to GitHub. Feel free to update the list with other items.

Action list:

  • Discuss the idea
    • done in a few meetings
  • Discuss the location of the new project
    • initially autosubmit/autosubmit, but it's taken, so we will use bsc-es/autosubmit
    • Francesco B. added Bruno to the team, and we are discussing about an Autosubmit team, managed by us so that it's easier to update the list of people with write access to the repo
    • Create the Autosubmit team, and add others
  • Move from GitLab issue & merge request templates, to GitHub issue & pull request templates
  • Move from GitLab workers CICD to GitHub Actions
    • The coverage that's handled by GitLab will have to be moved somewhere like Codecov, for instance
    • Revise "skipped" tests ( per ex, !508 (comment 318531) )
  • Choose a uniform main branch name (AS is master, others are main)
  • Migrate code, issues (? or leave issues where they are) and merge requests
  • Update documentation
    • README
    • Sphinx
    • ES Wiki
    • BSC page (it needs an update too)
    • References in Eduuni
    • GitLab Wiki (besides the README, there are many links there)
  • GitLab Wiki (can we move part or most of the information to GitHub / README / RTD)?
  • Update ReadTheDocs
  • Add the CITATION cff file (a comment from @mgimenez in another issue reminded about this feature in GH) -- done in !472 (merged)
  • Write a migration plan (dates for the real migrate and the switch)
  • Write a communication to share with the users. We have to explain why this is a move that will benefit them in the long-term (sustainability). We have to provide the schedule of the migration, letting some time for them to ask us doubts before it's done.
Edited by Luiggi Tenorio Ku