Hi
On Tue, Nov 19, 2024 at 11:30:03AM -0500, Vittorio Giovara wrote:
> On Sat, Nov 16, 2024 at 7:42 PM Michael Niedermayer <mich...@niedermayer.cc>
> wrote:
>
> > Not sure we have such a list elsewhere, i failed to find it
> >
> > Signed-off-by: Michael Niedermayer <mich...@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.
> >
> > +@anchor{Duties of a maintainer}
> > +@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 positionWhat list of "duties"/"rights" would you suggest for maintainers ? thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Awnsering whenever a program halts or runs forever is On a turing machine, in general impossible (turings halting problem). On any real computer, always possible as a real computer has a finite number of states N, and will either halt in less than N cycles or never halt.
signature.asc
Description: PGP signature
_______________________________________________ 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".
