Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org

[Kacper Michajlow <kasper93@gmail.com>]

On Tue, 22 Jul 2025 at 05:54, Lynne <dev@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.

> +  </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.

> +  </p>
> +  <p>
> +    Although <a href="https://patch.ffmpeg.org/">patchwork.ffmpeg.org</a> was set up to track submissions,

What is `patch.ffmpeg.org`?

> +    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.

> +  </p>
> +  <p>
> +    Additionally, new users have frequently encountered difficulties with mailing list development.
> +    From finding out the correct SMTP login details, configuring git send-email, new email security
> +    mechanisms interfering with mailing list operations, and finally not having a comfortable workflow
> +    to review patches.

Just a 2 cents from me, I don't think sending email itself is a
problem, but at the same time sending them feels like throwing a coin
into a big pond. Unless someone picks it up in "a few days", it's
likely lost, because there is no way to go back to previous changes,
label them. For both small and big changes, the submitter needs to
actively bump them to keep it on the table. With proper storing and
categorization this wouldn't be an issue.

> +  </p>
> +  <p>
> +    After years of discussions, and a vote, we officially announce the new platform,
> +    <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>, running <a href="https://forgejo.org/">Forgejo</a>.
> +    Documentation will be updated to reflect the change.
> +  </p>
> +  <p>
> +    Mailing lists will continue to be monitored, and used for project discussions and other topics
> +    better discussed elsewhere, but traffic and noise should become significantly reduced over time.

Incidentally, I never thought that FFmpeg ML had much noise. It's just
an inherent issue with one big bucket for everything, any discussion
is shadowing anything else that is happening on ML.

> +  </p>
> +  <p>
> +    Bugs/issues will be accepted on <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>, alongside
> +    with <a href="https://trac.ffmpeg.org/">trac.ffmpeg.org</a> for the time being.
> +  </p>
> +  <p>
> +    We are also hoping that this will significantly reduce the amount of unmerged patches.
> +    If you submitted a patch which received no replies or conclusion, we apologize, and you are encouraged
> +    to resubmit it on the new platform.
> +  </p>
> +
>    <h3 id="pr7.1">September 30th, 2024, FFmpeg 7.1 <span title="Rózsa Péter">"Péter"</span></h3>
>    <p>
>      <a href="download.html#release_7.1">FFmpeg 7.1 "Péter"</a>, a new
> --
> 2.50.0
> _______________________________________________
> 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".

- 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".