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, 21 Jul 2025 03:03:08 +0200
Message-ID: <2c16af56-e941-46fe-be12-d76167696152@rothenpieler.org> (raw)
In-Reply-To: <20250721005400.GX29660@pb2>

On 7/21/2025 2:54 AM, Michael Niedermayer wrote:
> Hi all
> 
> On Sun, Jul 13, 2025 at 01:43:57PM +0200, Michael Niedermayer 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)
> 
> 7 day period passed,
> 
> Quick count says:
> Gitlab :  3 Votes
> Forgejo: 12 Votes
> 
> 
>>
>> 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)
> 
> timo, ping can you post the patches ?

I'll rebase them into one patch and post them.

> 
>>
>> * extend my github cronjob to autosync Forgejo or Gitlab too
>>    (or someone else can set one up)
> 
> anyone wants to set this up ?

I can add forgejo to my sync cronjobs, yeah.

> 
>>
>> * announce code.ffmpeg.org publically so people can start submitting
>>    and reviewing on it as an alternative to the ML

Just be aware that merging is not possible, since the sync script will 
just force push anything merged away.

> suggestions for news (patch) and twitter announcement welcome!
> 
> thx
> 
> [...]
> 
> 
> _______________________________________________
> 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".

_______________________________________________
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-21  1:03 UTC|newest]

Thread overview: 35+ 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
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
2025-07-14 21:29 ` Alexander Strasser via ffmpeg-devel
2025-07-14 23:51 ` softworkz .
2025-07-15 12:48 ` Leo Izen
2025-07-15 18:09 ` Martin Storsjö
2025-07-15 18:24   ` Frank Plowman
2025-07-16  5:46   ` softworkz .
2025-07-16 10:28 ` Kacper Michajlow
2025-07-21  0:54 ` Michael Niedermayer
2025-07-21  1:03   ` Timo Rothenpieler [this message]
2025-07-21 15:32     ` Michael Niedermayer
2025-07-21  3:30   ` Lynne

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=2c16af56-e941-46fe-be12-d76167696152@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