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-requ...@ffmpeg.org with subject "unsubscribe".
