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 C0BA24BADA for ; Wed, 23 Jul 2025 04:05:53 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 41BC368D3F9; Wed, 23 Jul 2025 07:05:49 +0300 (EEST) Received: from vidala.pars.ee (vidala.pars.ee [116.203.72.101]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 418C7687C7C for ; Wed, 23 Jul 2025 07:05:43 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; s=202405r; d=lynne.ee; c=relaxed/relaxed; h=From:To:Subject:Date:Message-ID; t=1753243542; bh=zvtIiVCApCZoA/9cAjzZ3p3 eA9wAWoYkL058VDGD4/s=; b=HbB5mdrnSxRAW0LMqZsXUI+SuurC2FvNuwjbekAI27LVlKhQmK yt+Qmlb761hC4gc2U8CHufgAfUAwjt0FMtaTUn7Q2QkN1C74RHFRcs36e8MRNccT7xMm2m6xh8+ eQLvwaHT1g7D7XpSjFj5hOLKVKWdiws4P6gJpjEL8iu0hSER+wJ4NQQEKkn3lJyT0gB3gPTLBvM /w2IYqdi/RvBEjhYbCbxvNrn5PrXtqJNYVjHXTvCvNbLEsDr9y4NvJXX77VEHAZAvhd8U0XKYFT c72gsGjYexw/tywlNWb1huSb3bpQuVfoR8GX/HerJLx/PzJO3jIM8vluYHtx1ZW205w==; DKIM-Signature: v=1; a=ed25519-sha256; s=202405e; d=lynne.ee; c=relaxed/relaxed; h=From:To:Subject:Date:Message-ID; t=1753243542; bh=zvtIiVCApCZoA/9cAjzZ3p3 eA9wAWoYkL058VDGD4/s=; b=y/DN+Ds2lRJ4Ntey8uSi1kzmjoy4lERccYojC8FfTCEWihiYs0 5KmssfanhG56uv/nb/hn/kafrF4icruXWWDg==; Message-ID: <0d76ac66-2d99-4d6f-9861-6005c30c30cd@lynne.ee> Date: Wed, 23 Jul 2025 13:05:40 +0900 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: Lynne 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 22/07/2025 17:44, Kacper Michajlow wrote: > On Tue, 22 Jul 2025 at 05:54, Lynne wrote: >> >> --- >> src/contact | 11 +++++++++++ >> src/index | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++ >> 2 files changed, 63 insertions(+) >> >> diff --git a/src/contact b/src/contact >> index 6943d06..8a59864 100644 >> --- a/src/contact >> +++ b/src/contact >> @@ -1,3 +1,14 @@ >> +
>> +

>> + >> + Contributions

>> +
>> +

>> + To contribute to FFmpeg, login or sign up for an account on code.ffmpeg.org. >> + The main repository of the project is code.ffmpeg.org/FFmpeg/FFmpeg. >> +

>> +
>> +
> > doc\git-howto.texi and doc\developer.texi needs to also be updated > >>
>>
>> diff --git a/src/index b/src/index >> index 52829e1..1f45dec 100644 >> --- a/src/index >> +++ b/src/index >> @@ -35,6 +35,58 @@ >> News >> >> >> +

July 22nd, 2025, Modernization of contributions

>> +

>> + The project is modernizing its contribution methods and switching to a software forge. > > Mention which one specifically. > >> +

>> +

>> + We have setup a platform on code.ffmpeg.org. The new process > > `set up` > >> + features continuous integration on all commits and merge requests, labelling for categorization, > > Forgejo calls them "Pull Requests", it's not gitlab. > >> + conflict resolution, and logging in via OpenID or Github. > > What do you mean by `conflict resolution`? I don't think there is any > editing in the browser. > > Also could mention `issue tracking`, if that's going to be used. I mean that it would let you know if your PR has conflicts with current master. > >> +

>> +

>> + The main repository will become code.ffmpeg.org/FFmpeg/FFmpeg, >> + with all others being mirrored to it. >> + Users are encouraged to begin using it, effective now. >> +

>> +

>> + Mailing lists have supported our development for >> + nearly 25 years, >> + but as more and more contributors started to become involved, the ratio of merged patches to total mails begun >> + falling. Mailing lists became a source of friction, >> + with discussions frequently stalling and uncategorized noise drowning out patches by bumping them down in inboxes. > > Could just mention in a more neutral way that modern code forges are > better in keeping track of patches, new revisions, review and > comments. I think we first need to mention what issues we faced with MLs. > >> +

>> +

>> + Although patchwork.ffmpeg.org was set up to track submissions, > > What is `patch.ffmpeg.org`? patchwork.ffmpeg.org, fixed locally > >> + it was less than reliable, with many patches and mails slipping though. Since its activation exactly >> + 9 years ago, it recorded 54,476 patches, with 53,650 patches having the state of not archived. >> + In comparison, the mailing list has had a total of 150,736 emails during the same time period. > > Can mention that patchwork doesn't really help tracking active patches > and revisions, just makes some of the comments categorized. But also > we don't need to "shit on" other software. We can in more netural way > that new forget will be an improvement to patch tracking over existing > patchwork, and that's all. Its just far from perfect and the stats illustrate that. I don't think there's a way to skip implying patchwork doesn't work great. _______________________________________________ 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".