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: [RFC] Issue tracker
Date: Sun, 28 Sep 2025 10:54:14 +0300
Message-ID: <4679850.LvFx2qVVIh@basile.remlab.net> (raw)
In-Reply-To: <20250914212317.GG29660@pb2>

Le maanantaina 15. syyskuuta 2025, 0.23.17 Itä-Euroopan kesäaika Michael 
Niedermayer via ffmpeg-devel a écrit :
> Hi everyone
> 
> trac supports, custom search queries, customly formated results
> 
> People can vote on tickets,

I don't see much value in voting on tickets. It would be useful to know how 
many people are able and not able to reproduce a problem, but that's not how 
votes are used.

With that said, you can assign thumbs-up, thumbs-down and other emojis in 
Forgejo, if you want to vote on something.

> we can have custom ticket states and custom
> workflow on tickets.

We can have custom labels for tickets and MRs.

However before FFmpeg can consider migrating from Trac to Forgejo, we have to 
consider the (anti)spam implications. I suppose there is not much spam yet 
because Gitlab is vastly more popular, but that's probably only a matter of 
time.

If code.ffmpeg.org needs to be locked down with manual approval like 
FreeDesktop and VideoLAN's Gitlab instances, then migrating the bug reporting 
there may not be such a great idea. Unless we specifically want to restrict bug 
reporting to trusted community members.

Otherwise, I don't really see any benefit to Trac. Forgejo would allow us to 
link issues and MRs, and presumably also automatically close issues. We just 
need to agree whether to migrate existing issues or not (and if we do, find 
someone to do the SQL wizardry).

-- 
德尼-库尔蒙‧雷米
Tapio's place new town, former Finnish Republic of Uusimaa



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

  parent reply	other threads:[~2025-09-28  7:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14 21:23 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-15 11:09 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-15 11:37   ` Michael Niedermayer via ffmpeg-devel
2025-09-15 12:06   ` Timo Rothenpieler via ffmpeg-devel
2025-09-15 12:30     ` Michael Niedermayer via ffmpeg-devel
2025-09-15 12:47       ` Timo Rothenpieler via ffmpeg-devel
2025-09-15 12:57     ` Michael Niedermayer via ffmpeg-devel
2025-09-15 13:05       ` Michael Niedermayer via ffmpeg-devel
2025-09-15 17:19       ` Timo Rothenpieler via ffmpeg-devel
2025-09-15 18:26         ` Michael Niedermayer via ffmpeg-devel
2025-09-15 18:35           ` Timo Rothenpieler via ffmpeg-devel
2025-09-15 19:09             ` Gyan Doshi via ffmpeg-devel
2025-09-15 21:46               ` Michael Niedermayer via ffmpeg-devel
2025-09-16  4:39                 ` Gyan Doshi via ffmpeg-devel
2025-09-23 21:50                   ` [FFmpeg-devel] trac ticket statistics Was: " Michael Niedermayer via ffmpeg-devel
2025-09-24 10:56                     ` [FFmpeg-devel] " Gyan Doshi via ffmpeg-devel
2025-09-28  0:44                       ` Michael Niedermayer via ffmpeg-devel
2025-09-28  6:13                         ` Gyan Doshi via ffmpeg-devel
2025-09-23 22:33                   ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-15 22:36             ` Michael Niedermayer via ffmpeg-devel
2025-09-28  7:54 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-09-28  8:51   ` Michael Niedermayer via ffmpeg-devel
2025-09-28 11:32     ` Rémi Denis-Courmont via ffmpeg-devel
2025-09-28  9:18   ` Michael Niedermayer via ffmpeg-devel
2025-09-28  9:59     ` Jacob Lifshay 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=4679850.LvFx2qVVIh@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 http://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/ http://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