From: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Timo Rothenpieler <timo@rothenpieler.org> Subject: [FFmpeg-devel] Re: [RFC] Issue tracker Date: Mon, 15 Sep 2025 20:35:21 +0200 Message-ID: <1298de15-af42-4280-b897-97aadab95087@rothenpieler.org> (raw) In-Reply-To: <20250915182620.GM29660@pb2> [-- Attachment #1.1: Type: text/plain, Size: 2538 bytes --] On 9/15/2025 8:26 PM, Michael Niedermayer via ffmpeg-devel wrote: > Hi Timo > > On Mon, Sep 15, 2025 at 07:19:17PM +0200, Timo Rothenpieler via ffmpeg-devel wrote: >> On 9/15/2025 2:57 PM, Michael Niedermayer via ffmpeg-devel wrote: >>> Hi >>> >>> On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via ffmpeg-devel wrote: >>>> On 15/09/2025 13:09, Michael Niedermayer via ffmpeg-devel wrote: >>> [...] >>>>> Ideas, Comments ? >>>> >>>> I do think trac is a dead end software, and we want to eventually retire it. >>> >>> btw, anyone knows why the trac project seems dieing / dead ? >>> Its a quite capable issue tracker ... >>> >>> also how is it related to redmine, which seems to have some support >>> for importing trac ? >>> >>> Have we considered redmine as alternative ? >>> If we could do a full import of trac, this may be a smoother >> >> redmine is apparently a "trac clone written in ruby". >> No idea if it's database-compatible, or just similar idea but full >> re-implementation. >> > >> But really, I don't see how in the long run a separate issue tracker from >> Forgejo makes sense. >> The issue IDs will eventually clash, and integration and linking between >> them will be a right mess. > > the mix of trac and Forgejo is already a mess if theres no _clean_ > way to import the tickets > We would always have 15 years of ticket history outside our issue tracker > > if you really want to have pull requests and issues have distinct positive numbers > well, make one even and the other odd above the value where they would clash > so it would be > 0..20k Trac > 20k-25k Forgejo > 25k+ even Forgejo > 25k+ odd redmine That is not something that can be done, and honestly seems a bit silly to me. > >> >> Plus the multi-account issue you mentioned. > > redmine can accept OAuth2/OIDC logins via plugins IIUC > would need to be tested in a test setup but there seems support for shared > accounts in principle I honestly don't understand the insistence on an external issue tracker. That just makes things more complex for no real reason. And I also firmly disagree about the current setup being "a mess". With no new tickets being allowed on trac, its quite the opposite of that. If issues/tickets could be opened on both, then it'd be a mess. This way it's just a migration. And the tickets on trac won't go away, so no history will be lost. If you really want, I can import them all into Forgejo, but _that_ will be horribly messy. [-- Attachment #1.2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4742 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 18:35 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 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 [this message] 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=1298de15-af42-4280-b897-97aadab95087@rothenpieler.org \ --to=ffmpeg-devel@ffmpeg.org \ --cc=timo@rothenpieler.org \ /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