Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [POLL][VOTE] Preferred Issue Tracker
Date: Thu, 23 Oct 2025 20:41:32 +0300
Message-ID: <3318288.PWutnLV925@basile.remlab.net> (raw)
In-Reply-To: <aPoIUt6owFdfWja-@neo>

Le torstaina 23. lokakuuta 2025, 13.49.54 Itä-Euroopan kesäaika Michael 
Niedermayer via ffmpeg-devel a écrit :
> I ve missed a crucial detail, which only became obvious to me now.
> Seeing that people vote based on what they personally prefer,
> and 90% of the people seem not to care which bug tracker we use.

Isn't that what the majority of active developers prefer the best for the 
project, or the best possible approximation of it?
And if it's not, how are people supposed to evaluate it?

It seems to me that having main developers vote on what they prefer is 
actually the right way about it, or at least the "least bad".

Speaking as a CC member, I find the use of public balot questionable, but I 
don't see a problem with people voting to their preference. (And I don't plan 
to vote, since my involvement with FFMpeg bug triaging is negligible.)

-- 
ヅニ-クーモン・レミ
Tapiolan uusi kaupunki, Uudenmaan entinen Suomen tasavalta



_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-10-23 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 16:14 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-20 16:41 ` [FFmpeg-devel] " Timo Rothenpieler via ffmpeg-devel
2025-10-20 23:30   ` Michael Niedermayer via ffmpeg-devel
2025-10-21  2:28 ` Lynne via ffmpeg-devel
2025-10-21 11:03   ` Michael Niedermayer via ffmpeg-devel
2025-10-21 11:48     ` Michael Niedermayer via ffmpeg-devel
2025-10-23 10:49 ` Michael Niedermayer via ffmpeg-devel
2025-10-23 17:41   ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-10-23 22:01     ` Michael Niedermayer via ffmpeg-devel

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=3318288.PWutnLV925@basile.remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=remi@remlab.net \
    /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