[FFmpeg-devel] Re: [RFC] Issue tracker

[Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>]

On 15/09/2025 13:09, Michael Niedermayer via ffmpeg-devel wrote:
> Hi all
> 
> ATM the bug reporting guidlines point to trac
> and https://trac.ffmpeg.org/newticket redirects to forgejo
> 
> So if a user found a bug, now what does she do?
> 1. First she (maybe) looks at the bug reporting guidlines (which point to trac)
> 2. and she registers on trac
> 3. she maybe searches for existing tickets on trac, and maybe adds her info there
> 4. she tries to open a new ticket on trac and gets redirected to forgejo
> 5a. she refuses to register on a 2nd tracker and leaves
> 5b. she registers on forgejo
> 6. she searches for an existing report on forgejo and maybe adds her bug info there
> 7. she opens a new ticket on forgejo
> 
> lets summarize, what is wrong here
> 0. I think many people are/where unaware of the newticket redirect (I was unaware until very recently)
> 1. I think some of the consequences of this regirect where missed
> 2. the bug tracker was half switched to forgejo
> 3. users have to register on 2 trackers (they may need to add comments on either)
> 4. users have to search bugs on 2 trackers (both if they want to open a new one and also
>      if they are just looking for one)
> 5. forgejo lacks some nice features like searching per number of votes
> 
> So what are we going to do now ?
> T. Undo the half move and stay with trac, move or loose 61+32 tickets from forgejo to trac
> F. Fully move from trac to forgejo, move 3176+8501 tickets from trac to forgejo
> D. have some tickets in trac and some in forgejo, require users to register and search both
> ?. something else ?
> 
> 
> Ideas, Comments ?

I do think trac is a dead end software, and we want to eventually retire it.
It can stick around in read-only mode indefinitely, eventually turned 
into a dump of static HTML pages. But it's not a software that we can 
keep supporting forever.

I thought Forgejo had votes as well, but I can't find them anymore, so I 
might be misremembering that.
But the usual issue conclusions are represented via labels, and they do 
exist. And have been used for that purpose already.
Not sure I'd really want to stick with hard to maintain trac just for 
voting on issues. If we really want that, it'd probably easier to 
contribute that feature to Forgejo.

I'm also not a fan of migrating issues, since the migrates one are 
always going to be horribly ugly, basically just consisting of one big 
quote posted by a bot account.
It is possible to do though, so if that's desired instead of keeping 
trac itself around, I can look into it.

So my preferred solution is to just keep the two separated, disable new 
tickets on trac, and at some point in the distant future make trac fully 
read-only/turn it into static HTML pages.

Forgejo already back-references trac issues when they're tagged 
somewhere on the FFmpeg/FFmpeg repo, hence all the new issues/PRs start 
at 20000.
If we really kept using trac that would also eventually clash and then 
really make a huge mess.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org