[FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org
Ronald S. Bultje
rsbultje at gmail.com
Sun Jul 13 21:04:15 EEST 2025
G, preferably hosted by videolan.
On Sun, Jul 13, 2025 at 7:44 AM Michael Niedermayer <michael at niedermayer.cc>
wrote:
> Hi all
>
> Do people want Forgejo or Gitlab on code.ffmpeg.org for testing?
>
> F. code.ffmpeg.org should run Forgejo
> G. code.ffmpeg.org should run Gitlab
>
> all GA members can vote, by publically replying here with a
> "F." / "Forgejo" vs "G." / "Gitlab"
> End time is in 7 days unless teh community wants to extend that.
> (or do people want a formal vote to be setup? on vote.ffmpeg.org)
>
> After we decide what to run on code.ffmpeg.org, I intend to
> * apply the CI patches which timo currently keeps rebasing on the Forgejo
> git
> (maybe timo can post these to ffmpeg-devel)
>
> * extend my github cronjob to autosync Forgejo or Gitlab too
> (or someone else can set one up)
>
> * announce code.ffmpeg.org publically so people can start submitting
> and reviewing on it as an alternative to the ML
>
> * and a month or 2 after that we can re-asses how many people use
> code.ffmpeg.org
> and how many use the ML. Then we could decide to keep using both
> in parallel or switch back to ML or just use code.ffmpeg.org. Or in fact
> we could switch between Gitlab or Forgejo here still as well.
>
> thx
>
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker.
> User
> questions about the command line tools should be sent to the ffmpeg-user
> ML.
> And questions about how to use libav* should be sent to the libav-user ML.
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>
More information about the ffmpeg-devel
mailing list