From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [RFC] fateserver
Date: Sat, 24 Feb 2024 18:49:32 +0100
Message-ID: <20240224174932.GL6420@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 830 bytes --]
Hi all
Both fateserver and the fateserver rewrite lack a mainteiner
The original:
https://fate.ffmpeg.org/
perl code here:
https://git.ffmpeg.org/fateserver
The rewrite (from Timothy Gu unmaintained since 2016)
https://fatebeta.ffmpeg.org/
https://github.com/TimothyGu/fateserver-node
Really only one of these need to be maintained, but one needs to be
If you know someone who may be interersted in this, please tell me
The situation ATM, where when someone reports an issue, theres noone
responsible, noone taking care of it even with simple issues. Is really
not good
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact
[-- 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 reply other threads:[~2024-02-24 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 17:49 Michael Niedermayer [this message]
2024-02-25 6:36 ` Marth64
2024-02-25 19:28 ` Michael Niedermayer
2024-02-26 0:21 ` Marth64
2024-02-26 2:57 ` Michael Niedermayer
2024-02-26 14:29 ` Michael Niedermayer
2024-03-08 1:08 ` Marth64
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=20240224174932.GL6420@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