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 ?
thx
On Sun, Sep 14, 2025 at 11:23:17PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi everyone
>
> trac supports, custom search queries, customly formated results
>
> People can vote on tickets, we can have custom ticket states and custom
> workflow on tickets.
>
> Are these things possible in forgejo ?
>
> For example, what we use in trac:
>
> Open Tickets ordered by number of votes colored based on priorty
> https://trac.ffmpeg.org/report/11
>
> Non Developer tickets:
> https://trac.ffmpeg.org/report/15
>
> Open and New tickets sorted by priority:
> https://trac.ffmpeg.org/report/1
>
> Closed Tickts showing the resolution (needs_more_info, fixed, invalid,
> wontfix) sorted by last modification:
> https://trac.ffmpeg.org/query?status=closed&order=changetime&desc=1&col=id&col=summary&col=type&col=component&col=resolution&col=changetime
>
> thx
>
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Some people wanted to paint the bikeshed green, some blue and some pink.
> People argued and fought, when they finally agreed, only rust was left.
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
