[FFmpeg-devel] [PATCH 3/3] doc/developer: Duties of a maintainer

Vittorio Giovara vittorio.giovara at gmail.com
Tue Nov 19 18:30:03 EET 2024


On Sat, Nov 16, 2024 at 7:42 PM Michael Niedermayer <michael at niedermayer.cc>
wrote:

> Not sure we have such a list elsewhere, i failed to find it
>
> Signed-off-by: Michael Niedermayer <michael at niedermayer.cc>
> ---
>  doc/developer.texi | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>
> diff --git a/doc/developer.texi b/doc/developer.texi
> index 2af71ed749a..3a942b19627 100644
> --- a/doc/developer.texi
> +++ b/doc/developer.texi
> @@ -948,6 +948,23 @@ change. These get reviewed by the community like any
> other patch. It is expected
>  that, if someone has an objection to a new maintainer, she is willing to
> object
>  in public with her full name and is willing to take over maintainership
> for the area.
>
> + at anchor{Duties of a maintainer}
> + at section Duties of a maintainer
> +
> +A maintainer should review and apply/reject patches submited to her/his
> code.
>

their code


> +A maintainer should fix regressions.
> +A maintainer should fix security issues.
> +A maintainer should awnser questions which hold up other developers in the
> +maintained area as far as awnsers are known.
> +A maintainer should make sure his details in the MAINTAINERS file are
> accurate
> +that includes a way to contact as well as updating his/her entry if he
> stops
> +maintaining the area
>

why?

+"should" above is meant in a way that a maintainer may occasionally be
> unable to do
> +some item and thats ok. Its also ok if a maintainer leaves these tasks to
> others.
> +Or to require to be reminded. But its expected that a maintainer does
> whatever is
> +needed to get most of these things done eventually.
>

this feels like a lot of work for a volunteer position
-- 
Vittorio


More information about the ffmpeg-devel mailing list