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: Mon, 25 Mar 2024 10:41:44 +0100
Message-ID: <171135970425.7287.9343662815036172747@lain.khirnov.net> (raw)
In-Reply-To: <31fa300f-e7dd-498a-a492-39ada91a0658@gyani.pro>

Quoting Gyan Doshi (2024-03-22 14:05:05)
> Please do post the final text and options a day in advance.

I have now created the poll, but not started it yet (the text and
options can still be edited). It looks like this:

Description:

There is disagreement about the appropriateness and interpretation of
the following sentence in Technical Committee rules
(doc/community.texi):

    If the disagreement involves a member of the TC, that member should
    recuse themselves from the decision.

(see thread starting from Message-Id
<170841737762.27417.14992162535824834057@lain.khirnov.net> for more
details)

How should this sentence be changed? Rank the options below (labeled by
the developer who proposed them) in your order of preference.

Nicolas

Any member of the TC who had a strong opinion on the question raised
before it was raised should recuse themselves.

In particular, must recuse themselves any member of the TC who:

* participated in the discussion (on the ML, on IRC or elsewhere) in a
  specific direction (minor comments and questions being acceptable);
* has a personal interest in the outcome;
* is, was recently or soon will be employed by an entity having a
  personal interest in the outcome or has any kind of hierarchical
  relationship with such entity.

Failure to do so would result, upon discovery, into the exclusion of all
FFmpeg governance bodies, including the general assembly, for a duration
of no less than five years.

Additionally, any member of the general assembly can recuse any member
of the TC without having to provide a reason.

If the application of these rules result in all members of the TC
recused or if the remaining members do not feel comfortable being too
few, that means the project is in a crisis of trust that needs to be
resolved by the general assembly.

Gyan

Any member of the TC who has

* had a major participation in the discussion or demonstrated a partisan
  disposition on the concerned issue at any public venue, or
* a material interest in the resolution of the dispute, either directly
  or via current or anticipated employment or consideration

should be recused from participation in the TC activities related to the
concerned matter. This recusal may be effected either directly by the TC
member, or failing which, by a vote of the Community Committee (CC) -
the TC member must not participate in any such vote. Failure by the TC
member to reveal any such involvement as described above, if judged
intentional and material by the CC, shall result in exclusion of said
member from all FFmpeg governance bodies for a period of no less than
two years.

Anton

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.

Michael 1

Each TC member must vote on such decision according to what is, in their
view, best for the project.

If a TC member is aware of being in 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
that differs from what is best for the project.

If the disagreement involves a member of the TC, that member must recuse
themselves from the decision.

Michael 2

Each TC member must vote on such decision according to what is, in their
view, best for the project.

If a TC member is aware of being in 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
that differs from what is best for the project.

Notes

The difference between Michael 1 and Michael 2 is only that 1 has an
extra sentence at the end (the original disputed sentence with
should→must).

The difference between Michael 2 and Anton is in the second sentence
("is aware" vs. "feels") and third sentence (Michael 2 has "that differs
from what is best for the project.") at the end.

Candidates:

The top choice will win.

* Nicolas
* Gyan
* Anton
* Michael 1
* Michael 2
* left as is
* removed without replacement

-- 
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-03-25  9:41 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
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 [this message]
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=171135970425.7287.9343662815036172747@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