[FFmpeg-cvslog] doc/developer: Document relationship between git accounts and MAINTAINERS

[Michael Niedermayer]

ffmpeg | branch: master | Michael Niedermayer <michael at niedermayer.cc> | Sat Nov 16 21:32:53 2024 +0100| [7051825b0171bd5d566c5a5cc78852c5f3aa3072] | committer: Michael Niedermayer

doc/developer: Document relationship between git accounts and MAINTAINERS

This should have been documented long ago and i thought it was

Signed-off-by: Michael Niedermayer <michael at niedermayer.cc>

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=7051825b0171bd5d566c5a5cc78852c5f3aa3072
---

 doc/developer.texi | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/developer.texi b/doc/developer.texi
index ff181abb58..78053a4623 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -927,6 +927,25 @@ In case you need finer control over how valgrind is invoked, use the
 @code{--target-exec='valgrind <your_custom_valgrind_options>} option in
 your configure line instead.
 
+ at anchor{Maintenance}
+ at chapter Maintenance process
+
+ at anchor{MAINTAINERS}
+ at section MAINTAINERS
+
+The developers maintaining each part of the codebase are listed in @file{MAINTAINERS}.
+Being listed in @file{MAINTAINERS}, gives one the right to have git write access to
+the specific repository.
+
+ at anchor{Becoming a maintainer}
+ at section Becoming a maintainer
+
+People add themselves to @file{MAINTAINERS} by sending a patch like any other code
+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{Release process}
 @chapter Release process