Migration to Codeberg

[JacksonChen666]

GitHub is a closed-source code forge (for FOSS) with an aim for profit, owned by Microsoft. That's not great, so we are going to move the project to Codeberg and give up on GitHub. This comes in-addition to moving synadm to an organization from a personal account to avoid bus factor issues.

---

With this migration, we ask you to hold off creating issues and PRs, or commenting on any issues while we migrate. If necessary, you can join #synadm:peek-a-boo.at. Please create new issues and PRs on Codeberg, as it is now our primary repository location now.

The repository is now at https://codeberg.org/synadm/synadm. This tracking issue is available on GitHub and Codeberg, and issues/PRs have the same number.

If you have commented on an issue/PR, or created an issue/PR, you can login with GitHub on Codeberg to link your account (for existing accounts, see linked accounts in https://codeberg.org/user/settings/security).

---

This process has no 1-click solution, because we depend on some stuff as well which must be adjusted accordingly (ReadTheDocs for documentation, PyPI for publishing the things, room topics, bots, documentation, links, etc.). This is the plan (which doesn't have to be followed in exact order):

Pre-prep:

• Create an organization
• Wait for @JOJ0 to create a Codeberg account (CI and org access depend on that)
• Organization access stuff
• Figure out the rest of the plan (accidentally closing the browser tab resulted in me losing everything I wrote for this issue, yet again)
• Codeberg CI considerations (requires filing an application for approval and can include additional people)
• Consider order of things (change links before migrating? likely yes)

Prep/Questions:

• GitHub specific README to note we moved (.github/README.md? also include quick link to docs and stuff)
• PyPI metadata (setup.py?)
• RTD integration (https://docs.codeberg.org/integrations/read-the-docs/)
• Docs links?
• Find more references to the GitHub repo
• PyPI trusted publishers Requires tight integration with Codeberg which isn't done yet
• Review migration plan and make sure to prepare stuff

The migration:

• Migrate everything to Codeberg (issues, PRs, releases, etc. https://docs.codeberg.org/advanced/migrating-repos/)
• Make sure everything is OK
• Make everything on Codeberg public
• Matrix room topic changes
• Update links in important places (docs, ?)
• Include Codeberg link in GitHub description (depends on @JOJ0 since I can't do it)
• Archive the GitHub repo (depends on @JOJ0)

Post-migration:

• Update links on matrix.org? (Nope, only TWIM)
• Update more links
• Codeberg CI access request (https://codeberg.org/Codeberg-e.V./requests/issues/665)
• Matrix bot for issues on Codeberg (Codeberg has webhooks but that requires a dedicated account)
• Notify distro package maintainers? (Create release with stuff, then note that the project moved to Codeberg?)

As you might've noticed, this issue is assigned to me. @JOJ0 has shown interest in moving to Codeberg, but has said he don't have much time currently.

If you wish to comment on this issue, you can, but your comments won't be migrated. We also have a Matrix room.