| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ GNU Free Documentation License >> ] | ||
| [ < Meta-policy for this document ] | [ Up : Administrative policies ] | [ Patchy > ] | ||
14.2 Meisters
We have four jobs for organizing a team of contributors:
-
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.
Currently: Phil
-
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.
Currently: Graham
-
Translation Meister: trains new translators, updates the
translation priority list, and handles merging branches (in both
directions).
Currently: Francisco
-
Frog Meister: is responsible for code patches from (relatively)
inexperienced contributors. Keeps track of patches, does initial
reviewing of those patches, sends them to
-develwhen they’ve had some initial review on the Frog list, pesters the-develcommunity into actually reviewing said patches, and finally pushes the patches once they’re accepted. This person is not responsible for training new programmers, because that would be far too much work – his/her job is “only” to guide completed patches through our process.Currently: Carl
| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ GNU Free Documentation License >> ] | ||
| [ < Meta-policy for this document ] | [ Up : Administrative policies ] | [ Patchy > ] | ||