From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org
Date: Sun, 13 Jul 2025 23:47:40 +0200
Message-ID: <20250713214740.GH29660@pb2> (raw)
In-Reply-To: <CAEEMt2nyZpbXjeCNvGv7Y7bO6cC=R2j6Cx1-PEQix=4ERv35AA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1377 bytes --]
Hi Ronald
On Sun, Jul 13, 2025 at 02:04:15PM -0400, Ronald S. Bultje wrote:
> G, preferably hosted by videolan.
This poll really is about, what we should setup on our server.
If you want to discuss giving up our autonomy (not sure thats what you meant)
We can discuss that, though iam not sure email is the medium over which i can
convey my position successfully.
But let me try.
My vission for FFmpeg was, and is that it should be and remain the leading
multimedia framework. (I mean its even in teh "about" of ffmpeg)
And i very much would like to move in this direction together with everyone
who shares this vission. (including all the innovation, AI and so on in ffmpeg)
I also belive that decissions in FFmpeg should be made by the community
(who shares a similar vission).
And really the leading multimedia framework needs its own server and cannot
be hosted by another multimedia framework.
Thats on top of reasons related to performance, independance, and flexibility
Theres also the more personal reason, that i dont want to work on a #2
framework or appendix under some other framework. Id like to compete and
win and be working on #1 :)
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The greatest way to live with honor in this world is to be what we pretend
to be. -- Socrates
[-- 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-07-13 21:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 11:43 Michael Niedermayer
2025-07-13 11:49 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 11:58 ` Timo Rothenpieler
2025-07-13 15:57 ` Michael Niedermayer
2025-07-13 16:07 ` Timo Rothenpieler
2025-07-13 16:15 ` Timo Rothenpieler
2025-07-13 18:51 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 19:03 ` Yalda
2025-07-13 14:38 ` Rémi Denis-Courmont
2025-07-13 15:56 ` Jacob Lifshay
2025-07-13 15:58 ` Timo Rothenpieler
2025-07-13 17:35 ` Michael Niedermayer
2025-07-13 18:04 ` Ronald S. Bultje
2025-07-13 19:47 ` Timo Rothenpieler
2025-07-13 21:47 ` Michael Niedermayer [this message]
2025-07-13 22:07 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 21:55 ` Philip Langdale via ffmpeg-devel
2025-07-13 22:04 ` Timo Rothenpieler
2025-07-13 22:22 ` Marvin Scholz
2025-07-14 2:43 ` Zhao Zhili
2025-07-14 5:50 ` Steven Liu
2025-07-14 9:40 ` Hendrik Leppkes
2025-07-14 9:54 ` Lynne
2025-07-14 9:57 ` Gyan Doshi
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=20250713214740.GH29660@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