From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 6595C4700D for ; Tue, 25 Jul 2023 09:33:21 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 08AFE68C899; Tue, 25 Jul 2023 12:33:19 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1BD2E68C746 for ; Tue, 25 Jul 2023 12:33:13 +0300 (EEST) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 36P9XChR007653 for ; Tue, 25 Jul 2023 11:33:12 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id 55048EB5B7; Tue, 25 Jul 2023 11:33:12 +0200 (CEST) Date: Tue, 25 Jul 2023 11:33:12 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20230722192957.703-1-michael@niedermayer.cc> <20230722192957.703-5-michael@niedermayer.cc> <20230723152304.GJ7802@pb2> <1eba1389c52dead477fa1fd445d5ae918be25951.camel@haerdin.se> <8396bdd379b9244a79ee045bb85f9e96b2fbfee6.camel@haerdin.se> MIME-Version: 1.0 In-Reply-To: <8396bdd379b9244a79ee045bb85f9e96b2fbfee6.camel@haerdin.se> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Tue, 25 Jul 2023 11:33:12 +0200 (CEST) Subject: Re: [FFmpeg-devel] [PATCH 5/6] fftools: avradio support X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============1269005046377796705==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============1269005046377796705== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JmV/DzTHtcokdSiZ" Content-Disposition: inline --JmV/DzTHtcokdSiZ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Tomas H=C3=A4rdin (12023-07-24): > Features either are or aren't in scope. I don't see how you can > compromise on that. The scope is what we decide it is, collectively, based on arguments. Your conception of the scope is only a small part of that, and even smaller if you cannot sustain it with arguments. =E2=80=9CI don't see how you can compromise on that=E2=80=9D is called dogm= atism and has no place in this project. The way I see it, avradio has about as much or as little its place in a project that historically contained software implementations of the major and minor multimedia codecs as hardware acceleration. Yet support for hardware acceleration has been added, to the convenience and satisfaction of everybody. > The Linux kernel also has separation of concerns.=C2=A0It has a concept of > userland for example, unlike say TempleOS. Not everything is in scope > for the Linux project. Yet features have repeatedly made back and forth between kernel and userland and mixed implementations, searching for the sweet spot of compromise between performance, security and convenience. Proof that =E2=80=9Cthe scope=E2=80=9D, even when there is a much more clea= rly delineated frontier, is fluid and a matter of compromise. If you cannot accept compromise, then your opinion should not be taken into consideration in a functioning collective project. > I have 63 forks of ffmpeg alone. I don't see the problem. I am doubtful whether this is to be considered a good thing or a bad thing, but I am rather leaning towards bad. > As for me being loudest, someone has to be. As a licensed amateur radio > operator I also happen to have domain knowledge, which is why I know > radio stuff will affect the code in profound ways, as we are already > seeing evidence of. These are hard-gotten learns. Well, if you are right, then we will see patches on the mailing list that will affect the code in profound ways, and you will be able to object to them then. But far from =E2=80=9Calready seeing evidence=E2=80=9D of the apocalypse yo= u predict, we see that the avradio code already delivers features while being self-contained and only required extending the signal processing abilities of our libraries a little, and in ways that are useful to other developers. So I guess it proves being licensed to operate something does not make you qualified to evaluate the difficulty in implementing the software of that thing. What a surprise. I will add that =E2=80=9Caffect the code in profound ways=E2=80=9D was actu= ally true for hardware acceleration, requiring a big mess in the code and significant to the internal API and even public API and user interface. Yet nobody is objecting to them. --=20 Nicolas George --JmV/DzTHtcokdSiZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmS/ltYACgkQcZVLI8pN xgymDhAArgoOijKdFYONjua5K+TgjCK2cM0NcSWc9rVssBwNkdxgcxLfbl2iEz33 1vC7e9bNgs385HwpTDBwRW4Ee1ndsHJMiWkmKrhMG1b+fCC3mJLg/Zlrnbki2ffd lFqK91hp3vsW20HmVkkicwOc8rYJmvG90CuvRx2Xdz+NscZyXRgEGpxFxtNuNyjc Q3vBmAyrWB4ehmhay8odNcRu5vqEgQIHapA9rDmuThZB6J9P7KQALU8eJ27UWBGt 5qYuAqipSzHPuvSI8b7w8PU4o+beGZJm9sSSETiVtno8UJRfUGKe5Wm3cZFhk2Bm cOIxh0tq6WU92BX4Rerd6l3kTLEJ/QW1QYRcO5PnsfKnHF+K2R+/ZK++OOmB3kJf 7ssyd42FuNuHIf6zrsg5FWWsW4o+ovf03jSnw8kB+ldB4e4vozoHOv7+7ufoQQUh AaitoJM9GbnWKwZZkK9ks9jTgIK6uM+3N2lMVRqms57+r+Msth0SrgLM3EVe1htk 9F+eezY7Ba7cbY/87b2ju6TP9CG+UofLYUBjYpOvj3YuqVGJSUqPZWWCYuC3u51n nkt0XEW3n2J/kRQLdjVBbKfDhBHPtTnQWJyLuUJiZBIeQxF42omd35uXvgHMkWOp 3GIbA19LRE5a8227sX4T+GafVgtC4xiqX1L4z5UMOCMfrgiASlA= =7Ter -----END PGP SIGNATURE----- --JmV/DzTHtcokdSiZ-- --===============1269005046377796705== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============1269005046377796705==--