Scheduling migration from Microsoft GitHub to Codeberg: Request for feedback
Hello together, I am interested in your opinions and thoughts about this. I have mentioned this before. The project needs to migrate away from Microsoft GitHub. The current target would be Codeberg e.V., which hosts Forgejo (a successor to Gitea). I wonder if it might be a good plan to do the migration after the 1.6.0 release, which is scheduled for spring or early summer 2026. I see no good reasons against it. Technically, I do not expect much problems. The migration works very well and offers several options. Logistically I also don't expect much problems. The repo at Microsoft GitHub will have a clear migration statement on top of the README file and will be set to read-only. I'll also inform all known distro maintainers about the migration. Mirroring is definitly not an option. I would keep the repo on Microsoft GitHub available (but read-only) for a limited time (one or two years) and then remove it. What do you think? If you plan some donations around Christmas time maybe Codeberg e.V. might be a good choice. Christian
Hi Christian and all, I think moving to Codeberg is the correct and best solution. I also don’t prefer to develop projects under GitHub and deserted the place long time ago. Finishing a development cycle and moving to Codeberg sounds nice. It’s also polite to the people following the project and contributing to it. Also maybe announcing it beforehand can be arranged, but I’m not so sure about that. Just a food for thought. I don’t think it’s necessary to delete GitHub repositories after 2 years. Update the README.md files, point people to the right direction, archive the repo and let it get dusty. I generally do it like that, because I don’t want tp break old links around the internet. There’s no need to mirror to Microsoft’s GitHub. People should understand that there are other software forges around and GitHub has no monopoly over it. Oh, also, you can start the new bug report numbering in Codeberg from where the GitHub issues are left, so things don’t get confusing. Hope this helps, Cheers, H.
On 28 Nov 2025, at 08:53, c.buhtz@posteo.jp wrote:
Hello together,
I am interested in your opinions and thoughts about this.
I have mentioned this before. The project needs to migrate away from Microsoft GitHub. The current target would be Codeberg e.V., which hosts Forgejo (a successor to Gitea).
I wonder if it might be a good plan to do the migration after the 1.6.0 release, which is scheduled for spring or early summer 2026.
I see no good reasons against it. Technically, I do not expect much problems. The migration works very well and offers several options. Logistically I also don't expect much problems. The repo at Microsoft GitHub will have a clear migration statement on top of the README file and will be set to read-only. I'll also inform all known distro maintainers about the migration.
Mirroring is definitly not an option. I would keep the repo on Microsoft GitHub available (but read-only) for a limited time (one or two years) and then remove it.
What do you think?
If you plan some donations around Christmas time maybe Codeberg e.V. might be a good choice.
Christian _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3//lists/bit-dev.python.org Member address: hakan@bayindir.org
participants (2)
-
c.buhtz＠posteo.jp -
Hakan Bayındır