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

[Michael Niedermayer <michael@niedermayer.cc>]

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

Hi

On Fri, Mar 01, 2024 at 06:33:12PM +0100, Anton Khirnov wrote:
> Hi all,
> it seems the discussion died down,

There are patches pending, which i will apply soon if no objections
have been raised.

And noone owns law texts. Everyone can propose any derivation
of anothers suggestion. Thats the idea behind evolution and improvment
and the idea behind finding and dicussing variations.

Depending on these patches outcome, i may propose options here

That certainly does not qualify as "discussion died down"

But as a precaution for the strange style of "quick vote before we
find a consensus"

Please add the vote options: (I belive this gives the people a more
complete set of choices)

* Wait for the discussion, consensus and patch based process to finish.
  After which, if disagreements remain, use the GA vote process.

* Add a conflict of interrest text as specified by the patch below

* Replace "If the disagreement involves a member of the TC, that member should recuse themselves from the decision."
  by the conflict of interrest text as specified by the patch below

* Replace "If the disagreement involves a member of the TC, that member should recuse themselves from the decision." by
          "If the disagreement involves a member of the TC, that member must recuse themselves from the decision."
  and add the conflict of interrest text as specified by the patch below

* Replace "If the disagreement involves a member of the TC, that member should recuse themselves from the decision." by
          "If the disagreement involves a member of the TC, that member must recuse themselves from the decision."

(if the patch doesnt apply use best effort to merge manually)
--- a/doc/community.texi
+++ b/doc/community.texi
@@ -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 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.


As you can see we have so many options to consider, its better if we first
go through normal discussions and consensus finding instead of initiating a vote
while patches are pending on the very text the vote is about

thx

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

Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.

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