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 BB6054BEFC for ; Sat, 26 Jul 2025 20:28:37 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 79BC368D260; Sat, 26 Jul 2025 23:28:33 +0300 (EEST) Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com [209.85.221.44]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 4268368C4E4 for ; Sat, 26 Jul 2025 23:28:27 +0300 (EEST) Received: by mail-wr1-f44.google.com with SMTP id ffacd0b85a97d-3b7746135acso1224767f8f.2 for ; Sat, 26 Jul 2025 13:28:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1753561706; x=1754166506; darn=ffmpeg.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=W5XYtmTPEoq8pggQxzfItoV0GT1jhG4nMk44ZjSH+bQ=; b=B8+WuXsmGktUePzmEdsMjJhhF+HcAquUH3kMienQMyPVtax13xF22qIDHYfLrj7fty Dd4ZzQgmtIjjC1hGRO1wvNFldxFsLwNI0t9/YaaT+0QHKMrT0xaeMJuBtZU5yVwR1WXo DfZlxeHpAhul6t/6G4/JsqGKPOPnwqm1JIgcCUJ8/ob1gDtmsRcwwk87miQl75wfsICp icPA/2tnBjbUKw9V5NUYGPzYvF0wFhs034MYpvvqUcTGaJgqc/KsEclzEkTJHKHYhXFM LJqCnOi76V9qRUI2KQHzP6tp3U7VEsaJkA20/Gb91rjpltDHWbn9gAeQ69b9LEr+gzoC vc9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753561706; x=1754166506; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=W5XYtmTPEoq8pggQxzfItoV0GT1jhG4nMk44ZjSH+bQ=; b=FUBLgGmNXPEGHWAKIFufddQqQ2toW0P3C8QzILcK1K9lKQcxd+R0fecvNqsZj3KPWG KqIGqlMo+F0BHVRAuNBM4sLpAcv/P2NI8qfahPOCQ8FGoNZkZj/tIGVErYbNU1wrpKZw OBLJ4ks4EZ1rU60ESBZ0hmPay6wH22OTLUSKriNflndIPzg9Lt6cNcEPS/RVial9seBB zXAiCPXzbl04glGIduNWbtiH4Z5DtWZ2eT/xxG+Hj4IeMybkFnqNNVS/5NS9TG8rZWxk sGRmyEDMJESPST1ZNo1XDUvNYfA83cv+upk1cUXB50O0wtZOZ2wDkQLAIEj6WXSquM2N 8Jig== X-Gm-Message-State: AOJu0Ywdulxp6UlyJp1W46KCQk2CTPJA3wKypGEeXYWU5Dwzr+Gyt29g /CY6D7Z4nPTlFITvl9nt7sd37q/QBQDO4Dr02F5n7K2SGQeFEXlFGnZjjys1bw== X-Gm-Gg: ASbGnctZoJJ+Uhd4af8XAzqdsk/hD8Fw6eqGn0Q9TraaLvXp3hNILHmLemzFNGqLKgR RHGTghcDtYmkoM7HF+VmyHxhGLS1I21ARaIY+Ktax2A4aoVwOipVqOtdO6gyOoa+jC+OEh08EPM kaJuBni7uW3/oycsdQxrMszEv5NnB0zl56k3QSwBjjms2nSZQp7oSe5WbXMKaP6oQoIm2s2FHGf GssENqeLGirS3AXaqQm6tsK1Fak41JpRV0D3K6rRyCPDeDJvws0cocvSNYE2eP/jxoqtWTDswXf crTf/qzhbLgFpKMgj1iKobfItLqLxyS/XIBTZUXIYHW4XYG8hkcebcsttCYl43SUafktNZP8LsC vsR/YvMmWYRZz/X3pJAO32IOIzus3WY7vTWS5BhQ9Xx2c9rc7LHS+ZM87j7lrmMCiWuMdTw== X-Google-Smtp-Source: AGHT+IF3E3JfBSXzHlF3LihaNYsEkX+TNmAHZUD4VaSyI1MQOcXAn99WTVBWot4owhbrly6A5VkjvQ== X-Received: by 2002:a5d:5f53:0:b0:3a4:dfc2:bb60 with SMTP id ffacd0b85a97d-3b776603426mr5020635f8f.26.1753561705590; Sat, 26 Jul 2025 13:28:25 -0700 (PDT) Received: from [192.168.1.106] (33bf2319.skybroadband.com. [51.191.35.25]) by smtp.googlemail.com with ESMTPSA id ffacd0b85a97d-3b78404f5b0sm244180f8f.41.2025.07.26.13.28.25 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 26 Jul 2025 13:28:25 -0700 (PDT) Message-ID: <295044f4-5fcc-4704-ab61-3f2f7349791e@gmail.com> Date: Sat, 26 Jul 2025 21:28:24 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: ffmpeg-devel@ffmpeg.org References: <20250722035337.2216565-1-dev@lynne.ee> <577d17cb-a056-49c0-bf71-870e00684b37@gmail.com> <8ec2eab1-1a2e-4607-9186-3d55c9335e3a@rothenpieler.org> From: Derek Buitenhuis In-Reply-To: <8ec2eab1-1a2e-4607-9186-3d55c9335e3a@rothenpieler.org> 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 7/26/2025 9:14 PM, Timo Rothenpieler wrote: > 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? I'd say this announcement should be amended to reflect this then, because it does not read at all like testing, but the new sole way to contribute. (I did indeed miss the single sentence that missed testing at the beginning there, for the steps like "* announce code.ffmpeg.org publically so people can start submittin and reviewing on it as an alternative to the ML".) >>> 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. I remember a period where patches that got sent to the ML got told to use the new method, but not a period where it was treated simultaniously as an equal and continuing method to contribute. Very possible I am misremembering, but that's that I recall. > vlc-devel is still active to this day, even with the very occasional > stray patch still landing there, just not for patches. Unrelated, really. Nobody proposed killing this list for discussion purposes. > 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. As above, suggest rewording the ffmpeg.org change then to better reflect this. > How do you intend to get everybody into one boat to move over all at once? Update the contrib docs, and start replying to ML patches (either automated or not) with instructions on using Forgejo. After a short period, you disable the old method and/or repo, and only allow the new one (not an extended period). During the period above, do not treat ML contributions as business as usual. > VLC has a central governing body who is able to make such decisions and > force the issue if need be. Does the GA not cover this? I did notice the vote was very specifically not put to GA vote, meaning there can be further endless arguing and refusal to move. > 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. GA. Vote on it, implement it. That's the end of it. Either that, or ditch the GA, as it is literally pointless, and acknowledhe FFmpeg is Michael's project. - 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".