Hello bit maintainers & contributors, would migrating to Codeberg from Github be a possibility? I was a bit reluctant to ask this question because I am not a maintainer, and this decision belongs to the maintainers, that said, I have reported some bugs and feedback via Github's issue in the past - and I am really appreciated the responses and questions from maintainers. I no longer can do so because I deleted my Github account. I am no longer confortable using Github (i.e. a proprietary software running on the servers of a privately owned company). I would be confortable again to report (small) hiccups I see (BiT works really well overall) if the repository was hosted on the server of non-profit, for example Codeberg e.V., running a copyleft-licensed software, e.g. Forgejo. If you are wondering what the migration takes, this https://docs.codeberg.org/advanced/migrating-repos/ documents how to migrate from Github to Codeberg (or any other Gitea/Forgejo instances). There is a feature to migrate Issues ("the migration tool can not only migrate your repository data, but also metadata like issues, labels, wiki, releases, milestones, etc"). Again, I imagine the decision belongs to maintainers. Please take this email as an input to the conversation on whether BiT should migrate away from Github.
Hallo Mark, I am one of currently 3 active maintainers. You might know that we are not the founders. We do have write access to the repo but Germar is still the owner of the repos and has the last word and also he will have the workload of that migration. I can't speak for the team but just for myself. I fully support your request and your decision deleting your account at Microsoft GitHub. I also fully understand the reasons and share the concerns. My own projects, where I am the only one maintainer do also exist on Codeberg.org. So you see, that you don't have to convince me about migrating to Codeberg. But when it comes to BIT the situation is more complex. The project is more then 15 years old and has a big user base and also GNU/Linux distro maintainers focused on the Microsoft GitHub account. There is no strict technical reason why we do not migrate. It is more about resources. I am aware that the migration tool works very well. But we do have to communicate a lot. We will face some problems we are currently not aware of, etc. pp. We have to answer some questions, e.g. if TravisCI does support Codeberg projects? If not we need to invest time to migrate to Woodpecker (hosted by Codeberg) or something else. What is about migrated issues? The GitHub users are not notified about the moved issues. So we need to inform them in every currently open issue at Microsoft GH. There are so many tiny details. It is a very big thing for such an old big and hard to maintain project. We still working on ease up the maintenance. For example we drop Coverage.io. We reorganize folder structures. We will remove and integrate the "doc" and "user-callback" repo into "backintime" repo. Migration is on our list. But depending on the other items on that list and the priorities, it won't happen in the near future. Be aware that BIT still use the Weblate translation platform hosted on translate.codeberg.org. So there is a little piece of the project still migrated. :D
I no longer can do so because I deleted my Github account. I am no longer confortable using Github ... I would be confortable again to report (small) hiccups I see
You can also use this mailing list or our personal mail account for reporting problems. By the way: It is recommended to name the devil. Use "Microsoft GitHub" instead of "GitHub". There are a lot of "kids" really not knowing who they are dealing with. Best regards, Christian
Hallo Christian, Thanks a lot for the reply and taking some time to list some of the tasks migrating to codeberg.org would entail. Good to know the translation of BiT is taking place on Codeberg's instance of Webplate.
You can also use this mailing list or our personal mail account for reporting problems.
I will. Thanks for reminding me that we can report problems via the mailing list. Thank you to you three. Mark On Thursday, September 12th, 2024 at 12:10 PM, c.buhtz@posteo.jp <c.buhtz@posteo.jp> wrote:
Hallo Mark,
I am one of currently 3 active maintainers. You might know that we are not the founders. We do have write access to the repo but Germar is still the owner of the repos and has the last word and also he will have the workload of that migration. I can't speak for the team but just for myself. I fully support your request and your decision deleting your account at Microsoft GitHub. I also fully understand the reasons and share the concerns. My own projects, where I am the only one maintainer do also exist on Codeberg.org.
So you see, that you don't have to convince me about migrating to Codeberg.
But when it comes to BIT the situation is more complex. The project is more then 15 years old and has a big user base and also GNU/Linux distro maintainers focused on the Microsoft GitHub account. There is no strict technical reason why we do not migrate. It is more about resources. I am aware that the migration tool works very well. But we do have to communicate a lot. We will face some problems we are currently not aware of, etc. pp. We have to answer some questions, e.g. if TravisCI does support Codeberg projects? If not we need to invest time to migrate to Woodpecker (hosted by Codeberg) or something else. What is about migrated issues? The GitHub users are not notified about the moved issues. So we need to inform them in every currently open issue at Microsoft GH.
There are so many tiny details. It is a very big thing for such an old big and hard to maintain project. We still working on ease up the maintenance. For example we drop Coverage.io. We reorganize folder structures. We will remove and integrate the "doc" and "user-callback" repo into "backintime" repo.
Migration is on our list. But depending on the other items on that list and the priorities, it won't happen in the near future.
Be aware that BIT still use the Weblate translation platform hosted on translate.codeberg.org. So there is a little piece of the project still migrated. :D
I no longer can do so because I deleted my Github account. I am no longer confortable using Github ... I would be confortable again to report (small) hiccups I see
You can also use this mailing list or our personal mail account for reporting problems.
By the way: It is recommended to name the devil. Use "Microsoft GitHub" instead of "GitHub". There are a lot of "kids" really not knowing who they are dealing with.
Best regards, 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: lua8ds@proton.me
participants (2)
-
c.buhtz＠posteo.jp -
Mark Johnno