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 4BD6D4BF0A for ; Sat, 26 Jul 2025 20:30:35 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 0929B68D38D; Sat, 26 Jul 2025 23:30:31 +0300 (EEST) Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 5202B68CF41 for ; Sat, 26 Jul 2025 23:30:24 +0300 (EEST) Received: by mail-ed1-f53.google.com with SMTP id 4fb4d7f45d1cf-60702d77c60so5813309a12.3 for ; Sat, 26 Jul 2025 13:30:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1753561823; x=1754166623; darn=ffmpeg.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=AbPQE0wGg7QlOYmffsTltLSJDLTRzA/hSsAgE0nzLsA=; b=euhyZ3pfOCEGPHPGkZ4jLGH8VwgBsnwfXfYdC+uNx5JdWW1UrCWDTM0sMeBRAcUk6f x3kTOeD7pEJUCUTFR6ckTGVVpb3KFc1SPws0OpzpnFsX5djwIhVmwXxk5dThYSuw2HwG 0h1ePjqfvjYVhXKFQxfTXbSfB9ypvzDe8ff8OY2Sy6MWjCQNdsi3mhfsnpP/vXWpQQbu WVdEJ0H9piEPyWQiBZdMwWBTVjD4eMso2b0EkgSEHQPKGMy+4CG7xLd/fZO3i9wpVp6g 3MVxvOzK1K8XD4/dc0WVe4Ym4100MpAFkrSYaGIS00NxmogDDsp4K+n7i3dY8fsfkE8F Knzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753561823; x=1754166623; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=AbPQE0wGg7QlOYmffsTltLSJDLTRzA/hSsAgE0nzLsA=; b=OZgMHlKL4YDXMyZPhoAyhWa4g46bMJErI8MCnuvv49Sjn3P39vHMyFOW3fIoDtmogD ptmexgIGJD5aKSu3WD1jjaScgcdk1s9DI9jPqHzjpU9U3vvsCeacfqGHGhKNBtF2j5Qz OHi050DoCQlRbI7CeF9Qmyq9sKTYeP9kN1/ZGshZwtulTyuaeUPVjP1isgq1sNIk1BcF KlrjAb8SA03fijS487FMjWz7atWRKFXye1LSQ8DVg24zlbrBbKzjmVqSHqTWbVrBQloD FHrIkScgSc1Gu3Vi7To8HZhiIgGU1FK/unGF0a00Vt77wFyKmOvBzhujpwgmrbbfUKj6 be+A== X-Gm-Message-State: AOJu0Yy7sqOk/izgAs3NEmaDHxH0oNdh76FJmL+nB39QSXA106O0/IIY qECO7oTw0sB46izt4EaWgS6Jk9LqNIqVl4BtEXRoV6bcHPHxm5eI7EbcerUErRNt554mtSvEqb+ c0f9mHktmqzGKkU7wg9rABOoF9Q/M/O1RJA== X-Gm-Gg: ASbGncuZUpKTzw8DBkpxS4KGhT1hhy6BmP70L8GN1zpM7P2OUs06AScL++n6i8tN1+Q h5D8ks/XzQxtZ8+vD2LJLlxhvP+01HkqMR4ORG6XiIMuj045cjJJ3vIeNHKw8elommFZl/M9woO bas6VxQ53Gn1vi8xSSD06zW5xZHpkjdwA2qixPysR8rVfwf11e4hBb/aMCHWAD4tAhvCWP/x+hT pE4 X-Google-Smtp-Source: AGHT+IH+nfx67EDVWI2dhvvLVvRyqsfXAVuhXD2+tHaIVVQsJk1BgDnpKLQxGfYMAVrvl60maivnMd+ARLhmQC3Yoqw= X-Received: by 2002:aa7:d353:0:b0:606:bea1:1740 with SMTP id 4fb4d7f45d1cf-614f1dbdb07mr4626285a12.30.1753561822706; Sat, 26 Jul 2025 13:30:22 -0700 (PDT) MIME-Version: 1.0 References: <20250722035337.2216565-1-dev@lynne.ee> <8818ec57-ac91-4a42-9be5-79c07c12b265@rothenpieler.org> In-Reply-To: <8818ec57-ac91-4a42-9be5-79c07c12b265@rothenpieler.org> From: Kacper Michajlow Date: Sat, 26 Jul 2025 22:29:49 +0200 X-Gm-Features: Ac12FXxkAPaes4svuSPXTyU4ZmaDd4rNr9eho94ka1oJDeMNOTOYvxXI8AbqHJo Message-ID: To: FFmpeg development discussions and patches 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 Sat, 26 Jul 2025 at 22:23, Timo Rothenpieler wrote: > > On 7/26/2025 10:14 PM, Kacper Michajlow wrote: > > n Sat, 26 Jul 2025 at 21:29, Timo Rothenpieler wrote: > >> > >> On 7/26/2025 7:03 PM, Derek Buitenhuis wrote: > >>> On 7/22/2025 4:53 AM, Lynne wrote: > >>>> --- > >>>> src/contact | 11 +++++++++++ > >>>> src/index | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++ > >>>> 2 files changed, 63 insertions(+) > >>> > >>> So I am a bit unclear, is development now Forgejo or ML, or both? > >>> > >>> Because right now, it seems like both, and that is basically the worst > >>> possible outcome. It is very difficult to follow both, and the amount > >>> of people reviewing or even looking at patches on either is now significantly > >>> splintered/reduced, allowing lower quality code to wade itself in the meantime, > >>> IMO. > >>> > >>> Also, as far as I can tell, the git access list was not really carried over in > >>> any way. > >>> > >>> It all seems a bit chaotic and directionless... or rather, with 0 plan. > >> > >> It's still an extended test. You cannot push to it, since it's just a > >> mirror. > >> > >> How do you expect to suddenly switch every last person over from the ML > >> to a new tool? > >> There's always going to be a transition period where both are in use, > >> gradually shifting. > >> So yes, for now there needs to be eyes on both. > >> > >> Hopefully pushing to it/hitting the merge button should be possible soon > >> (hinges on cooperation with Videolan) > > > > I agree with Derek on this topic, I think it is unreasonable to have > > two ways to merge patches into the main repository. > > > > Once the "merge button" is operational, all direct push to the > > repository should be restricted and always required to go through PR. > > > > There may still be communication/review overlap between ML/forgejo, > > but ultimately it should go through one path of merge/approve. > > I agree, but unfortunately don't feel like it's a realistic expectation. > Forcing everyone into a new workflow all at once is not going to go well > with everybody. I agree. But like mentioned in the previous message, I don't think giving more time changes this in practice. It will likely just move the "pain point" to a different date. Because at some point there will be "the date". Of course this hinges on the fact we will actually use forgejo, it would be unreasonable to force people to move and then say we are going back to ML or something. A test period is required, so the decision can be made. - Kacper _______________________________________________ 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".