From: Vittorio Giovara <vittorio.giovara@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/s302m: enable non-PCM decoding Date: Sun, 18 Feb 2024 23:47:56 +0100 Message-ID: <CABLWnS8XKw3dFV4u2KG4hSr+X2z8FC+1MUzPBFHs0AEws_zgaQ@mail.gmail.com> (raw) In-Reply-To: <20240218223439.GP6420@pb2> On Sun, Feb 18, 2024 at 11:34 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > Hi > > On Sun, Feb 18, 2024 at 07:20:43PM +0100, Anton Khirnov wrote: > > Quoting Michael Niedermayer (2024-02-18 01:43:14) > > > "If the disagreement involves a member of the TC" > > > does IMHO not preclude commenting on a patch. > > > > > > For a disagreement we need 2 parties. For example one party who > > > wants a patch in and one who blocks the patch. or 2 parties where both > > > block the other. > > > > > > Being a party of a disagreement would not make anyones opinon invalid. > > > > Anything that goes to TC is a disagreement. > > probably, thats true, yes > > > > Anyone who expressed an > > opinion on the patch then is 'a party to the disagreement'. > > no, i dont see it that way > A developer blocking a patch is a party to the disagreement > So is the developer who calls the TC because of that. > Disagree. If that basically means that no patches will be ever blocked by the members of the TC! They should express the best technical excellence of the whole community, not be stifled from participating in the discussion If it helps, I'll block the patch so that Anton can vote in the TC. Do you see how slippery (and insane) this interpretation of the rule becomes? > Similarly if you look at real world court cases > parties to the lawsuit are the one who is filling the lawsuit and > the defendant. > The thousand people expressing an oppinion in some random place are > not parties to the disagreement > This is a false dichotomy, we're not a court case where we're interpreting the law, we're trying to solve a technical disagreement. > More formally, you could define a "party to a disagreement" as > all minimal sets of people whos non existence would resolve the > disagreement > By that reasoning you shouldn't vote either since you touched basically all of ffmpeg codebase! > * A disagreement implies that there are 2 parties > * And we assume here that what one party wants is better for FFmpeg than > what the other wants. > * The TC needs to find out which partys choice is better or suggest a 3rd > choice. > * If one but not the other party is a member of the TC then this decission > becomes biased if that member votes > > Your interpretation suggests that the TC members are "above" everyone and > should > prevail in arguments they have with others. > Nobody is saying that!!! > I dont think the GA has given that power to the TC. > Are you suggesting to have a vote to rewrite/reinterpret the rule? -- Vittorio _______________________________________________ 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:[~2024-02-18 22:48 UTC|newest] Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-23 6:49 Gyan Doshi 2024-01-23 6:49 ` [FFmpeg-devel] [PATCH 2/2] fate: add tests for dolby_e decoding in s302m Gyan Doshi 2024-01-23 7:56 ` [FFmpeg-devel] [PATCH 1/2] avcodec/s302m: enable non-PCM decoding Kieran Kunhya 2024-01-23 8:32 ` Gyan Doshi 2024-01-23 9:05 ` Kieran Kunhya 2024-01-23 14:50 ` Devin Heitmueller 2024-01-23 14:53 ` Kieran Kunhya 2024-01-23 15:04 ` Devin Heitmueller 2024-01-23 10:28 ` Nicolas Gaullier 2024-01-23 11:18 ` Gyan Doshi 2024-01-25 4:59 ` Andreas Rheinhardt 2024-01-25 7:11 ` Gyan Doshi 2024-01-25 13:17 ` Andreas Rheinhardt 2024-01-26 4:23 ` Gyan Doshi 2024-01-26 6:42 ` Andreas Rheinhardt 2024-01-28 10:54 ` Anton Khirnov 2024-01-28 21:29 ` Kieran Kunhya 2024-01-29 4:00 ` Gyan Doshi via ffmpeg-devel 2024-01-29 9:27 ` Nicolas Gaullier 2024-01-29 10:17 ` Gyan Doshi 2024-01-29 10:18 ` Kieran Kunhya 2024-02-15 10:47 ` Anton Khirnov 2024-02-15 12:31 ` Gyan Doshi 2024-02-15 16:10 ` Anton Khirnov 2024-02-15 16:47 ` Gyan Doshi 2024-02-15 20:26 ` Kieran Kunhya 2024-02-16 4:12 ` Gyan Doshi 2024-02-16 9:03 ` Anton Khirnov 2024-02-17 11:46 ` Gyan Doshi 2024-02-17 12:22 ` Anton Khirnov 2024-02-17 12:37 ` Gyan Doshi 2024-02-17 19:55 ` Anton Khirnov 2024-02-18 0:43 ` Michael Niedermayer 2024-02-18 18:20 ` Anton Khirnov 2024-02-18 22:34 ` Michael Niedermayer 2024-02-18 22:47 ` Vittorio Giovara [this message] 2024-02-19 8:45 ` Nicolas George 2024-02-19 14:15 ` Vittorio Giovara 2024-02-19 14:28 ` Nicolas George 2024-02-19 14:37 ` Vittorio Giovara 2024-02-19 14:41 ` Nicolas George 2024-02-18 22:48 ` Hendrik Leppkes 2024-02-19 1:17 ` Michael Niedermayer 2024-02-19 2:26 ` Vittorio Giovara 2024-02-19 2:07 ` Ronald S. Bultje 2024-02-19 21:37 ` Anton Khirnov 2024-02-19 21:54 ` Nicolas George 2024-02-20 21:39 ` Michael Niedermayer 2024-02-20 21:56 ` Kieran Kunhya 2024-02-20 22:07 ` Nicolas George 2024-02-18 18:50 ` Rémi Denis-Courmont 2024-02-18 18:55 ` Nicolas George 2024-02-18 4:06 ` Gyan Doshi 2024-02-18 18:03 ` Anton Khirnov 2024-02-18 18:40 ` Nicolas George 2024-02-18 19:03 ` Rémi Denis-Courmont 2024-02-18 19:11 ` Nicolas George 2024-02-18 21:06 ` Vittorio Giovara 2024-02-18 21:25 ` Nicolas George 2024-02-18 21:55 ` Vittorio Giovara 2024-02-19 8:54 ` Nicolas George 2024-02-19 14:21 ` Vittorio Giovara 2024-02-19 14:30 ` Nicolas George 2024-02-19 14:33 ` Vittorio Giovara 2024-02-19 14:34 ` Nicolas George 2024-02-18 19:02 ` Gyan Doshi 2024-02-18 21:46 ` Vittorio Giovara 2024-02-19 5:10 ` Gyan Doshi 2024-02-19 14:30 ` Vittorio Giovara 2024-02-19 15:39 ` Gyan Doshi 2024-02-20 3:02 ` Vittorio Giovara 2024-02-17 12:31 ` Rémi Denis-Courmont 2024-02-19 2:16 ` epirat07 2024-02-16 13:55 ` Andreas Rheinhardt 2024-02-17 11:44 ` Gyan Doshi
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=CABLWnS8XKw3dFV4u2KG4hSr+X2z8FC+1MUzPBFHs0AEws_zgaQ@mail.gmail.com \ --to=vittorio.giovara@gmail.com \ --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