FFmpeg moves to Forgejo

#1

Post by whataguy » Wed, Aug 13, 2025, 11:08 AM UTC

FFmpeg moves to Forgejo
code.ffmpeg.org

Re: FFmpeg moves to Forgejo

#2

Post by ec109685 » Sun, Aug 17, 2025, 1:42 AM UTC

Why did it move to Forgejo?

Re: FFmpeg moves to Forgejo

#3

Post by bhaney » Sun, Aug 17, 2025, 1:44 AM UTC

I'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.

Re: FFmpeg moves to Forgejo

#4

Post by bigfishrunning » Sun, Aug 17, 2025, 1:47 AM UTC

bhaney wrote: post #3

I'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 would you have to migrate? If you're happy with Gitea just stay there.

Re: FFmpeg moves to Forgejo

#5

Post by Incipient » Sun, Aug 17, 2025, 1:48 AM UTC

bhaney wrote: post #3

I'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.

I use gitea and it "just works". I'm definitely not going anywhere.

Re: FFmpeg moves to Forgejo

#6

Post by bigfishrunning » Sun, Aug 17, 2025, 1:48 AM UTC

ec109685 wrote: post #2

Why did it move to Forgejo?

They were using an old fashioned mailing list to pass patches around, I would imagine features like pull requests and issue tracking made forgejo an attractive option

Re: FFmpeg moves to Forgejo

#7

Post by kjeldsendk » Sun, Aug 17, 2025, 1:51 AM UTC

ec109685 wrote: post #2

Why did it move to Forgejo?

The list seems long? https://forgejo.org/

Re: FFmpeg moves to Forgejo

#8

Post by stepupmakeup » Sun, Aug 17, 2025, 1:51 AM UTC

bhaney wrote: post #3

I'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.

All 3 are still under active development.

Re: FFmpeg moves to Forgejo

#9

Post by 000ooo000 » Sun, Aug 17, 2025, 1:51 AM UTC

bhaney wrote: post #3

I'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.

[flagged]

Re: FFmpeg moves to Forgejo

#10

Post by homebrewer » Sun, Aug 17, 2025, 1:52 AM UTC

bhaney wrote: post #3

I'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.

We've been using gitea for 6 years, and I see no reason to migrate anywhere at this moment. Gitea sees faster development and has more features (even though many patches flow to Forgejo — the reverse is impossible due to license restrictions).

It is possible to migrate from 1.22 to Forgejo simply by changing the binary, and downgrading from 1.24 to 1.23, and from 1.23 to 1.22 is possible if you know your way around PostgreSQL and have a spare hour. I always write downgrade scripts for each release and test them before upgrading Gitea to make sure that I can always back out and move to Forgejo if Gitea folds. Haven't seen much reason to do it up to this moment, though.

edit: for example, here's a 1.23 → 1.22 downgrade script; I don't have access to 1.24 → 1.23 atm:

https://paste.debian.net/plainh/7d8cab27