[FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Lynne
dev at lynne.ee
Wed Jul 23 07:05:40 EEST 2025
On 22/07/2025 17:44, Kacper Michajlow wrote:
> On Tue, 22 Jul 2025 at 05:54, Lynne <dev at lynne.ee> 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 @@
>> +<div class="well">
>> + <h3 id="Contributions">
>> + <i class="fa fa-pencil"></i>
>> + Contributions</h3>
>> + <div style="color: white">
>> + <p>
>> + To contribute to FFmpeg, login or sign up for an account on <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>.
>> + The main repository of the project is <a href="https://code.ffmpeg.org/FFmpeg/FFmpeg">code.ffmpeg.org/FFmpeg/FFmpeg</a>.
>> + </p>
>> + </div>
>> +</div> <!-- well -->
>
> doc\git-howto.texi and doc\developer.texi needs to also be updated
>
>> <div class="well">
>> <div class="row">
>> diff --git a/src/index b/src/index
>> index 52829e1..1f45dec 100644
>> --- a/src/index
>> +++ b/src/index
>> @@ -35,6 +35,58 @@
>> News
>> </h1>
>>
>> + <h3 id="forge">July 22nd, 2025, Modernization of contributions</h3>
>> + <p>
>> + The project is modernizing its contribution methods and switching to a software forge.
>
> Mention which one specifically.
>
>> + <p>
>> + </p>
>> + We have setup a platform on <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>. 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.
>
>> + </p>
>> + <p>
>> + The main repository will become <a href="https://code.ffmpeg.org/FFmpeg/FFmpeg">code.ffmpeg.org/FFmpeg/FFmpeg</a>,
>> + with all others being mirrored to it.
>> + Users are encouraged to begin using it, effective now.
>> + </p>
>> + <p>
>> + Mailing lists have supported our development for
>> + <span title="with a total of 346,615 emails since April 2005">nearly 25 years</span>,
>> + but as more and more contributors started to become involved, the ratio of merged patches to total mails begun
>> + <span title="perhaps just correlation">falling</span>. 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.
>
>> + </p>
>> + <p>
>> + Although <a href="https://patch.ffmpeg.org/">patchwork.ffmpeg.org</a> 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.
More information about the ffmpeg-devel
mailing list