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 5557143247 for ; Mon, 25 Jul 2022 19:01:13 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 39C2C68B7D2; Mon, 25 Jul 2022 22:01:11 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1E9AB68B630 for ; Mon, 25 Jul 2022 22:01:04 +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 26PJ13GG003681 for ; Mon, 25 Jul 2022 21:01:03 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id 33BB2EB5B9; Mon, 25 Jul 2022 21:01:03 +0200 (CEST) Date: Mon, 25 Jul 2022 21:01:03 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20220703170714.GF396728@pb2> <20220725113201.GU2088045@pb2> MIME-Version: 1.0 In-Reply-To: <20220725113201.GU2088045@pb2> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Mon, 25 Jul 2022 21:01:03 +0200 (CEST) Subject: Re: [FFmpeg-devel] [PATCH v5 00/25] Subtitle Filtering 2022 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="===============2273738767283734655==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2273738767283734655== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DkCjXYyW4zqsGO/F" Content-Disposition: inline --DkCjXYyW4zqsGO/F Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Michael Niedermayer (12022-07-25): > I think many if us, myself included have had un-fun periods in ffmpeg. > This on its own is already bad and we should strive to make project > contributions more fun to all. In my opinion, it would require at least two things: - That the members of the Community Committee step in more proactively in budding conflicts. And take sides: not =E2=80=9Cboth be nice=E2=80=9D = but =E2=80=9Cyou started it, shut up=E2=80=9D. - A person or group of person capable of deciding ahead if a change that will affect every body is worth investing time implementing it. > If we add a XML parser to FFmpeg. Such a thing would be used by several > bits and we need to ensure it has redundant maintainership. > So i think a xml parser needs broad support by developers otherwise we > run the risk that if it has a single maintainer only and that maintainer > stops maintaining it that could be annoying to more than just the parser > itself. > I cannot remember exactly without re-reading the old thread what the issu= es > people had with the xml parser. If it was some component of it or in gene= ral. > But i think its mostly a question if theres more than one person who wants > to maintain it. There is nothing to re-read: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/thread.html#296107 Nobody answered. Even to send files to make sure they would be supported. We would need reliable maintainers, you are right. But right now, we rely on libxml2, and that is not ideal: it is not a standard library on non-Linux systems, and even if it seems better nowadays, it used to be a =E2=80=9Csecurity issue of the week=E2=80=9D kind of library. > If you work on libavfilter, noone will snatch it from you. If you > dont work on it, eventually someone else will attempt to take over and > push libavfilter in the direction he feels best which may or may not=20 > match what you want. I will try to motivate myself to advance the FATE coverage, which is the blocking issue. Thanks, --=20 Nicolas George --DkCjXYyW4zqsGO/F Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmLe6G0ACgkQcZVLI8pN xgypmA//X5GVuDwIxILfk4ImRrnTQ3aZwAWLkRTIsehujN63vdySaiDLsKs2ne9b x5AVuC6i/mcr08H7gsTg/aVwvZaMrF7KukMqPIPF/2An3e4Bl2Emzkj47qm7tHIY 7sa+FEDgpRApUWJ8U4WDGhl2VOwBs8xJpOdyulcEBizwosiSAbaOAQ3vU5lvUVYo zQEFyX1pudPumTqZV3hmKPO52HhP9H6bMwJLRstnsoxT/jB1h+QxKuVoaUFdEL+k qd/1y2ZbxyjKSwKAPba7gRVVhl8u44Gdtqibf+jaGrjWvLIHMJNe7mQCfIfPtU06 NLskoVLP5R23Pahmr9KEZzdx2iLpRzY7L1pmpX47N53pB8X7TiCViD0eTgatLW5m e+oGMlwkLtlvGvjBppPJ2OK8UXAr49VQRtEw0YCZwuXCNbLAFvjPYiSlvDQdrE3C ybE4Aqkpb02impq4NYPPqlpFaqkI8eeWf+HIlMSWe6xSsxzv0SrhB5/G2INenmHb 0fybMJGt5H45V/nekMm3nSSEi+aPgUGKL/FiadzP1IOG9E0pz/LFXgfyfr/01rGZ u4pj/CGw8m5mFaSc/8AMGSWSqQMbharqNzvLoSfgqS6OYNaMdZfb7lZNGTjhQeir xmMIQmgIslZ3GIXmLQy3D7C55GLaDlOkFSPjeTWb65in/pLZI+Y= =LLmP -----END PGP SIGNATURE----- --DkCjXYyW4zqsGO/F-- --===============2273738767283734655== 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". --===============2273738767283734655==--