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 CDFD7410C6 for ; Mon, 9 Oct 2023 19:49:32 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id DD89468CA95; Mon, 9 Oct 2023 22:49:29 +0300 (EEST) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E08C268C953 for ; Mon, 9 Oct 2023 22:49:22 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 9E73A40004 for ; Mon, 9 Oct 2023 19:49:21 +0000 (UTC) Date: Mon, 9 Oct 2023 21:49:20 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20231009194920.GC3543730@pb2> MIME-Version: 1.0 X-GND-Sasl: michael@niedermayer.cc Subject: [FFmpeg-devel] [RFC] SDR Vote 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="===============8493499060824699171==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8493499060824699171== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ftjCgYj7ABv2ooUJ" Content-Disposition: inline --ftjCgYj7ABv2ooUJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all On VDD I was asked about (not) listing a release with SDR on the download p= age and IIRC the consensus was to do a vote on it. As you notice i am a bit hesitant to start a vote because its always better to find solutions evereyone is happy with and not just a majority. I also would prefer this vote to be done by someone neutral and not me but i failed to find a volunteer for that (and i tried). So if i have to make this vote, the plan would be to take the GA list of people posted in the last VDD mail. And use vote.ffmpeg.org (maybe make a test vote first, iam not sure) and then vote about the 2 main Questions, both independantly, they seem simple yes/no votes. The first Vote is, SDR in git master yes/no. (a no implies that i will maintain a seperate fork of FFmpeg with SDR) We could also make these 2 options more elaborate: * Two FFmpegs, one official FFmpeg without SDR. And one inofficial maintain= ed by Michael with all features including the self contained SDR avdevice/demuxer. OR * One FFmpeg, including the self contained SDR avdevice/demuxer. (self contained SDR avdevice/demuxer.) is the code as it is in the libavrad= io repository that is currently: https://git.ffmpeg.org/gitweb/libavradio.git/commitdiff/886e4ed6521e288a572= 3a9896dc1cf96af127630?hp=3Da47afb80840e5ecd5eaf2d583e9a042805ad204a All suggested cleanup and fixes people might find, will of course be done b= efore applying The 2nd question is *. Our download page shall only list the official FFmpeg release / reposito= ries OR *. FFmpeg developers can list their maintained FFmpeg forks on the download= page These shall be listed with some description and the name or alias of the= maintainer(s). What about the external library? * No volunteer to design or even talk about the API, no volunteer to maintain seperate build system and testing infra. * Inconvenient at this stage for developing the code, API/ABI gets too enta= ngled into design decissions, so internal design has to settle down first IMO. OR API has to be very high = level but then its a clone of avdevice API and some people opposed that too. so its git master or fork or sdr code dies really and i dont want the code to die and so we end with this RFC, and if noone comes up with a practical/realist= ic alternative then a vote. A problem is that there is a divide between the developers making decissions about the SDR code (for example asking for an external library) and the developers working on the SDR code. This is a difficult setup. Normally we have people maintaining / working on / being affected by / being the aut= hors of some code making decissions about it. Thx --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB When you are offended at any man's fault, turn to yourself and study your own failings. Then you will forget your anger. -- Epictetus --ftjCgYj7ABv2ooUJ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZSRZPQAKCRBhHseHBAsP q713AJ9FroH+MLAetLaOBCgxqiqPq1MWWwCfVGFeUOyOl2q82EVN3Bzh6t6PRlQ= =efuE -----END PGP SIGNATURE----- --ftjCgYj7ABv2ooUJ-- --===============8493499060824699171== 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". --===============8493499060824699171==--