Hi Alexander

On Tue, Sep 16, 2025 at 03:59:38PM +0200, Alexander Strasser via ffmpeg-devel wrote:
> On 2025-09-16 10:49 +0200, Michael Niedermayer via ffmpeg-devel wrote:
> > 
> [...]
> > 
> > * If we keep forgejo we will likely transition our issue tracker tickets
> >   into forgejo too, discussing with timo yesterday night indicates that
> >   this likely can be done cleaner and neater than at first expected.
> 
> I would say this is not an absolute requirement and you also say likely.
> 
> Just saw Timo voicing his concerns in #ffmpeg-devel , not on the
> technical part but about if it really is a good idea.
> 
> I'm not entirely sure what is best and on the practicality and effort.

The effort to handle 2 issue trackers is real, especially for users
and would make ffmpeg look incompetent on top of that

I read some random comments on redmine and people spoke about
transitioing from trac to redmine from redmine to gitlab.
I mean that they done that and no longer needed trac import support thus.

If you look at google they switched their tracker for ther fuzzer
stuff, all issues where transitioned there are no "static html"
with banners


> Could also imagine to leave a static readonly version online and add a
> banner at the top on how to proceed with new issues.

we moved the whole history from cvs to svn then from svn to git


> 
> Just saying IMHO we should postpone this detailed discussion to a later
> point iff our Forgejo instance will be the primary forge.
> 

> Also in that case I think migrating our Trac Wiki would be a good idea
> and should be done first (before tackling our Trac issues).

As long as the wiki is only in one place the wiki can wait.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you think the mosad wants you dead since a long time then you are either
wrong or dead since a long time.