Repository migration in 2026

[redstrate]

Overview

• Kawari development will continue on Codeberg.
• The Codeberg repository will be created on 2026-06-01.
• This GitHub repository will be archived on 2026-06-01, and then deleted on 2026-12-01.
• A migration notice will be in place on this GitHub repository once the migration begins, and in place until the repository is permanently retired.
• Dates are subject to change (depending on my availability) but the general timeline should stay the same length.

Q & A

• Will I need a Codeberg account?
  • Yes. If you don't want the hassle of handling a second password, you can sign in with GitHub.
• Is Codeberg a good fit for the project?
  • Yes. It has everything we need: basic issue management, CI, code review, branch protections, forking and code search. Existing and new contributors should feel right at home - in our new home.
  • Other pieces of our tooling like KawariUpdater and PacketAnalyzer already live on Codeberg!
• Will our CI become worse?
  • Not in any meaningful sense, but the biggest change will be who is paying for the hosting. GitHub (currently) subsidizes public projects, but in our Codeberg repository I'll be paying for CI time out of my own pocket. This currently isn't a huge expense, so I'm not concerned to be honest.
  • We'll still have automatic artifacts, deployment and so on.
• What will happen to existing issues and PRs?
  • If existing issues will be migrated has not decided yet, but a backup of will be made regardless.
  • This question will have a more concrete answer at a later date.
• How will Codeberg be supported, since they are a relatively small & independent organization compared to Microsoft?
  • Personally, I have begun paying yearly dues and joined their e.V. as a member.
  • Although their infrastructure is getting better and better, I do have a mirror on my own infrastructure just in case. It's not like GH has perfect uptime either 🙈
  • The Kawari repository is extremely tiny (only ~4 MB) and the CI is running on my own infrastructure - not on theirs. So our impact is going to be minuscule compared to other projects.
• What will happen to my fork?
  • See the GitHub documentation for when this happens.

If you have any questions or concerns about the migration, please let me know here.