If I understand correctly, a new pacman.conf will be shipped without community. Eventually the community repo will cease to exist. It might be worthwhile making an announcement post-migration to have users remove that repo from their pacman.conf file.
Ya, that is quite a lot of reorganizing there
lot of testing stuff moved around, then... " The [community] repository will be merged into [extra] and will therefore be empty after the migration."
Hopefully there won't be issues with this kind of migration.
Not really. As always when there is a change made to pacman.conf there will be a resulting .pacnew file that will be needed to be merged. If not you will start receiving error messages when your system tries to pull from the community repo and it is empty.
I'm assumong you're post is the correct information. That said are you guys going to wait til at least Arch finichest reworking their repos? I can't see having 2 reorganizations to deal with at the same time.
We really don't need to do anything, as mentioned. If you read the article carefully, it does say:
All affected repositories will be provided as empty repositories for a transition period after the migration. For regular users, this means that everything works as before.
Which means that everything will continue working normally. The mention of Garuda Migrations, is in case that we really need (or want) to deal with it, which we would do probably, but a few days or weeks later.