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: [POLL] [VOTE] code.ffmpeg.org vs. ML Date: Tue, 16 Sep 2025 22:39:32 +0200 Message-ID: <20250916203932.GT29660@pb2> (raw) In-Reply-To: <aMltSgJ_o8VQDnqi@metallschleim.local> [-- Attachment #1.1: Type: text/plain, Size: 1944 bytes --] 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. [-- 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-16 20:40 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-09-16 8:49 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel 2025-09-16 9:00 ` [FFmpeg-devel] " Diederick C. Niehorster via ffmpeg-devel 2025-09-16 11:04 ` Timo Rothenpieler via ffmpeg-devel 2025-09-16 11:12 ` Martin Storsjö via ffmpeg-devel 2025-09-16 18:49 ` Michael Niedermayer via ffmpeg-devel 2025-09-16 19:54 ` Martin Storsjö via ffmpeg-devel 2025-09-17 9:41 ` Nicolas George via ffmpeg-devel 2025-09-18 12:00 ` Michael Niedermayer via ffmpeg-devel 2025-09-16 11:13 ` Martin Storsjö via ffmpeg-devel 2025-09-16 11:54 ` Marvin Scholz via ffmpeg-devel 2025-09-16 13:59 ` Alexander Strasser via ffmpeg-devel 2025-09-16 20:39 ` Michael Niedermayer via ffmpeg-devel [this message] 2025-09-16 21:12 ` Balint Marton via ffmpeg-devel 2025-09-17 14:24 ` Timo Rothenpieler via ffmpeg-devel 2025-09-17 18:32 ` Marton Balint via ffmpeg-devel 2025-09-17 23:41 ` Timo Rothenpieler via ffmpeg-devel 2025-09-18 7:02 ` Nicolas George via ffmpeg-devel 2025-09-18 8:52 ` Jacob Lifshay via ffmpeg-devel 2025-09-18 9:15 ` Nicolas George via ffmpeg-devel 2025-09-18 9:49 ` Jacob Lifshay via ffmpeg-devel 2025-09-18 12:18 ` Niklas Haas via ffmpeg-devel 2025-09-18 17:44 ` Marton Balint via ffmpeg-devel 2025-09-17 14:46 ` Niklas Haas via ffmpeg-devel 2025-09-17 3:57 ` Philip Langdale via ffmpeg-devel 2025-09-17 9:42 ` Nicolas George via ffmpeg-devel 2025-09-17 14:44 ` Niklas Haas via ffmpeg-devel 2025-09-18 9:10 ` Zhao Zhili via ffmpeg-devel 2025-09-17 14:53 ` softworkz . via ffmpeg-devel 2025-09-18 9:20 ` Gyan Doshi via ffmpeg-devel 2025-09-19 7:46 ` Peter Ross 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=20250916203932.GT29660@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