From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] clarifying the TC conflict of interest rule
Date: Fri, 23 Feb 2024 15:18:04 +0100
Message-ID: <ZdipHKZfOiBYIig7@phare.normalesup.org> (raw)
In-Reply-To: <5110ad53-09ab-4980-acb9-6f1b2f658e43@gyani.pro>
Gyan Doshi (12024-02-23):
> Just to be clear, that's not my basis.
>
> I said,
>
> "As a TC member who is part of the disagreement, I believe your
> participation is recused."
>
> based on the existing rule,
>
> "If the disagreement involves a member of the TC, that member should recuse
> themselves from the decision"
>
> Disagreement implies the existence of opposing sides, so discussion members
> from both sides are barred from the TC proceedings.
> The wiggle room in interpretation is over whether 'involves' captures all
> participants, including minor ones, or just the principal interlocutors.
> Note that the rule says nothing about patch authorship or asymmetry in its
> application.
>
> Anton's original disagreement, as I understand it, is about the propriety of
> the rule i.e. he believes that pre-existing public opposition (or agreement)
> on the issue should not bar a TC member. That's a disagreement with the
> rule, not with its interpretation.
I am not sure what you mean exactly, but I suppose that if you mentioned
the rule here and not any other rule, it was because you thought it was
right to apply it, that this rule applied would make the ruling more
just and trustworthy.
My proposal wants to make absolutely clear your concern was valid.
Regards,
--
Nicolas George
_______________________________________________
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-23 14:18 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 8:22 Anton Khirnov
2024-02-20 8:50 ` Anton Khirnov
2024-02-20 9:12 ` Marton Balint
2024-02-20 9:21 ` Anton Khirnov
2024-02-20 19:32 ` Marton Balint
2024-02-22 21:34 ` Anton Khirnov
2024-02-20 10:01 ` Gyan Doshi
2024-02-20 11:09 ` Anton Khirnov
2024-02-22 6:50 ` Gyan Doshi
2024-02-22 21:21 ` Anton Khirnov
2024-02-23 7:56 ` Nicolas George
2024-02-23 10:56 ` Gyan Doshi
2024-02-23 14:18 ` Nicolas George [this message]
2024-02-23 14:52 ` Zhao Zhili
2024-02-23 16:05 ` Anton Khirnov
2024-02-23 19:36 ` Ronald S. Bultje
2024-02-26 16:33 ` Anton Khirnov
2024-02-26 18:12 ` Ronald S. Bultje
2024-02-26 19:17 ` Anton Khirnov
2024-02-26 19:48 ` Ronald S. Bultje
2024-02-26 20:02 ` Anton Khirnov
2024-02-26 20:30 ` Rémi Denis-Courmont
2024-02-26 20:44 ` Nicolas George
2024-02-20 20:50 ` Niklas Haas
2024-02-22 21:14 ` Anton Khirnov
2024-02-23 23:27 ` Michael Niedermayer
2024-02-24 11:05 ` Paul B Mahol
2024-02-26 16:52 ` Anton Khirnov
2024-02-26 22:47 ` Michael Niedermayer
2024-02-27 7:20 ` Anton Khirnov
2024-02-27 16:55 ` Michael Niedermayer
2024-03-01 16:50 ` Anton Khirnov
2024-02-20 14:01 ` Michael Niedermayer
2024-02-20 14:18 ` Rémi Denis-Courmont
2024-02-20 16:10 ` Anton Khirnov
2024-02-20 20:41 ` Michael Niedermayer
[not found] ` <3C1074B4-096B-4806-BFB0-9D491E148C48@cosmin.at>
2024-02-20 21:12 ` Cosmin Stejerean via ffmpeg-devel
2024-02-20 21:51 ` Michael Niedermayer
2024-02-22 21:54 ` Anton Khirnov
2024-02-23 14:25 ` Michael Niedermayer
2024-02-20 16:07 ` Nicolas George
2024-02-20 19:57 ` Rémi Denis-Courmont
2024-02-22 21:16 ` Anton Khirnov
2024-02-23 14:00 ` Michael Niedermayer
2024-02-23 14:15 ` Nicolas George
2024-02-23 16:07 ` Anton Khirnov
2024-03-01 17:33 ` Anton Khirnov
2024-03-02 5:37 ` Gyan Doshi
2024-03-02 19:01 ` Ronald S. Bultje
[not found] ` <3EB2D263-CAB5-4096-A061-D880D4BE95F6@cosmin.at>
2024-03-02 19:08 ` Cosmin Stejerean via ffmpeg-devel
2024-03-03 1:34 ` Michael Niedermayer
2024-03-03 7:23 ` Gyan Doshi
2024-03-03 2:49 ` Michael Niedermayer
2024-03-03 21:57 ` Anton Khirnov
2024-03-03 23:36 ` Michael Niedermayer
2024-03-03 23:56 ` Michael Niedermayer
2024-03-05 18:38 ` Niklas Haas
2024-03-05 19:02 ` Nicolas George
2024-03-04 21:15 ` Anton Khirnov
2024-03-05 2:36 ` Michael Niedermayer
2024-03-05 10:23 ` Anton Khirnov
2024-03-04 0:57 ` Michael Niedermayer
2024-03-04 9:45 ` Vittorio Giovara
2024-03-05 2:50 ` Michael Niedermayer
2024-03-05 10:27 ` Anton Khirnov
2024-03-06 23:25 ` Michael Niedermayer via ffmpeg-devel
2024-03-07 3:37 ` Zhao Zhili
2024-03-07 14:01 ` Vittorio Giovara
2024-03-08 13:16 ` Paul B Mahol
2024-03-05 12:44 ` Vittorio Giovara
2024-03-06 2:06 ` Michael Niedermayer
2024-03-22 12:52 ` Anton Khirnov
2024-03-22 13:01 ` Nicolas George
2024-03-22 13:05 ` Gyan Doshi
2024-03-25 9:41 ` Anton Khirnov
2024-03-25 12:10 ` Gyan Doshi
2024-03-25 14:49 ` Anton Khirnov
2024-03-24 2:21 ` Michael Niedermayer
2024-03-24 11:40 ` Anton Khirnov
2024-03-24 23:44 ` Michael Niedermayer
2024-03-25 9:44 ` Anton Khirnov
2024-03-26 8:20 ` Anton Khirnov
2024-03-26 22:14 ` Michael Niedermayer
2024-03-29 11:39 ` Anton Khirnov
2024-03-29 19:52 ` Michael Niedermayer
2024-04-01 11:16 ` Anton Khirnov
2024-04-01 12:20 ` Gyan Doshi
2024-04-01 13:07 ` Anton Khirnov
2024-04-01 14:59 ` Michael Niedermayer
2024-04-01 15:46 ` Paul B Mahol
2024-04-01 15:41 ` Paul B Mahol
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=ZdipHKZfOiBYIig7@phare.normalesup.org \
--to=george@nsup.org \
--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