Re: [FFmpeg-devel] [RFC] clarifying the TC conflict of interest rule

[Michael Niedermayer <michael@niedermayer.cc>]

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

On Fri, Mar 22, 2024 at 01:52:55PM +0100, Anton Khirnov wrote:
> Michael,

> following up on the previous discussion in this thread - if you,
> personally, would like to vote for a different option than those
> suggested so far, please propose one.

The goal of the vote is to find the option which most people prefer.
Not the option that I personally prefer.
The winning options often are compromises that noone has as their
favorite but the team as a whole prefers.

You also added 3 options yourself, which i presume you dont all
intend to vote for yourself


> I am not going to add a large number of options that nobody actually
> wants to vote for, as it imposes a burden on the voters who have to
> carefully read and compare all the options.

The intend of the vote here is to resolve a disagreement we have.

Simply omiting opposing options is not how Democracy works

You could discuss with others and try to find a smaller set of options
that still represent all cases the team may want.

I think the 2 main cases from the ones proposed by me are:
(that is just my feeling and i cant read peoples minds and there may be
 other preferrances that should be represented)


@@ -82,6 +82,14 @@ The TC has 2 modes of operation: a RFC one and an internal one.

 If the TC thinks it needs the input from the larger community, the TC can call for a RFC. Else, it can decide by itself.

+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.
-If the disagreement involves a member of the TC, that member should recuse themselves from the decision.

 The decision to use a RFC process or an internal discussion is a discretionary decision of the TC.



@@ -82,6 +82,13 @@ The TC has 2 modes of operation: a RFC one and an internal one.

 If the TC thinks it needs the input from the larger community, the TC can call for a RFC. Else, it can decide by itself.

+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 should recuse themselves from the decision.

 The decision to use a RFC process or an internal discussion is a discretionary decision of the TC.


thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

it is not once nor twice but times without number that the same ideas make
their appearance in the world. -- Aristotle

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