[FFmpeg-devel] [PATCH 2/3] doc/developer: Document how disagreements should be handled

[Michael Niedermayer]

Hi Vittorio

On Tue, Nov 19, 2024 at 05:47:52PM -0500, Vittorio Giovara wrote:
> On Tue, Nov 19, 2024 at 1:55 PM Michael Niedermayer <michael at niedermayer.cc>
> wrote:
> 
> > Hi
> >
> > On Sun, Nov 17, 2024 at 11:03:35AM +0100, Anton Khirnov wrote:
> > > Quoting Michael Niedermayer (2024-11-17 01:42:20)
> > > > I think this would work better than TC or nothing process.
> > > >
> > > > Signed-off-by: Michael Niedermayer <michael at niedermayer.cc>
> > > > ---
> > > >  doc/developer.texi | 3 +++
> > > >  1 file changed, 3 insertions(+)
> > > >
> > > > diff --git a/doc/developer.texi b/doc/developer.texi
> > > > index 78053a4623a..2af71ed749a 100644
> > > > --- a/doc/developer.texi
> > > > +++ b/doc/developer.texi
> > > > @@ -937,6 +937,9 @@ The developers maintaining each part of the
> > codebase are listed in @file{MAINTAI
> > > >  Being listed in @file{MAINTAINERS}, gives one the right to have git
> > write access to
> > > >  the specific repository.
> > > >
> > > > +In actively maintained areas, the maintainer has the last word in
> > case of a technical disagreement.
> > >
> > > Strongly against.
> >
> > > It would lead to the project partitioning into walled
> > > gardens
> >
> > The term "walled garden" is not correct in this context
> > Walled garden refers to "Controlled Ecosystem", "Limited
> > Interoperability", "Dependency Lock-In", "Selective Openness"
> >
> >
> > > each with its own inconsistent set of rules.
> >
> > most would follow the same or very similar rules. I agree that some
> > outliers
> > could end with different rules. I dont think as FFmpeg grows this
> > centralized
> > TC system can function.
> > The TC
> > 1. lacks expertiese in some areas
> >
> 
> vague attacks on the TC should not be tolerated - either list and provide
> examples or don't disparage elected members of the community

every TC member knows every part of the project, every specification
every architecture, every decoder, every encoder, every filter, every demuxer
every muxer, every protocol, ...

No, as a TC member I can tell you even though i have more authored commits
in FFmpeg than the next few people combined. I do not know everything


> 
> 
> > 2. for a growing project there is a point where the TC cannot handle the
> > cases
> >    anymore at a acceptable quality
> >
> 
> you're not it, chief

The TC can handle 1 case per month, if the project doubles in size it can handle
2 cases a month.
If it doubles again, the TC can handle 4 cases a month.
Eventually the TC can handle a billion cases a second, no problem here

As the project grows, the number or maintainers grows with it. The capacity
of the TC does not grow with it.

thx

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

The bravest are surely those who have the clearest vision
of what is before them, glory and danger alike, and yet
notwithstanding go out to meet it. -- Thucydides
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20241120/3e887b58/attachment.sig>