The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

[davidak@chaos.social]

The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

https://github.com/go-gitea/gitea/issues/1029#issuecomment-4269181192

At the same time, the community fork @forgejo is self-hosted for a long time and is also powering the popular @Codeberg and at least 8 other public instances. So this seem to be a good time to migrate if you haven't already.

https://forgejo.org

[jean_dupont@mastodon.social]

@davidak @forgejo @Codeberg Fuck nooo!!

[dan@axillae.telent.net]

@davidak @forgejo @Codeberg although not nearly as good a time as two years ago would have been, back when the database schema were still compatible. Oh well ...

[nik@toot.teckids.org]

@davidak @forgejo @Codeberg

It's good for any project to be well-known for something. Even if it's being the most embarassing example for not eating your own dogfood, I guess.

[cinebox@masto.hackers.town]

@davidak @forgejo “we can’t use Gitea because no AI. Also our server keeps going down from the AI crawlers” bruh

[ratsnakegames@mastodon.social]

@dan @davidak @forgejo @Codeberg my strategy of never updating anything keeps paying dividends

[avghelper@gts.average.name]

@davidak @forgejo @Codeberg

"The gap between GitHub and Gitea is larger and larger (including various AI powers). ... Another challenge is the server stability ... due to AI crawlers"

interesting.

[claudius@darmstadt.social]

@nik @davidak @forgejo @Codeberg god you said it so much better than whatever I had in my mind. Why would I trust a project-team that apparently does not even trust its own creation enough to use it?

[blahajj@mastodon.social]

@davidak lol

[moepman@social.troll.academy]

@davidak I would swap gitea for @forgejo right now if there was a documented way to migrate that is not ever user has to move every repo on its own.