On Mon, Sep 15, 2025 at 01:09:47PM +0200, 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 ?
Some brainstorming, potential steps that someone may need to do
for T,
phase 0:
+ forgejos new ticket page should redirect to trac instead of trac to
forgejo
or the page should explain the use of forgejo vs trac
phase 1
+ some or all of the 93 tickets should be moved to trac
(if all then forgejos issue tracker can be disabled)
phase 2:
+ we need to investigate some scalability issues. We have one admin page
that takes a really long time to load. It sometimes times out but seems
working ATM. But as users, tickets and sessions grow we will likely at
some point become unable to load this page without increasing timeouts
at webserver and browser. Timo has already spend time on
updating things, switching database and so on. So really solving this,
may involve becoming active in development on trac itself
for F,
phase 0:
+ bugreporting guide needs update
+ tracs new ticket page should explain the transition and link to forgejo
not just redirect (it confuses users especially if the bugreporting
guide just
pointed them to trac)
phase 1:
+ 11696 tickets need to be moved into forgejo with their metadata (creation
date, authors, comments, state, resolution, number, keywords, html and
git links,
CC, attachments) or we need to accept to loose this data in a searchable
way
+ keywords -> labels ?
+ per ticket redirects to forgejo
phase 2:
+ wiki needs to be transitioned to forgejo, ideally with history or we need
to keep the wiki in trac and disable in forgejo
+ per wiki page redirects to forgejo
phase 3:
+ trac shutdown
+ landing page (register & new) redirect to forgejo
note, we also serve trac.mplayerhq.hu
for D,
+ bugreporting guide needs update
+ both trackers search and register pages need to point to the other too
so the users know that they need to search both trackers
+ or hire some web UI developer and have her write a meta search
that searches both trakers
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Dictatorship: All citizens are under surveillance, all their steps and
actions recorded, for the politicians to enforce control.
Democracy: All politicians are under surveillance, all their steps and
actions recorded, for the citizens to enforce control.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
