14.3 Meisters
We have four primary jobs to help organize all our contributors:
The Bug Meister
The Bug Meister’s responsibilities are:
-
To organize the individual Bug Squad volunteers, making sure that
each member is aware of their responsibilities. See
The Bug Squad.
-
To train new Bug Squad volunteers in the Issue Tracker process. See
Issues.
-
To have the final say on our policies for Issues and their
classification. See Issue classification.
Current Bug Meister: Colin Hall bug-lilypond@gnu.org
The Doc Meister
The Doc Meister’s responsibilities are:
-
To train new volunteers in our Documentation style and policy,
including organizing LilyPond Snippet Repository (LSR) work.
-
To organize the individual volunteers – who does what on which job –
and to check that everything is running smoothly.
-
To have final say on any Documentation policy. See
Documentation policy.
Current Doc Meister: None
The Patch Meister
The Patch Meister’s responsibilities are:
-
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 ‘random’ contributors and advising them on how to submit
a patch for testing and review. See Uploading a patch for review
and The patch review cycle.
-
Updates all Issue statuses for all patches that are currently in the
testing and review process periodically – currently every 3 - 4 days.
See Patch handling.
Note: The Patch Meister’s role is a purely administrative one and no
programming skill or judgement is assumed or required.
Currently: James Lowe pkx@gnu.org
The Translation Meister
The Translation Meister’s responsibilities are:
-
To train new documentation translators in the translation process. See
Translating the documentation.
-
To update the translation priority list and handle the merging of the
translation branches (in both directions).
-
To have final say on any Translation management policies. See
Translating the documentation.
Currently: Francisco Vila translations@lilynet.net
This document was generated by gub on July 13, 2020 using texi2html 1.82.