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

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

[Lynne]

---
 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 -->
 
 <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.
+  <p>
+  </p>
+    We have setup a platform on <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>. The new process
+    features continuous integration on all commits and merge requests, labelling for categorization,
+    conflict resolution, and logging in via OpenID or Github.
+  </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.
+  </p>
+  <p>
+    Although <a href="https://patch.ffmpeg.org/">patchwork.ffmpeg.org</a> was set up to track submissions,
+    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.
+  </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.
+  </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.
+  </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".

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

[Kacper Michajlow]

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

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

[Jacob Lifshay]

On Tue, Jul 22, 2025 at 1:44 AM Kacper Michajlow <kasper93@gmail.com> wrote:
> On Tue, 22 Jul 2025 at 05:54, Lynne <dev@lynne.ee> wrote:
> > +    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,

If you don't need to send patches, email isn't really a problem.

however, imo figuring out how to get git send-email to work is a
significant problem (it took me like 20-30min to set up since I was
also figuring how to securely store the gmail app password in gnome
keyring using a git credential helper), I have contributed to quite a
few FOSS projects over the last 10yr or so and FFmpeg is the only(?)
one that requires using git send-email. the vast majority of them are
using a git forge or you just point them to your git forge of choice
and they'll pull from there.

tbh the only reason I'm contributing now using git send-email is
because I'm being paid to, if I weren't being paid I'm much less
likely to have bothered even when I had the code in a git repo.

Jacob Lifshay
_______________________________________________
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".

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

[Lynne]

On 22/07/2025 17:44, Kacper Michajlow wrote:
> 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.

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

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

[Leo Izen]

On 7/21/25 23:53, Lynne wrote:
> ---
>   src/contact | 11 +++++++++++
>   src/index   | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>   2 files changed, 63 insertions(+)
> 

In addition to what kasper said, you should also update README.md's 
contributing section at the bottom of the file.

May be wise to do that in a separate patch, don't know.

- Leo Izen (Traneptora)

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

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

[Lynne]

On 23/07/2025 00:01, Leo Izen wrote:
> On 7/21/25 23:53, Lynne wrote:
>> ---
>>   src/contact | 11 +++++++++++
>>   src/index   | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>   2 files changed, 63 insertions(+)
>>
> 
> In addition to what kasper said, you should also update README.md's 
> contributing section at the bottom of the file.
> 
> May be wise to do that in a separate patch, don't know.

Its in a separate repository, this is for ffmpeg-web.
_______________________________________________
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".

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

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 1906 bytes --]

Hi Lynne

On Tue, Jul 22, 2025 at 12:53:29PM +0900, Lynne wrote:

[...]

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

People should not submit bug reports randomly to 2 trackers, thats a problem.
It would make searching for issues 2x as hard.

If we discuss and decide to change the bug tracker (which we have not discussed,
less decided) -> than we should import all the issues from trac into the new tracker first.

In fact i suggest we make the forgejo issue tracker forward people to trac currently


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

The announcment should probably mention that performance, as in number of
submissions / percentage of applied / not reviewed patches will be
monitored compared to the mailing list.

(and obviously someone has to do that, i do think such basic performance
 monitoring is important after/ during such a change)

later then (in a month or whatever) we should make an announcment with
the performance numbers

[And if we want to have strong statistics, then it is neccessary
 to pre-announce _exactly_ when and what will be meassured how.
 https://en.wikipedia.org/wiki/Preregistration_(science) ]

just thought this would be a interresting subject for a statistics paper,
if someone (maybe outside the ffmpeg team) wants to do it ...

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I am the wisest man alive, for I know one thing, and that is that I know
nothing. -- Socrates

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

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

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

[Lynne]

On 23/07/2025 08:04, Michael Niedermayer wrote:
> Hi Lynne
> 
> On Tue, Jul 22, 2025 at 12:53:29PM +0900, Lynne wrote:
> 
> [...]
> 
>> +  <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>
> 
> People should not submit bug reports randomly to 2 trackers, thats a problem.
> It would make searching for issues 2x as hard.
> 
> If we discuss and decide to change the bug tracker (which we have not discussed,
> less decided) -> than we should import all the issues from trac into the new tracker first.
> 
> In fact i suggest we make the forgejo issue tracker forward people to trac currently

I disagree, I think we need a fresh start to track bugs properly. BtbN 
suggested he could redirect the new issue button on trac to Forgejo.

>> +  <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>
> 
> The announcment should probably mention that performance, as in number of
> submissions / percentage of applied / not reviewed patches will be
> monitored compared to the mailing list.
> 
> (and obviously someone has to do that, i do think such basic performance
>   monitoring is important after/ during such a change)
> 
> later then (in a month or whatever) we should make an announcment with
> the performance numbers

We all know there were plenty of patches left over. What we need to do 
is to start earning back the trust of casual submitters by at least 
letting them know that patches which might have gotten lost will get a 
second chance.
I already included data which hints at how many patches were left out in 
the form of ML vs patchwork stats.
> [And if we want to have strong statistics, then it is neccessary
>   to pre-announce _exactly_ when and what will be meassured how.
>   https://en.wikipedia.org/wiki/Preregistration_(science) ]
> 
> just thought this would be a interresting subject for a statistics paper,
> if someone (maybe outside the ffmpeg team) wants to do it ...
We could announce it later once we open the gates and start gathering data.
_______________________________________________
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".

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

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 2045 bytes --]

Hi Lynne

On Wed, Jul 23, 2025 at 01:01:06PM +0900, Lynne wrote:
> 
> 
> On 23/07/2025 08:04, Michael Niedermayer wrote:
> > Hi Lynne
> > 
> > On Tue, Jul 22, 2025 at 12:53:29PM +0900, Lynne wrote:
> > 
> > [...]
> > 
> > > +  <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>
> > 
> > People should not submit bug reports randomly to 2 trackers, thats a problem.
> > It would make searching for issues 2x as hard.
> > 
> > If we discuss and decide to change the bug tracker (which we have not discussed,
> > less decided) -> than we should import all the issues from trac into the new tracker first.
> > 
> > In fact i suggest we make the forgejo issue tracker forward people to trac currently
> 
> I disagree,

You can disagree, but you cannot "in the name of the community" suggest
things that have never been discussed by the community


> I think we need a fresh start to track bugs properly.

IMHO:

1. We need to understand the problem,
2. then think about how to solve it (and choose a solution)
3. then implement the solution
4. then evaluate the implementation/solution

About 1. (IMHO)
* The problem is that carl has become inactive and stoped doing user
  support and maintain the 10000+ bugs on the tracker.

About 2. (IMHO)
* The solution is to hire carl or someone else (or find a volunteer)
  to do this work. Changing the tracker will not fix this.

  FFlabs should have  enough captial to hire carl for this. People should ask
  FFlabs to hire him and carl to accept to be hired for this work.
  Or a "bugs maintaince and user support" should be on the STF 2025 page
  with conditions that someone agrees to, to do that work.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Opposition brings concord. Out of discord comes the fairest harmony.
-- Heraclitus

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

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

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

[Kieran Kunhya via ffmpeg-devel]

>
>
>
> About 2. (IMHO)
> * The solution is to hire carl or someone else (or find a volunteer)
>   to do this work. Changing the tracker will not fix this.
>
>   FFlabs should have  enough captial to hire carl for this. People should
> ask
>   FFlabs to hire him and carl to accept to be hired for this work.


The commercial decisions of FFlabs are for its shareholders during its
internal meetings, not this mailing list. Not is it relevant to suggest
people should petition a private company (of which I understand you are a
shareholder).

It doesn't take a business mastermind to understand why this plan is flawed.

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

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

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]

Hello Kieran

On Wed, Jul 23, 2025 at 10:39:01AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> >
> >
> >
> > About 2. (IMHO)
> > * The solution is to hire carl or someone else (or find a volunteer)
> >   to do this work. Changing the tracker will not fix this.
> >
> >   FFlabs should have  enough captial to hire carl for this. People should
> > ask
> >   FFlabs to hire him and carl to accept to be hired for this work.
> 
> 
> The commercial decisions of FFlabs are for its shareholders during its
> internal meetings, not this mailing list.

Thats a misunderstanding.

Let me quote the president and CEO:

"The company is just a way to finance the community to work on the same
 things as usual."

and

"To me, the company should be transparent to the project. It's just a way
 to funnel money to the community."


thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The educated differ from the uneducated as much as the living from the
dead. -- Aristotle 

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

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

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

[Kieran Kunhya via ffmpeg-devel]

On Wed, Jul 23, 2025 at 10:59 AM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hello Kieran
>
> On Wed, Jul 23, 2025 at 10:39:01AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> > >
> > >
> > >
> > > About 2. (IMHO)
> > > * The solution is to hire carl or someone else (or find a volunteer)
> > >   to do this work. Changing the tracker will not fix this.
> > >
> > >   FFlabs should have  enough captial to hire carl for this. People should
> > > ask
> > >   FFlabs to hire him and carl to accept to be hired for this work.
> >
> >
> > The commercial decisions of FFlabs are for its shareholders during its
> > internal meetings, not this mailing list.
>
> Thats a misunderstanding.
>
> Let me quote the president and CEO:
>
> "The company is just a way to finance the community to work on the same
>  things as usual."
>
> and
>
> "To me, the company should be transparent to the project. It's just a way
>  to funnel money to the community."

One is the vision of the CEO whereas in reality the legal requirements
(articles of association) matter.
Again a topic for your board meeting, not this ML.

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

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

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 2266 bytes --]

Hi Lynne

On Wed, Jul 23, 2025 at 01:01:06PM +0900, Lynne wrote:
> 
> 
> On 23/07/2025 08:04, Michael Niedermayer wrote:
> > Hi Lynne
> > 
> > On Tue, Jul 22, 2025 at 12:53:29PM +0900, Lynne wrote:
[...]
> > > +  <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>
> > 
> > The announcment should probably mention that performance, as in number of
> > submissions / percentage of applied / not reviewed patches will be
> > monitored compared to the mailing list.
> > 
> > (and obviously someone has to do that, i do think such basic performance
> >   monitoring is important after/ during such a change)
> > 
> > later then (in a month or whatever) we should make an announcment with
> > the performance numbers
> 
> We all know there were plenty of patches left over. What we need to do is to

yes, but the patches arent "forgotten". Everyone, including myself have them
in their ffmpeg-devel mailbox.

Iam not reviewing them not because iam unaware of them but because its just
way too many patches for one person, who than also has many other things to do
besides reviewing patches.

Once one understands this, the solution should be clear
1. we have to split up responsibilities, that is the maintainers system
   each area should have a maintainer who would not waste time with noise outside
   her area. And also not have to endlessly argue with people not maintaining the
   specific code.
2. hire more reviewers/maintainers, so we have more manpower, FFlabs and STF are
   options here, both these options should be used.
3. better tools to get the right patches to the right reviewer with less work,
   I hope forgejo will achieve this
4. We should try to shift work that others can do, away from key people,
   so they have more time for work that we have noone else who can do it.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

z(9) = an object that transcends all computable functions describable
in finite terms. - ChatGPT in 2024

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

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