From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat: add Software Defined Radio support
Date: Sun, 25 Jun 2023 00:19:04 +0200
Message-ID: <ZJdr2DdGMIZDROZ9@phare.normalesup.org> (raw)
In-Reply-To: <20230623181241.GN3250409@pb2>
[-- Attachment #1.1: Type: text/plain, Size: 3247 bytes --]
Michael Niedermayer (12023-06-23):
> * What iam interrested in was working with the signals at a low level, why
> because i find it interresting and fun.
Then this is what you should be spending your time on, and to hell with
anybody who says otherwise.
Unless you have commitments that we are not privy of, nobody can tell
you how you are supposed to be spending your time and skills. Nobody can
force you to manage releases and fix fuzzing bugs and do all the things
you do that are necessary to the project. Necessary to a conception of
the good of the project that is not even your own I think.
Nobody can prevent you from hacking the things that motivate you. At
worst, they can prevent you from committing the resulting code into
official FFmpeg. That would be the project's loss, and you can still
publish it on a private branch. But they do not have the power to block
you from pushing. It is not even clear they have the authority do block
you, more so if the code is really good and fits FFmpeg well. The only
thing that can block you is your desire to play nice and not harm the
project. I would like to emphasize that some of the frequent naysayers
do not have an excellent track record when it comes to playing nice and
especially not harming the project.
I am especially annoyed by the “it's too hard” naysayers — the same I
have been getting when I say that I want to write a XML suited to our
needs to replace our use of libxml. They do not realize they reveal more
about their own skills than anybody else. You know if you can write a
radio, so ignore them and go ahead. And if they were right, if it is too
hard and you fail… well, you would just have wasted your own time; and
you would have had fun and learned things on the occasion, which means
the time was not even wasted.
But the whole attitude who wants FFmpeg to be a Serious OpenSource TM
Project, who needs to make releases and worry above all about ABI
stability, is really the attitude who is killing all the fun in working
on FFmpeg.
Hey, people, realize FFmpeg does not exist to be a Serious OpenSource TM
Project, FFmpeg does not exist to serve other projects, to serve
companies who benefit from it give the bare minimum back.
FFmpeg exists because some day a dude thought it would be fun to write a
MPEG decoder. And everybody else told him it would be too hard,
everybody else told him to use an existing library and to leave it to
the professionals. He did not believe them and proved them utterly
wrong, and the rest, as the saying goes, is history.
So I will say it explicitly. We — me, and everybody who agrees with me —
do not want to just maintain a bunch of wrappers for the convenience of
others, we want to have fun writing interesting code, trying new ways of
doing things, inventing original optimizations. We can find a balance
and work on useful things too. But if you want us to work only on the
boring useful things, if you want to bar us from working on fun things,
then just fork you.
P.S.: I do not think I am skilled enough in that area to review your
code. But if you think I am, maybe on some parts, then I will happily.
Regards,
--
Nicolas George
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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:[~2023-06-24 22:19 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 22:28 Michael Niedermayer
2023-06-22 13:43 ` Michael Niedermayer
2023-06-22 13:55 ` James Almer
2023-06-22 15:05 ` Michael Niedermayer
2023-06-22 15:10 ` James Almer
2023-06-22 16:26 ` Michael Niedermayer
2023-06-22 16:42 ` James Almer
2023-06-22 22:00 ` Michael Niedermayer
2023-06-23 2:34 ` Kieran Kunhya
2023-06-23 11:17 ` Michael Niedermayer
2023-06-23 11:36 ` Kieran Kunhya
2023-06-23 16:37 ` Rémi Denis-Courmont
2023-06-23 18:12 ` Michael Niedermayer
2023-06-23 18:17 ` Paul B Mahol
2023-06-23 18:56 ` Michael Niedermayer
2023-06-23 19:10 ` Paul B Mahol
2023-06-23 19:16 ` James Almer
2023-06-24 20:27 ` Rémi Denis-Courmont
2023-06-24 21:03 ` Tomas Härdin
2023-06-25 13:53 ` Michael Niedermayer
2023-06-25 14:25 ` Michael Niedermayer
2023-06-24 22:19 ` Nicolas George [this message]
2023-06-25 14:10 ` Michael Niedermayer
2023-06-27 19:09 ` Rémi Denis-Courmont
2023-06-28 22:15 ` Tomas Härdin
2023-06-29 7:14 ` Nicolas George
2023-06-29 9:46 ` Jean-Baptiste Kempf
2023-06-30 21:51 ` Tomas Härdin
2023-07-02 8:11 ` Michael Niedermayer
2023-07-02 9:34 ` Nicolas George
2023-07-02 9:54 ` Tomas Härdin
2023-07-02 9:56 ` Nicolas George
2023-06-23 20:10 ` Tomas Härdin
2023-06-23 21:18 ` Michael Niedermayer
2023-06-24 9:51 ` Tomas Härdin
2023-06-24 21:01 ` Michael Niedermayer
2023-06-24 22:01 ` Tomas Härdin
2023-06-25 9:54 ` Michael Niedermayer
2023-06-27 9:00 ` Tomas Härdin
2023-06-27 10:57 ` Nicolas George
2023-06-27 17:07 ` Tomas Härdin
2023-06-27 17:11 ` Nicolas George
2023-06-25 10:23 ` Kieran Kunhya
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=ZJdr2DdGMIZDROZ9@phare.normalesup.org \
--to=george@nsup.org \
--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