[FFmpeg-devel] [PATCH] [RFC][v2] Tech Resolution Process

Ronald S. Bultje rsbultje at gmail.com
Mon Jan 18 23:36:54 EET 2021


On Mon, Jan 18, 2021 at 3:33 PM Anton Khirnov <anton at khirnov.net> wrote:

> Quoting Ronald S. Bultje (2021-01-18 21:12:50)
> > Hi,
> >
> > On Mon, Jan 18, 2021 at 2:55 PM Anton Khirnov <anton at khirnov.net> wrote:
> >
> > > I have at some point touched most major pieces of code in the project.
> > > I also have opinions on how many things should be done. So according to
> > > your definition, that makes me biased and disqualified from voting on
> > > almost anything, so there is no point in me being a TC member. Same
> > > applies to Michael.
> >
> >
> > But neither disqualifies you. TC is invoked when a specific unresolvable
> > disagreement arises between two developers. A TC member should not vote
> if
> > he is one of these two people.
> >
> > Or did you mean something else?
>
> Doesn't have to be two people. IIUC in the model situation there is a
> disagreement on the mailing list where a consensus cannot be reached. So
> potentially many people commenting. You could say that any one of them
> is "involved".


I agree "involved" should be constrained to just be one of the two parties
bringing this up to the TC. And yes this can be gamed, everything can. It's
meant to prevent extreme cases, not make the world a perfect place. We
can't do that with rules alone.

Ronald


More information about the ffmpeg-devel mailing list