[WIP] Big Bang TODO List

[iHiD]

These are steps to be completed as part of the big bang. These should be done in order.

• Disable v2 website webhooks (tracks and website copy)
• Merge exploded repo PR in v3-website
• Rename master to main
  • All track repos
  • All track tooling
  • https://github.com/exercism/website-copy
  • https://github.com/exercism/configlet
  • https://github.com/exercism/canonical-data-syncer
  • https://github.com/exercism/github-actions
  • https://github.com/exercism/request-new-language-track and any templates within it.
• Rename automated-comments dir to analyzer-comments in website-copy
• Rename docs to legacy-docs
• Rename v3-docs to docs
• Rename website to v2-website
• Rename v3-website to website
• Rename configlet to configlet-legacy
• Rename canonical-data-syncer to configlet
• Archive this repo
• Remove TODOs in Erik's big script
• Run Erik's big script

[wolf99]

Will the v2 repos existing docs have their links to the central v2 docs updated to reflect the change there to legacy-docs, or will this need to be updated on a per repo basis?

[iHiD]

Great question. Two thoughts:

1. I intend for the new docs to be rendered on the Exercism website and for links to point there, rather than to GitHub. So at some point before launch, my intention would be update any legacy docs references to point to the Exercism website instead of GitHub.
2. I'm going to be going through the whole existing docs repo and cutting/pasting things that are still relevant into the new docs repo. A huge amount has changed as part of v3, and I want to restructure the repo entirely, so there will be a lot of links that are no longer relevant, and others that change in location.

I think for both things, it's perfectly reasonable to consider that we can script all these changes, and that maintainers should probably just need to do a final check on their repos to ensure things are all still correct. @ErikSchierboom Could you add scripting this to your pre-launch checklist pls.

[ErikSchierboom]

Added

[ghost]

@iHiD or @ErikSchierboom will the "big script" migrate a track's open issues? The Rust track has a number of them that are still relevant: https://github.com/exercism/v3/issues?q=is%3Aopen+is%3Aissue+label%3Atrack%2Frust.
If the script will not, I can gladly port them to @exercism/rust. I would reorganize them a bit too since they have stale data.

[iHiD]

It will not, because it's not in the API. However, I am planning on doing it manually on Friday, as once the repo is archived we won't be able to. If you want to do that before Friday, I'd be super-grateful. But don't use up your valuable exercise-writing time on it :)

[ghost]

@iHiD I transfered all the Rust's track open issues to @exercism/rust.
I was unable to find a way to do so in bulk. The linked tool discussed here does not retain comments. So I followed GitHub's primary guide.

[iHiD]

Thank @efx - yeah, it's a manual process that I'm about to embark on with @nicolechalmers! Thank you 💙