From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Michael Niedermayer <michael@niedermayer.cc> Subject: [FFmpeg-devel] Re: [RFC] Issue tracker Date: Mon, 15 Sep 2025 14:30:49 +0200 Message-ID: <20250915123049.GJ29660@pb2> (raw) In-Reply-To: <62f9da36-5260-49d3-8cf7-d59d6456fb0d@rothenpieler.org> [-- Attachment #1.1: Type: text/plain, Size: 1897 bytes --] 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 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 this actually feels like quite doable for someone knowing Forgejo and also the trac db layout. (that is not me) thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If a bugfix only changes things apparently unrelated to the bug with no further explanation, that is a good sign that the bugfix is wrong. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 163 bytes --] _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-09-15 12:31 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-09-14 21:23 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel 2025-09-15 11:09 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel 2025-09-15 11:37 ` Michael Niedermayer via ffmpeg-devel 2025-09-15 12:06 ` Timo Rothenpieler via ffmpeg-devel 2025-09-15 12:30 ` Michael Niedermayer via ffmpeg-devel [this message] 2025-09-15 12:47 ` Timo Rothenpieler via ffmpeg-devel 2025-09-15 12:57 ` Michael Niedermayer via ffmpeg-devel 2025-09-15 13:05 ` Michael Niedermayer via ffmpeg-devel 2025-09-15 17:19 ` Timo Rothenpieler via ffmpeg-devel 2025-09-15 18:26 ` Michael Niedermayer via ffmpeg-devel 2025-09-15 18:35 ` Timo Rothenpieler via ffmpeg-devel 2025-09-15 19:09 ` Gyan Doshi via ffmpeg-devel 2025-09-15 21:46 ` Michael Niedermayer via ffmpeg-devel 2025-09-16 4:39 ` Gyan Doshi via ffmpeg-devel 2025-09-15 22:36 ` Michael Niedermayer via ffmpeg-devel
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20250915123049.GJ29660@pb2 \ --to=ffmpeg-devel@ffmpeg.org \ --cc=michael@niedermayer.cc \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git