From: Jacob Lifshay <programmerjake@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org
Date: Sun, 13 Jul 2025 08:56:27 -0700
Message-ID: <B208E7B9-0241-40D6-B061-564EB7505EE9@gmail.com> (raw)
In-Reply-To: <20250713114357.GD29660@pb2>
On July 13, 2025 4:43:57 AM PDT, Michael Niedermayer <michael@niedermayer.cc> wrote:
> Hi all
>
> Do people want Forgejo or Gitlab on code.ffmpeg.org for testing?
i'll note that I ran into some important upsides and downsides with both of those when picking which to use for projects i've worked on, hopefully this info is useful for ffmpeg:
* gitlab just recently decided their open source version won't be supporting pull mirroring (where the server actively pulls every so often from a remote repository):
https://gitlab.com/gitlab-org/gitlab/-/issues/23166#note_2620944560
* forgejo doesn't yet support scoped permissions for oauth, so if you use a forgejo account for authenticating with some website/program, that effectively gives that website/program full permissions to anything you can access/modify through your forgejo account (it says administrative privileges, so maybe even more than that?):
https://forgejo.org/docs/latest/user/oauth2-provider/
(not to be confused with using e.g. google to log into your forgejo account which afaik has no significant issues)
* forgejo's runner (for CI) is almost completely compatible with github actions (though forgejo doesn't aim for compatibility), so that makes running CI easier in some ways since iirc basically every github action I've tried on forgejo just works.
Jacob
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-13 15:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 11:43 Michael Niedermayer
2025-07-13 11:49 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 11:58 ` Timo Rothenpieler
2025-07-13 15:57 ` Michael Niedermayer
2025-07-13 16:07 ` Timo Rothenpieler
2025-07-13 16:15 ` Timo Rothenpieler
2025-07-13 18:51 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 19:03 ` Yalda
2025-07-13 14:38 ` Rémi Denis-Courmont
2025-07-13 15:56 ` Jacob Lifshay [this message]
2025-07-13 15:58 ` Timo Rothenpieler
2025-07-13 17:35 ` Michael Niedermayer
2025-07-13 18:04 ` Ronald S. Bultje
2025-07-13 19:47 ` Timo Rothenpieler
2025-07-13 21:47 ` Michael Niedermayer
2025-07-13 22:07 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 21:55 ` Philip Langdale via ffmpeg-devel
2025-07-13 22:04 ` Timo Rothenpieler
2025-07-13 22:22 ` Marvin Scholz
2025-07-14 2:43 ` Zhao Zhili
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B208E7B9-0241-40D6-B061-564EB7505EE9@gmail.com \
--to=programmerjake@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git