From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] statictrac, trac and caching Date: Sun, 15 Jun 2025 18:53:30 +0200 Message-ID: <20250615165330.GZ29660@pb2> (raw) In-Reply-To: <CAAhd_PVjRijuj8OZpeFseNafhid2fM2Z7YRf2HQtDNu55iUUYQ@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1459 bytes --] Hi Marth64 On Sun, Jun 15, 2025 at 11:06:47AM -0500, Marth64 wrote: > On Sun, Jun 15, 2025 at 10:57 AM Kacper Michajlow > <kasper93-at-gmail.com@ffmpeg.org> wrote: > > Maybe it's time to retire the trac? It is quite slow by design and not > > really actively maintained anymore. Holding onto legacy software > > always increases the burden of maintainability. > > I do feel that a good portion of wiki technical documentation can > probably be moved to the main docs. The wiki has the huge advantage that people can edit it easily Editing the docs people have to do a git checkout, edit a file with an editor, make a git commit read patch submission rules submit a patch to ML or forge. Thats alot stumbling blocks thrown in ones way > There are some good examples and information there that seem to me can > be crystallized into plain old texi. > While I'm neutral about Trac I think in a sense this could also help > in the sense of reducing server load for this somewhat static content. yesterdays incident had like ~40k accesses on teh same file. So moving 99% of content out of trac would not have helped if that file was in teh 1% thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Let us carefully observe those good qualities wherein our enemies excel us and endeavor to excel them, by avoiding what is faulty, and imitating what is excellent in them. -- Plutarch [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-06-15 16:53 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-15 13:35 Michael Niedermayer 2025-06-15 13:42 ` Michael Niedermayer 2025-06-15 13:53 ` Derek Buitenhuis 2025-06-15 15:58 ` [FFmpeg-devel] Forensics Was: " Michael Niedermayer 2025-06-15 16:17 ` Derek Buitenhuis 2025-06-15 14:45 ` [FFmpeg-devel] " James Almer 2025-06-15 16:13 ` [FFmpeg-devel] Forensics Was: " Michael Niedermayer 2025-06-15 18:45 ` Michael Niedermayer 2025-06-15 14:53 ` [FFmpeg-devel] " James Almer 2025-06-15 15:57 ` Kacper Michajlow 2025-06-15 16:06 ` Marth64 2025-06-15 16:53 ` Michael Niedermayer [this message] 2025-06-15 17:03 ` Marth64 2025-06-15 16:48 ` Michael Niedermayer 2025-06-15 19:05 ` Michael Niedermayer 2025-06-15 16:28 ` Michael Niedermayer
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=20250615165330.GZ29660@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.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