Doc: CG - Updated the Meister's section

Issue 4667

Added 'Patch Meister' and
the various responsibilities
that go with the role.

Edited the existing entries
for the other three meisters
so that they are all consistently
described.

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 5420b04b05728ea772d379ea1c12f26f1bc418d6..ec8e751a032ca32bc66d3d6a8cbe1be376342b76 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -108,34 +108,108 @@ should be set to the repository lilypond-extra, see
 @node Meisters
 @section Meisters
 
-We have four jobs for organizing a team of contributors:
+We have four primary jobs to help organize all our contributors:
+
+@unnumberedsubsec The Bug Meister
+
+The Bug Meister's responsibilities are:
+
+@itemize
+
+@item
+To organize the individual Bug Squad volunteers, making sure that
+each member is aware of their responsibilities.  See
+@ref{The Bug Squad}.
+
+@item
+To train new Bug Squad volunteers in the Issue Tracker process.  See
+@ref{Issues}.
+
+@item
+To have the final say on our policies for Issues and their
+classification.  See @ref{Issue classification}.
+
+@end itemize
+
+Current Bug Meister: Colin Hall @email{bug-lilypond@@gnu.org}
+
+
+@unnumberedsubsec The Doc Meister
+
+The Doc Meister's responsibilities are:
+
+@itemize
+
+@item
+To train new volunteers in our Documentation style and policy,
+including organizing LilyPond Snippet Repository (LSR) work.
+
+@item
+To organize the individual volunteers -- who does what on which job --
+and to check that everything is running smoothly.
+
+@item
+To have final say on any Documentation policy.  See
+@ref{Documentation policy}.
+
+@end itemize
+
+Current Doc Meister: None
+
+
+@unnumberedsubsec The Patch Meister
+
+The Patch Meister's responsibilities are:
 
 @itemize
 
 @item
-Bug Meister: trains new Bug Squad volunteers, organizes who works
-on which part of their job, checks to make sure that everything is
-running smoothly, and has final say on our policy for Issues.
+To keep track of all patches submitted for testing and review.  This
+includes scanning the bug and dev email lists looking for any patches
+submitted by @q{random} contributors and advising them on how to submit
+a patch for testing and review.  See @ref{Commits and patches}.
 
-Currently: Colin H
+@item
+To makes sure that any patch submitted has a corresponding Issue Tracker
+and Rietveld Issue created for it before it enters the testing and
+review process.  See @ref{Issues}.
 
 @item
-Doc Meister: trains new doc editors/writers, organizes who works
-on which part of the job, checks to make sure that everything is
-running smoothly, and has final say on our policy for
-Documentation.  Also includes LSR work.
+Updates all Issue statuses for all patches that are currently in the
+testing and review process periodically -- currently every 3 - 4 days.
+See @ref{Patch handling}.
+
+@end itemize
 
-Currently: None
+@warning{The Patch Meister's role is a purely administrative one and no
+programming skill or judgement is assumed or required.}
+
+Currently: James Lowe @email{pkx@@gnu.org}
+
+
+@unnumberedsubsec The Translation Meister
+
+The Translation Meister's responsibilities are:
+
+@itemize
 
 @item
-Translation Meister: trains new translators, updates the
-translation priority list, and handles merging branches (in both
-directions).
+To train new documentation translators in the translation process.  See
+@ref{Translating the documentation}.
 
-Currently: Francisco
+@item
+To update the translation priority list and handle the merging of the
+translation branches (in both directions).
+
+@item
+To have final say on any Translation management policies.  See
+@ref{Translating the documentation}.
 
 @end itemize
 
+Currently: Francisco Vila @email{translations@@lilynet.net}
+
+
 
 @node Managing Staging and Master branches with Patchy
 @section Managing Staging and Master branches with Patchy