Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] clarifying the TC conflict of interest rule
Date: Mon, 26 Feb 2024 23:47:20 +0100
Message-ID: <20240226224720.GW6420@pb2> (raw)
In-Reply-To: <170896637695.29002.14771451562422231612@lain.khirnov.net>


[-- Attachment #1.1: Type: text/plain, Size: 4390 bytes --]

On Mon, Feb 26, 2024 at 05:52:56PM +0100, Anton Khirnov wrote:
> Hi Michael,
> Quoting Michael Niedermayer (2024-02-24 00:27:08)
> > On Thu, Feb 22, 2024 at 10:14:20PM +0100, Anton Khirnov wrote:
> > > Quoting Niklas Haas (2024-02-20 21:50:33)
> > > > On Tue, 20 Feb 2024 09:50:33 +0100 Anton Khirnov <anton@khirnov.net> wrote:
> > > > > + Each TC member must vote on such decision according to what is, in their
> > > > > + view, best for the project. If a TC member is affected by a conflict of
> > > > > + interest with regards to the case, they must announce it and recuse
> > > > > + themselves from the TC discussion and vote. A conflict of interest is
> > > > > + presumed to occur when a TC member has a personal interest (e.g.
> > > > > + financial) in a specific outcome of the case.
> > > > 
> > > > My preferred wording would change "If a TC member is" to "If a TC member
> > > > feels they are" and "must" to "should".
> > > > 
> > > > I read it as a common sense recommendation, not a legalese text. It is
> > > > ultimately up to the individual to judge whether they are acting in good
> > > > faith or not.
> > > 
> > > Okay, that makes sense to me. I am then changing my proposal to:
> > > ------------------------------------------------------------------------
> > > Each TC member must vote on such decision according to what is, in their
> > > view, best for the project. If a TC member feels they are affected by a
> > > conflict of interest with regards to the case, they should announce it
> > > and recuse themselves from the TC discussion and vote. A conflict of
> > > interest is presumed to occur when a TC member has a personal interest
> > > (e.g. financial) in a specific outcome of the case.
> > > ------------------------------------------------------------------------
> > > 
> > > If someone wants a "stronger" version of this among the voting options,
> > > feel welcome to propose one.
> > 
> > Lets take a look at "the line"
> > 
> > "If the disagreement involves a member of the TC, that member should recuse themselves from the decision."
> > 
> > There are 3 obvious choices here:
> > 1: (unchanged) "If the disagreement involves a member of the TC, that member should recuse themselves from the decision."
> > 2: (must)      "If the disagreement involves a member of the TC, that member must   recuse themselves from the decision."
> > 3: (remove it) ""
> > 
> > Thats what the vote should be about IMO.
> > 
> > Then seperately, theres the question about the (unrelated) text you want to add
> > That too has 3 choices
> > 1. (unchanged) ""
> > 2. (should)    "conflict of interest ... they should announce it and recuse themselves ..."
> > 3. (must)      "conflict of interest ... they must   announce it and recuse themselves ..."
> > 
> > Thats what a 2nd independant vote should be _IF_ we dont already have
> > a unanimous agreement about this.
> > 
> > Now honestly why this uses a "should" after apparently
> > this very dissussion here showed that "should" is interpreted differently
> > by different people, i dont know.
> > I mean either we want people to recuse themselves or we dont if specific
> > circumstances apply. It cannot be in the per persons free choice if they
> > recuse themselves in a conflict of interrest.
> > This just makes no sense. ... Ohh i have a financial interrest in the
> > outcome, i dont have to recuse myself, i only "should" ahh ok ...
> > 
> > The "Each TC member must vote on such decision according to what is, in their view, best for the project."
> > I suspect you can just propose adding this and without any vote.
> > There may be unanimous agreement for this
> 
> I don't understand what point you are trying to make.

Look at the 3 patches i just posted.
I suspect we can move alot closer to what you suggest without a vote but
simply by consensus

And then do a vote just on what remains


> 
> Do you want to propose another alternative for the vote?

If theres something remaining that we do not agree on then yes

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Many that live deserve death. And some that die deserve life. Can you give
it to them? Then do not be too eager to deal out death in judgement. For
even the very wise cannot see all ends. -- Gandalf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2024-02-26 22:47 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
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 [this message]
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=20240226224720.GW6420@pb2 \
    --to=michael@niedermayer.cc \
    --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