On 7/13/2025 8:04 PM, Ronald S. Bultje wrote:
G, preferably hosted by videolan.
The main issue I have with Videolan Gitlab is the ultra locked down
signup policy.
People appear in Videolan IRC multiple times a week asking to get their
account activated, and only sometimes actually get help. Often they
already waited multiple days.
It's an understandable anti-spam measure, but also extremely hostile to
any potential contributor.
Also, Videolan Gitlab is very often, like at the moment of writing,
EXTREMELY slow.
It just took it over a full minute to render the main page of the VLC
repo, and this isn't the first time I've seen it this slow.
There's periods where it's decently responsive, but I feel like I have
seen it slow more often than fast.
It's probably also bogged down by the flood of LLM scrapers, but there
do not seem to be any countermeasures in place.
On Sun, Jul 13, 2025 at 7:44 AM Michael Niedermayer <mich...@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@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
