Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Date: Wed, 23 Jul 2025 01:04:34 +0200
Message-ID: <20250722230434.GG29660@pb2> (raw)
In-Reply-To: <20250722035337.2216565-1-dev@lynne.ee>


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

  parent reply	other threads:[~2025-07-22 23:04 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22  3:53 Lynne
2025-07-22  8:44 ` Kacper Michajlow
2025-07-22  9:15   ` Jacob Lifshay
2025-07-25  3:40     ` compn
2025-07-25  3:58       ` Jacob Lifshay
2025-07-25  4:36         ` compn
2025-07-25 11:41         ` Nicolas George
2025-07-25 14:20           ` Kieran Kunhya via ffmpeg-devel
2025-07-31 19:38           ` Rémi Denis-Courmont
2025-07-31 21:16             ` Nicolas George
2025-07-23  4:05   ` Lynne
2025-07-22 15:01 ` Leo Izen
2025-07-23  4:01   ` Lynne
2025-07-22 23:04 ` Michael Niedermayer [this message]
2025-07-23  4:01   ` Lynne
2025-07-23  9:16     ` Michael Niedermayer
2025-07-23  9:39       ` Kieran Kunhya via ffmpeg-devel
2025-07-23  9:59         ` Michael Niedermayer
2025-07-23 10:02           ` Kieran Kunhya via ffmpeg-devel
2025-07-23 11:48           ` Nicolas George
2025-07-25  4:05           ` compn
2025-07-26 14:57             ` Michael Niedermayer
2025-07-23  9:38     ` Michael Niedermayer
2025-07-23 11:49       ` Nicolas George
2025-07-27 12:07   ` Niklas Haas
2025-07-27 12:41     ` Nicolas George
2025-07-27 20:47     ` Michael Niedermayer
2025-07-27 21:06       ` Diederick C. Niehorster
2025-07-26 17:03 ` Derek Buitenhuis
2025-07-26 19:29   ` Timo Rothenpieler
2025-07-26 20:01     ` Derek Buitenhuis
2025-07-26 20:14       ` Timo Rothenpieler
2025-07-26 20:24         ` Kacper Michajlow
2025-07-26 20:29           ` Derek Buitenhuis
2025-07-26 20:41           ` Timo Rothenpieler
2025-07-26 20:45             ` Derek Buitenhuis
2025-07-26 21:07             ` Kacper Michajlow
2025-07-26 21:18               ` Timo Rothenpieler
2025-07-26 22:44             ` Michael Niedermayer
2025-07-26 22:57               ` Timo Rothenpieler
2025-07-26 22:48             ` Michael Niedermayer
2025-07-27  9:40             ` Nicolas George
2025-07-27  9:39           ` Nicolas George
2025-07-27 16:48             ` Kacper Michajlow
2025-07-30 21:55               ` Nicolas George
2025-07-26 20:28         ` Derek Buitenhuis
2025-08-01  8:49         ` Rémi Denis-Courmont
2025-07-26 20:14     ` Kacper Michajlow
2025-07-26 20:23       ` Timo Rothenpieler
2025-07-26 20:29         ` Kacper Michajlow
2025-07-26 20:33           ` Derek Buitenhuis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250722230434.GG29660@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git