From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTPS id 6229A44AD3
	for <ffmpegdev@gitmailbox.com>; Sun, 13 Jul 2025 21:55:36 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id B942D68E418;
	Mon, 14 Jul 2025 00:55:31 +0300 (EEST)
Received: from mail.overt.org (mail.overt.org [72.14.183.176])
 by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id F219568E11D
 for <ffmpeg-devel@ffmpeg.org>; Mon, 14 Jul 2025 00:55:24 +0300 (EEST)
Received: from authenticated-user (mail.overt.org [72.14.183.176])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest
 SHA256) (No client certificate requested)
 by mail.overt.org (Postfix) with ESMTPSA id 6A36060A49
 for <ffmpeg-devel@ffmpeg.org>; Sun, 13 Jul 2025 16:55:23 -0500 (CDT)
Date: Sun, 13 Jul 2025 14:55:20 -0700
To: ffmpeg-devel@ffmpeg.org
Message-ID: <20250713145520.4dbdd425@fido7>
In-Reply-To: <20250713114357.GD29660@pb2>
References: <20250713114357.GD29660@pb2>
MIME-Version: 1.0
Subject: Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
From: Philip Langdale via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Philip Langdale <philipl@overt.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/20250713145520.4dbdd425@fido7/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

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.

--phil
_______________________________________________
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".