Moving away from Github

[selfhoster1312]

@poVoq suggested if we make a community-maintained fork of matterbridge, we should move away to Codeberg.

Pros:

• more aligned with FLOSS values
• probably aligns with other matterbridge forks who moved away from Github
• Forgejo (Gitea fork) web interface is much more responsive and user-friendly than Github

Cons:

• it's harder to get a codeberg account for other people to report bugs and propose PRs
• Codeberg had problems with intense DDOS in the past rendering the service unusable for days (is that over?)

[selfhoster1312]

@poVoq What is the status of federation in forgejo at the moment? Could people from other instances report bugs and propose PRs or not yet? (i.e. do you need a codeberg.org account specifically to participate?)

If that's supported already i think it's a very reasonable solution to move away right now and not think too much about it. If that's not the case, I would propose a migration plan over several months:

• first reassemble the contributors community on Github, letting them know we plan to move
• after 3 months, move the main development team and the review/CI to Codeberg and keep a Github mirror with issues/PRs open for drive-by contributors
• after 6 months, reevaluate the situation

What do you (and others) think?

[poVoq]

The performance issues of Coderberg are directly caused by Github and it's army of shitty AI scrapers (and similar other companies of course), but they have it more or less under control these days.

Forgejo federation is sadly not anywhere close to being released. Mid of next year the earliest I would guess.

The plan sounds ok.