Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] clarifying the TC conflict of interest rule
Date: Tue, 20 Feb 2024 12:09:32 +0100
Message-ID: <170842737298.27417.5283452340136231344@lain.khirnov.net> (raw)
In-Reply-To: <903b92fd-f1b5-42ee-81f4-04136b3b526f@gyani.pro>

Quoting Gyan Doshi (2024-02-20 11:01:15)
> 
> 
> On 2024-02-20 02:20 pm, Anton Khirnov wrote:
> > So IMO the only case that needs to be excluded is 6) - an actual
> > conflict of interest. I therefore propose the following wording changes:
> >
> > --- a/doc/community.texi
> > +++ b/doc/community.texi
> > -If the disagreement involves a member of the TC, that member should recuse themselves from the decision.
> >
> > + 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.
> 
> 1) besides financial interest, what are some other types of 'personal 
> interest in a specific outcome of the case'?

The intent is cover all cases where a TC member has substantial
motivation that conflicts with choosing what is best for the project.

Besides money, it could be non-monetary compensation (gifts, promotions,
favors, etc.), or maybe your best friend won't speak to your for a week
if you don't vote for their preferred outcome, and so on. I'm sure
someone can think of other examples.

If you think my wording can be improved, feel welcome to suggest changes
to it, or propose an alternative one and the GA will decide.

> 2) the proposed wording says, 'they must announce it and recuse
> themselves'. That makes it seem that if a member does not self-attest
> or admit to a conflict of interest, then they cannot be stopped from
> voting. To frame it as a question, what are the independent ways (
> i.e. not including the said member) of making a conflict of interest
> determination?

My intent is that a TC member affected by a conflict of interest
* must announce it
* cannot vote
These two points hold independently, so if a TC member fails to announce
a conflict of interest that is then discovered later, then their vote is
invalid.

As for determining conflict of interest in case of dishonest TC members,
I don't think there is a general solution for it. But as I said in my
reply to Marton - we already have to assume honesty and good faith on
part of committee members, since a dishonest person could game any
proposed interpretation.

-- 
Anton Khirnov
_______________________________________________
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-20 11:09 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 [this message]
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
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=170842737298.27417.5283452340136231344@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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