Le sunnuntaina 17. marraskuuta 2024, 2.42.20 EET Michael Niedermayer a écrit :
> I think this would work better than TC or nothing process.
>
> Signed-off-by: Michael Niedermayer <mich...@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. +In all other cases, the technical committee has
> the last word in case of a technical disagreement.
> +
It can't work that way. We don't have an objective metric of where one area
stops and another's start. This is particularly obvious for horizontal areas
such as ISAs, OSes, build system and testing which overlap with many different
vertical areas like formats, codecs and protocols. And we can also have
disagreements between multiple maintainers of single area.
Even if we did have clear objective boundaries, disagreements can also overlap
different areas or concern intrinsically project-wide technical policies.
--
レミ・デニ-クールモン
http://www.remlab.net/
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
