Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org
Date: Mon, 14 Jul 2025 00:04:48 +0200
Message-ID: <a40e1263-83bf-4331-8afb-e83ac9296780@rothenpieler.org> (raw)
In-Reply-To: <20250713145520.4dbdd425@fido7>

On 7/13/2025 11:55 PM, Philip Langdale via ffmpeg-devel wrote:
> On Sun, 13 Jul 2025 13:43:57 +0200
> Michael Niedermayer <michael@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
>>
> 
> F.
> 
> I do not actually have a strong opinion, but I know Timo already got
> Forgejo set up, and so we should take advantage of that.

I want to point out that I primarily set up Forgejo since I have never 
done so before, while I have some limited experience with Gitlab from work.
And since I figured more people had never used Gitea/Forgejo before than 
Gitlab, a test instance made sense to me.

I can set up Gitlab in the span of one evening in place of Forgejo, so 
Forgejo already being there should not be a criteria.
_______________________________________________
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".

  reply	other threads:[~2025-07-13 22:05 UTC|newest]

Thread overview: 24+ 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
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 [this message]
2025-07-13 22:22 ` Marvin Scholz
2025-07-14  2:43   ` Zhao Zhili
2025-07-14  5:50   ` Steven Liu
2025-07-14  9:40 ` Hendrik Leppkes
2025-07-14  9:54 ` Lynne
2025-07-14  9:57 ` Gyan Doshi

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=a40e1263-83bf-4331-8afb-e83ac9296780@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --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