| Message ID | 20240226224438.1793-2-michael@niedermayer.cc |
|---|---|
| State | New |
| Headers | show |
| Series | [FFmpeg-devel,1/3] doc/community: Vote in the interest of the project (first part of Antons proposal) | expand |
| Context | Check | Description |
|---|---|---|
| yinshiyou/make_loongarch64 | success | Make finished |
| yinshiyou/make_fate_loongarch64 | success | Make fate finished |
| andriy/make_x86 | success | Make finished |
| andriy/make_fate_x86 | success | Make fate finished |
Le tiistaina 27. helmikuuta 2024, 0.44.37 EET Michael Niedermayer a écrit : > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > --- > doc/community.texi | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/doc/community.texi b/doc/community.texi > index 8a38c6aca0..fc22a8fa61 100644 > --- a/doc/community.texi > +++ b/doc/community.texi > @@ -84,6 +84,9 @@ If the TC thinks it needs the input from the larger > community, the TC can call f > > 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. It looks like the meaning and intent do not match up here. I would expect something like either of: * 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. * If a TC member is aware of a conflict of interest with regards to the case, they must announce it and the conflicted TC member(s) must recuse themselves from the TC discussion and vote. But either way this leaves open what you do if somebody outside the TC asserts a conflict of interest against a TC member, or worse, if a conflict of interest is asserted post-facto. So in the end, while this rule seems well-meaning and agreeable, I don't see how you can avoid having conflicted TC member vote. Consequently, this should be a strong recommendation rather than a strict rule. Again, the effective way to work-around this problem is to keep a large and diverse enough TC membership to offset the one or few hypothetical dishonest votes.
On Sun, Mar 03, 2024 at 10:19:03AM +0200, Rémi Denis-Courmont wrote: > Le tiistaina 27. helmikuuta 2024, 0.44.37 EET Michael Niedermayer a écrit : > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > > --- > > doc/community.texi | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/doc/community.texi b/doc/community.texi > > index 8a38c6aca0..fc22a8fa61 100644 > > --- a/doc/community.texi > > +++ b/doc/community.texi > > @@ -84,6 +84,9 @@ If the TC thinks it needs the input from the larger > > community, the TC can call f > > > > 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. > > It looks like the meaning and intent do not match up here. I would expect > something like either of: > > * 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. This was the intended meaning, i will update my patch [...] > Again, the effective way to work-around this problem is to keep a large and > diverse enough TC membership to offset the one or few hypothetical dishonest > votes. This doesnt work. The set of people is very specific, and they will always be representatives of the community so when 60% of the community works for companies which would benefit by FFmpeg not competing. There would be no realistic way to have a committee that wasnt also 60% affected by this. And for this we need a clear rule. thx [...]
On Mon, Mar 4, 2024 at 1:46 AM Michael Niedermayer <michael@niedermayer.cc> wrote: > > Again, the effective way to work-around this problem is to keep a large > and > > diverse enough TC membership to offset the one or few hypothetical > dishonest > > votes. > > This doesnt work. The set of people is very specific, and they will always > be > representatives of the community so when 60% of the community works for > companies which would benefit by FFmpeg not competing. There > would be no realistic way to have a committee that wasnt also 60% affected > by this. And for this we need a clear rule. > This scenario is, also, not realistic.
On Mon, Mar 04, 2024 at 10:42:02AM +0100, Vittorio Giovara wrote: > On Mon, Mar 4, 2024 at 1:46 AM Michael Niedermayer <michael@niedermayer.cc> > wrote: > > > > Again, the effective way to work-around this problem is to keep a large > > and > > > diverse enough TC membership to offset the one or few hypothetical > > dishonest > > > votes. > > > > This doesnt work. The set of people is very specific, and they will always > > be > > representatives of the community so when 60% of the community works for > > companies which would benefit by FFmpeg not competing. There > > would be no realistic way to have a committee that wasnt also 60% affected > > by this. And for this we need a clear rule. > > > > This scenario is, also, not realistic. that may or may not be, but rules cannot be applied at the discretion of the person who has a conflicting interrest against FFmpeg thx [...]
diff --git a/doc/community.texi b/doc/community.texi index 8a38c6aca0..fc22a8fa61 100644 --- a/doc/community.texi +++ b/doc/community.texi @@ -84,6 +84,9 @@ If the TC thinks it needs the input from the larger community, the TC can call f 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. + 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.
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> --- doc/community.texi | 3 +++ 1 file changed, 3 insertions(+)