From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id E42A14BEDF for ; Sat, 26 Jul 2025 20:14:19 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 898F468CF18; Sat, 26 Jul 2025 23:14:15 +0300 (EEST) Received: from btbn.de (btbn.de [144.76.60.213]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 15F6E68C7F8 for ; Sat, 26 Jul 2025 23:14:08 +0300 (EEST) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id 462052819FB90 for ; Sat, 26 Jul 2025 22:14:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1753560847; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qEE2DV6svXdlta6N4UW+JrlTdw65UKCIDL/ApigHhOw=; b=kFsuyYNcdan946ftjCS+4VO8SN6BKoxJfAIL8rolj0AmNeI4Y/GTKYNNffH6QIc9n020JZ wxZUcwBboNpqsl+OnxM5Mpf/urjl2axSPWLLeNcqWLkAqvXreXkzDhWaVe2Ag7gs5fHSyg GSr++R4mgpVGas0PGmb9BvSQtqxj0MSXKCo1qreUjCVm2HPdQ66AX/fj/J1q5FXTt1O9O2 1MPr4Q1qzeT7AsAggkcdARQ69GXrdZr7503T8D4eTGEhk+9eRpspdHh8KVkZYfHaYvTYxU DoXo7mupLCDF8Lw7076RQr+KmlRF672IagXNWhYHfbOswyAP4cctSIXBz3GN9A== Message-ID: <8ec2eab1-1a2e-4607-9186-3d55c9335e3a@rothenpieler.org> Date: Sat, 26 Jul 2025 22:14:08 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: <20250722035337.2216565-1-dev@lynne.ee> <577d17cb-a056-49c0-bf71-870e00684b37@gmail.com> Content-Language: en-US From: Timo Rothenpieler In-Reply-To: <577d17cb-a056-49c0-bf71-870e00684b37@gmail.com> Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 7/26/2025 10:01 PM, Derek Buitenhuis wrote: > On 7/26/2025 8:29 PM, Timo Rothenpieler wrote: >> It's still an extended test. You cannot push to it, since it's just a >> mirror. > > That's not what written in the announcement, and the fact it is "still > a test" has not been communicated on this list, to my knowledge. It's > all about as clear as mud... > > It's possible I am the only one dumb enough to miss that fact, but I suspect > (hope) probably not. It's what the whole vote was about, the vote was not "Let's migrate to this", but "Let's put this through a more extended test". So I'd say the list was very much informed about that? >> How do you expect to suddenly switch every last person over from the ML >> to a new tool? > > You do it once, decisively, with no point where it is both dev paths simultaniously. > VideoLAN managed it, and countless companies and other projects have managed it with > no overlap. Many of which I have experienced first hand. It's one thing to slowly > move projects from an org/community over, but having several extant methods of > contributing and reviewing the same repo's code is pretty much the #1 thing that > is avoided. Videolan hat the exact same transitional period, where both the ML and Gitlab were in use for at least a couple months to half a year. vlc-devel is still active to this day, even with the very occasional stray patch still landing there, just not for patches. I expect this to go similar for FFmpeg. At some point there will be a more strong PSA sent out that Patches via ML will no longer receive the same attention. But so far now is not that time. > This isn't really unique to FFmpeg. > >> There's always going to be a transition period where both are in use, >> gradually shifting. > > ... why? It's not necessary, and is a pretty terrible experience for not > much gain except more time for people to argue. How do you intend to get everybody into one boat to move over all at once? VLC has a central governing body who is able to make such decisions and force the issue if need be. FFmpeg does not, so I don't see who would be able to make such a call, and specially then also have everyone follow it. >> So yes, for now there needs to be eyes on both. > > Unfortunate. > > - Derek > _______________________________________________ > 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".