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

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

On 15/09/2025 14:30, Michael Niedermayer via ffmpeg-devel wrote:
> Hi
> 
> On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via ffmpeg-devel wrote:
> [...]
> 
>>
>> I thought Forgejo had votes as well, but I can't find them anymore, so I
>> might be misremembering that.
> 
> One can add thumbs up and down to individual messages of an issue but they
> are not shown in the search results or searchable as far as i can see
> 
> In fact the whole search capability in Forgejo is disappointing
> even searching for open (not new) tickets doesnt work as documented
> (one cannot disable "new" lables by alt + mouse click it works by
>   alt + keyboard click)
> 
> 
>> 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.
> 
> Naively, i would have thought that issue migration would be done by a
> Database -> Database thing

Yeah, that's how I'd do it as well. But every actual reply to an issue 
needs to be associated to a user, and spamming our user DB with 
thousands of users just for the migration isn't great.

> but there are many shades of this
> 
> one could leave issues in trac and instead extend Forgejos search so it
> simply in addition to what it does also have it run a sql querry
> in the trac db and simply return links to the trac tickets

I doubt Forgejo would accept that as a contribution, and I do not really 
want to start maintaining a fork of Forgejo for our instance.

> this actually feels like quite doable for someone knowing Forgejo
> and also the trac db layout. (that is not me)

It'd need to be done in some generic way so that any arbitrary issue 
tracker can be hooked up like that. So it's quite a bit of work.

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

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