Consider Archiving and Standardizing

[jonthegeek]

Consider a project to migrate to r4ds/tidytuesday, while keeping an archive of past datasets as-is here.

Why?

• We still have "master" as the default branch.
• Tons of other people's code references exact URLs within this repo (so we can't reorganize).
• READMEs (especially for older datasets) aren't standardized.
• We don't really use the full "rfordatascience" name anywhere other than this repo anymore.

We can update the main README to reference the new home, and update tidytues.day redirects to utilize whatever new structure we come up with.

I imagine we'll need these steps:

• Define a new weekly format and overall repo structure. It should either be pretty solid as far as what we could possibly want... or be really flexible.
• Create new, standardized copies of all standardizable datasets at the new repo. This should be relatively easy using ttmeta.
• Update tidytuesdayR to "think" in the new repo.
• Migrate ttpost into the new repo.
• Update ttmeta to read from the new repo.
• Update this repo's main README to point people to the other repo.
• Consider updating all READMEs here to point to their corresponding README in the new repo.
• Set this repo to read-only.

I think this is a good idea, but I'm going to wait at least a few days before staring on the project in case I change my mind.