The site doesn't load any css for me on mobile, is it really worth it not to use GitHub or gitlab?
It's pretty good on desktop. Report the bug and I'm sure they'll get to it
FFmpeg moves to Forgejo
21–30 of 374 posts
Re: FFmpeg moves to Forgejo
#22The site doesn't load any css for me on mobile, is it really worth it not to use GitHub or gitlab?
I had that issue after it "verified I'm a human", I refreshed and it looked fine.
Re: FFmpeg moves to Forgejo
#23Earlier quoted context omitted.
Why would you have to migrate? If you're happy with Gitea just stay there.
According to Forgejo[1], Gitea underwent a secret hostile takeover by a for-profit company and has been moving from free software to "open core" bullshit. The reason that I, and I assume a lot of other people, made an effort to switch from Github to Gogs/Gitea was to evade the for-profit corpo nonfree crap. The more I'm looking into it, the more it looks like the real development is happening on Forgejo too. [1] http…
A more charitable framing of the situation is: the for-profit company is because people always complained about Gitea "why is it developed on GitHub, not your own hosting" but that means money has to be involved in the cloud hosting project; it is just the same Gitea core developers it has always been, not a takeover.
The "open core" (Gitea Enterprise) is not Gitea, it is a downstream fork by CommitGo, who you can pay for contract development for custom features. The features are expected to be upstreamed, there are open PRs, they just don't yet meet Gitea's code review standards. You can run them from the PRs if you like.
Re: FFmpeg moves to Forgejo
#24The site doesn't load any css for me on mobile, is it really worth it not to use GitHub or gitlab?
How fascinating, the exact same thing happened to me!
Re: FFmpeg moves to Forgejo
#25Earlier quoted context omitted.
Yeah, it's hard to take them seriously when they've been saying very nasty things about the project their whole foundation is built upon, and from where they continue to draw most of their functionality. Gitea is ahead on that despite patches flowing one way only. If you look at forgejo commits, more than half of them are merges of library updates made by the renovate bot, which artificially inflates the level of act…
> it's hard to take them seriously when they've been saying very nasty things about the project their whole foundation is built upon I'm not sure why that would make them hard to take seriously unless the things they're saying are false. Is that what you're claiming? > If you look at forgejo commits, more than half of them are merges of library updates made by the renovate bot, which artificially inflates the level o…
None of the really heavy hitters from the "core team" have left. As long as 100% FOSS Gitea pulls ahead in functionality, and can be downgraded relatively easily with an hour of work, I personally see no reason to move anywhere. You can part in different ways, the vibes you give off certainly matter, even when you're 100% technically correct.
And I suggested comparing releases, not commits; Gitea is ahead here both in what it supported at the moment of the hard fork, and in what has been introduced since then (counting only the MIT version).
Re: FFmpeg moves to Forgejo
#26I'm finding out about Forgejo (and their reasons for forking Gitea) right now for the first time. I already migrated my Gogs install to Gitea, and now I have to migrate Gitea to Forgejo? This shit is why people just stay on Github.
Why leave Gitea just because an alternative exists..
Re: FFmpeg moves to Forgejo
#27How exactly does mailing list contributions work? I've only ever seen a few urls of messages but they are extremely obtuse. You would need to click parent parent parent to get context on the message you originally read.
I must be missing something and since mailing lists are dying, would love to understand this relic of the past.
Re: FFmpeg moves to Forgejo
#28Why did it move to Forgejo?
It sounds like they're still testing but there's this from https://ffmpeg.org/pipermail/ffmpeg-devel/2025-July/346938.h... : ### July 22nd, 2025, Modernization of contributions The project is modernizing its contribution methods and switching to a software forge. We have setup a platform on [code.ffmpeg.org](https://code.ffmpeg.org/). The new process features continuous integration on all commits and merge requests,…
Main link should point to this ...
Re: FFmpeg moves to Forgejo
#29Congrats! I was waiting for them to start using a decent bug tracker.
Re: FFmpeg moves to Forgejo
#30Why not GitHub?