LilyPond Contributor's Guide: 14.3 Meisters

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < Environment variables ]		[ Up : Administrative policies ]	[ > ]

14.3 Meisters

We have four primary jobs to help organize all our contributors:

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < Meisters ]		[ Up : Meisters ]	[ > ]

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

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < ]		[ Up : Meisters ]	[ > ]

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

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < ]		[ Up : Meisters ]	[ > ]

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.
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 Issues.
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

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < ]		[ Up : Meisters ]	[ Managing Staging and Master branches with Patchy > ]

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

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < ]		[ Up : Meisters ]	[ Managing Staging and Master branches with Patchy > ]