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 via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: ga@ffmpeg.org, Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] [POLL][VOTE] Preferred Issue Tracker
Date: Mon, 20 Oct 2025 18:14:47 +0200
Message-ID: <aPZf9wYZsFn7x23c@neo> (raw)


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

Hi everyone

We currently have 2 issue trackers (trac and forgejo),

Previous discussion:
"[RFC] Issue tracker" and "trac ticket statistics"
https://lists.ffmpeg.org/archives/list/ffmpeg-devel@ffmpeg.org/thread/HS46O6K62MHRHJDJC45XLRMR64RE5IB7/#LMXCTJDF5SIUSX43X7YZ4347U5YHWW33

I think there are 2 questions, the first is,
which issue tracker do we want to use going forward?
And the 2nd question is, about migrating tickets.

First lets establish which tracker we want to use going forward.
It seems there where 2 options suggested.

"T", Trac, with a potential future switch to redmine (similar to trac)

"F", Forgejo

The difference is easy to spell out,

Trac has many more features (more powerfull search, votes on tickets, a range of anti spam features, ...)
trac seems not very actively maintained, redmine seems actively maintained

Forgejo avoids maintaining a seperate issue tracker but its fairly basic, also if we ever switch to
a different forge having issues in forgejo is a factor to consider.

About performance/speed, If someone has data on similar hw and similar
 # tickets and # users, this would be interresting, I was unable to
find such comparission.

after this Vote, i intend to start one about "migrating tickets."

All GA members can vote, by replying to this mail on ffmpeg-devel,
duration is 7 days
I will try to vote last, so i can break a tie if we have one.

If you dont vote, then dont complain about the outcome,
If you want something else than what was suggeted in the RFC, you can of course
suggest that too during the vote

thx
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who are best at talking, realize last or never when they are wrong.

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

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

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

             reply	other threads:[~2025-10-20 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 16:14 Michael Niedermayer via ffmpeg-devel [this message]
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
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=aPZf9wYZsFn7x23c@neo \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=ga@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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