1 @c -*- coding: utf-8; mode: texinfo; -*-
2 @node Administrative policies
3 @chapter Administrative policies
5 This chapter discusses miscellaneous administrative issues which
6 don't fit anywhere else.
9 * Meta-policy for this document::
14 @node Meta-policy for this document
15 @section Meta-policy for this document
17 The Contributor's Guide as a whole is still a work in progress,
18 but some chapters are much more complete than others. Chapters
19 which are @qq{almost finished} should not have major changes
20 without a discussion on @code{-devel}; in other chapters, a
21 disorganized @qq{wiki-style dump} of information is encouraged.
23 Do not change (other than spelling mistakes) without discussion:
28 @ref{Introduction to contributing}
31 @ref{Working with source code}
35 Please dump info in an appropriate @@section within these manuals,
36 but discuss any large-scale reorganization:
44 @ref{Documentation work}
50 @ref{Regression tests}
53 @ref{Programming work}
58 Totally disorganized; do whatever the mao you want:
72 @ref{Administrative policies}
81 We have four jobs for organizing a team of contributors:
86 Bug Meister: trains new Bug Squad volunteers, organizes who works
87 on which part of their job, checks to make sure that everything is
88 running smoothly, and has final say on our policy for Issues.
93 Doc Meister: trains new doc editors/writers, organizes who works
94 on which part of the job, checks to make sure that everything is
95 running smoothly, and has final say on our policy for
96 Documentation. Also includes LSR work.
101 Translation Meister: trains new translators, updates the
102 translation priority list, and handles merging branches (in both
108 Frog Meister: is responsible for code patches from (relatively)
109 inexperienced contributors. Keeps track of patches, does initial
110 reviewing of those patches, sends them to @code{-devel} when
111 they've had some initial review on the Frog list, pesters the
112 @code{-devel} community into actually reviewing said patches, and
113 finally pushes the patches once they're accepted. This person is
114 @emph{not} responsible for training new programmers, because that
115 would be far too much work -- he job is @qq{only} to guide
116 completed patches through our process.
124 @node Unsorted policies
125 @section Unsorted policies
127 @subsubheading Language-specific mailing lists
129 A translator can ask for an official lilypond-xy mailing list once
130 they've finished all @qq{priority 1} translation items.
132 @subsubheading Performing yearly copyright update (@qq{grand-replace})
134 At the start of each year, copyright notices for all source files
135 should be refreshed by running the following command from the top of
142 Internally, this invokes the script @file{scripts/@/build/@/grand@/-replace@/.py},
143 which performs a regular expression substitution for old-year -> new-year
144 wherever it finds a valid copyright notice.
146 Note that snapshots of third party files such as @file{texinfo@/.tex} should
147 not be included in the automatic update; @file{grand@/-replace@/.py} ignores these
148 files if they are listed in the variable @code{copied_files}.
151 @subsubheading Push git access
153 Git access is given out when a contributor has a significant
154 record of patches being accepted without problems. If existing
155 developers are tired of pushing patches for a contributor, we'll
156 discuss giving them push access. Unsolicited requests from
157 contributors for access will almost always be turned down.