Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Timo Rothenpieler <timo@rothenpieler.org>
Subject: [FFmpeg-devel] Re: [POLL][VOTE] Preferred Issue Tracker
Date: Mon, 20 Oct 2025 18:41:17 +0200
Message-ID: <dca3cdbc-d9fc-4464-9f8d-582af5eddbc8@rothenpieler.org> (raw)
In-Reply-To: <aPZf9wYZsFn7x23c@neo>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 1832 bytes --]

On 20.10.2025 18:14, Michael Niedermayer via ffmpeg-devel wrote:
> 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


F for Forgejo, simply because maintaining two applications, specially 
one as old and "brittle" as trac is a pain.

trac currently needs subtantially more server resources than Forgejo, 
while having roughly similar amounts of requests.
It also frequently goes down if the traffic goes too hard, and needs a 
reboot to come back.

I also personally feel like we don't really need/use any of the more 
advanced features in trac. At least I have never looked at votes before, 
or heard anyone talk about them before Forgejo came up.
The only clear advantage it has is the much more refined search, but 
that's something other people have noticed to be lacking in Forgejo as 
well, so there is ongoing effort to improve it.


Also, redmine is not something one can just switch to.
It looks similar, but is an entirely seaprate thing.
There is also no clear way to migrate to it, so it'd be another 
disruptive switch.
There is https://www.redmine.org/projects/redmine/wiki/redminemigrate
but it explicitly says the migration from Trac is obsolete and does not 
work.

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3203 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 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: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 ` Timo Rothenpieler via ffmpeg-devel [this message]
2025-10-20 23:30   ` [FFmpeg-devel] " 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=dca3cdbc-d9fc-4464-9f8d-582af5eddbc8@rothenpieler.org \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=timo@rothenpieler.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