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 854A0430DF for ; Fri, 19 Aug 2022 16:01:43 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 1F7BD68B979; Fri, 19 Aug 2022 19:01:40 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 2666068B2BC for ; Fri, 19 Aug 2022 19:01:34 +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 27JG1XOm023680 for ; Fri, 19 Aug 2022 18:01:33 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id 3ED78E0101; Fri, 19 Aug 2022 18:01:33 +0200 (CEST) Date: Fri, 19 Aug 2022 18:01:33 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20220817214932.42351-1-george@nsup.org> MIME-Version: 1.0 In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Fri, 19 Aug 2022 18:01:33 +0200 (CEST) Subject: Re: [FFmpeg-devel] [PATCH 1/2] doc/plans: add a file to list approved projects 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="===============2721724995314316808==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2721724995314316808== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="V+QAngsNqfHLlitL" Content-Disposition: inline --V+QAngsNqfHLlitL Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jean-Baptiste Kempf (12022-08-18): > Those plans files become outdated very quickly and are often not maintain= ed. > Or they become infinite unicorn-wishlist things. > Or they become a blocking task for the project. Or I might be hit by a bus. Or I might decide to try heroin and overdose because it was cut with fentanyl. Or=E2=80=A6 If we always focus on the worst-case scenario, we never go forward. Worst case scenario here? It becomes blocking, we discuss to remove it, wasted a little time. Less worst case scenario: it becomes an unicorn-wishlist, somebody finds something doable in it and starts contributing to the project. Anyway=E2=80=A6 > I have NO opinion on AVWriter, but just show the API and documentation be= fore implementing it. > Once people agree on the API need and form, just implement it, I don't se= e the need for a plans.md file for that. Hum, I like that idea. For AVWriter, much of the API itself is macros and inline functions, but it is a minor issue that I can work around. =E2=80=9COnce people agree=E2=80=9D means applying it; I hope nobody will b= ikeshed the idea of pushing a .h file with no implementation I insist that I am not doing this to =E2=80=9Cpreemptively shield [my] code= from criticism=E2=80=9D, like Anton disingenuously said. If that was the case, I would not have written =E2=80=9CThe resulting patches will be subject to technical review like any other patches=E2=80=9D. What I am trying to do is to find a way to discuss broad strokes before investing time in details, because without it the project is condemned to immobility because of naysayers. It is not specific to AVWriter, it is not specific to me. If we had that procedure at the time the new channel layout API was implemented, then we could have discussed it to take into account the needs of users, filters, advanced formats and devices and now have a great channel layout API. Instead, we had to salvage one that was not designed with these considerations in mind, but because it was a series of 279 patches, nobody dared send it back for complete redesign as we should have. I find this borderline dishonest. Depending on the responses to this mail, I will send a patch to add avwriter.h and doc/avwriter.md and start the actual discussion. Regards, --=20 Nicolas George --V+QAngsNqfHLlitL Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmL/s9sACgkQcZVLI8pN xgy+zA/+Ibvb42gmMXFbpqLZDI/66nVwjfpEFuDc4rkbDXrkCTKEkUVl9BOeX/AK NYsAvEhTnLvpKpXjYOxtd5mGHzofCudsNB+aP9enD511NVKDTQsjpFJjm5i0isFm FjivANa85fRki9MYZVt0hGP04IfrtcwPsTlkWFfRP9ej2W2ezDXcTDHgYkn7wfvw zrW/PvkNCmm9qoEFQeBwF6AmdyAhcPT+yX2h23qLMP42FQk7QKJyP6JOmiTFtuII d5TtZx3AtrzP8T4seF8J0ocFd1FKge8z93HWV1kqXAnFGg5zlw0Rt8GELxelfqXV 2AOLZg3w2AY0QltgExTQkz5m78/7ribprn0BGjTpewrje31eXAsZBK7Iqrr1FB1e csvPH/M3+2VXJ8GiN3LGt+jBYYqTukOIY2cTsONsOI1BpJGULVMncP5zZClDM+wb QwU5m+cso3kHBwi6i6IwhJj5WSz0ukGZ7681tkB+bv3umZp8XNDBNlBpOKgb7RtR obvN77SWB6lgkDXzixn7/FEQYXS4qzxZ8UX7mJlE1nZleTwgmfgDi4de2mvQQ4gz x2eJaQHKVsmIFTNIwi+BP1ih12BuxLZEfK2qt7Jt17AF8+n45r8g7VFBchREBjoa D8h105LbfDzivXoSGZNdbrS3HBgLVKgwkrB66IzOcnREaarsE7E= =y7aQ -----END PGP SIGNATURE----- --V+QAngsNqfHLlitL-- --===============2721724995314316808== 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". --===============2721724995314316808==--