[FFmpeg-devel] [PATCH 2/3] doc/developer: Document how disagreements should be handled
Michael Niedermayer
michael at niedermayer.cc
Tue Nov 19 20:55:24 EET 2024
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
2. for a growing project there is a point where the TC cannot handle the cases
anymore at a acceptable quality
3. Some people simple and plain disagree with being under the TC (These do leave
FFmpeg or never join)
4. The TC is slow, this latency makes development in disputed cases just painfull
A maintainer can make a decission within minutes not the days or weeks the TC
needs. Also during this time long flame threads develop on the ML
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Nations do behave wisely once they have exhausted all other alternatives.
-- Abba Eban
-------------- 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/20241119/1bbb8079/attachment.sig>
More information about the ffmpeg-devel
mailing list