From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] unfuck FFmpeg Was: Re: [PATCH v0] Implement promeg decoder.
Date: Tue, 21 Jan 2025 16:17:43 +0100
Message-ID: <20250121151743.GG4991@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1169 bytes --]
Hi James
On Mon, Jan 20, 2025 at 12:07:27PM -0300, James Almer wrote:
> On 1/20/2025 11:30 AM, Nicolas George wrote:
[...]
> I'd really like if we can stop with the "Everything's fucked, nothing can be
> done" mails every other week and instead make use of the framework we came
> up with, or if needed, change it and improve it.
So you (plural) want to unfuck FFmpeg ?
to unfuck FFmpeg IMO
1. de-escalate
2. give the people who want to do the work confidence that they have the
support of the community behind them, dont try to find new ways
to screw everyone over
3. If something you want isnt happening be that a booth, be that some
documentation, whatever. You know, you want it -> you do it
or maybe help the person who already is trying to do it. Dont attack
them
4. I really think the recently growing mindset of "attack and defame"
should not be accepted.
5. If people want some formal ffgoverment, i think this is much more
work than what we all imagined. But we can do it.
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
You can kill me, but you cannot change the truth.
[-- 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".
reply other threads:[~2025-01-21 15:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250121151743.GG4991@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