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 295AF4BEE7 for ; Sat, 26 Jul 2025 20:23:13 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 666B768BB78; Sat, 26 Jul 2025 23:23:09 +0300 (EEST) Received: from btbn.de (btbn.de [144.76.60.213]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 34F0968CFF6 for ; Sat, 26 Jul 2025 23:23:02 +0300 (EEST) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id 6F5BC2819FB90 for ; Sat, 26 Jul 2025 22:23:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1753561381; 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=ioOPUY8iMxcuNBVX1IPBfJyuW90cnHaYCKKtSC98ZVU=; b=hIwd5Bg19DLCySH1PEgdOmzAbaQL800VA4LuzUgR4LDaDjJKTyW9PiWBkOuw+Quu3KXI34 XcOFZblUWD+Yl4RvtkDignKHfxP3iCj4wegj790oRtpuZbUInwv6sV88BSyseDpkLgEiFn /tXerjFN//LpT+4RXpD5oHE+MuHrwPVs8UZkE3unFlSar1yr45/u6gfBt57nOCOq1U9J/C JKrQOO1lkwKkfu2WdV2yB4wMqC556KFDdFgE/7soF5VeOwPAILP3MjN4mCziRpcLhnfcoQ pYCO0BUbBnMeAbqiEVNQWgF9LSrHoQY9LfADdqZvHeNg5/YAU5RDhR29lqgDvg== Message-ID: <8818ec57-ac91-4a42-9be5-79c07c12b265@rothenpieler.org> Date: Sat, 26 Jul 2025 22:23:02 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: <20250722035337.2216565-1-dev@lynne.ee> Content-Language: en-US From: Timo Rothenpieler In-Reply-To: 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: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. _______________________________________________ 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".