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::
12 * Administrative mailing list::
15 @node Meta-policy for this document
16 @section Meta-policy for this document
18 The Contributor's Guide as a whole is still a work in progress,
19 but some chapters are much more complete than others. Chapters
20 which are @qq{almost finished} should not have major changes
21 without a discussion on @code{-devel}; in other chapters, a
22 disorganized @qq{wiki-style dump} of information is encouraged.
24 Do not change (other than spelling mistakes) without discussion:
29 @ref{Introduction to contributing}
32 @ref{Working with source code}
36 Please dump info in an appropriate @@section within these manuals,
37 but discuss any large-scale reorganization:
45 @ref{Documentation work}
51 @ref{Regression tests}
54 @ref{Programming work}
59 Totally disorganized; do whatever the mao you want:
73 @ref{Administrative policies}
82 We have four jobs for organizing a team of contributors:
87 Bug Meister: trains new Bug Squad volunteers, organizes who works
88 on which part of their job, checks to make sure that everything is
89 running smoothly, and has final say on our policy for Issues.
94 Doc Meister: trains new doc editors/writers, organizes who works
95 on which part of the job, checks to make sure that everything is
96 running smoothly, and has final say on our policy for
97 Documentation. Also includes LSR work.
102 Translation Meister: trains new translators, updates the
103 translation priority list, and handles merging branches (in both
109 Frog Meister: is responsible for code patches from (relatively)
110 inexperienced contributors. Keeps track of patches, does initial
111 reviewing of those patches, sends them to @code{-devel} when
112 they've had some initial review on the Frog list, pesters the
113 @code{-devel} community into actually reviewing said patches, and
114 finally pushes the patches once they're accepted. This person is
115 @emph{not} responsible for training new programmers, because that
116 would be far too much work -- he job is @qq{only} to guide
117 completed patches through our process.
125 @node Unsorted policies
126 @section Unsorted policies
128 @subsubheading Language-specific mailing lists
130 A translator can ask for an official lilypond-xy mailing list once
131 they've finished all @qq{priority 1} translation items.
133 @subsubheading Performing yearly copyright update (@qq{grand-replace})
135 At the start of each year, copyright notices for all source files
136 should be refreshed by running the following command from the top of
143 Internally, this invokes the script @file{scripts/@/build/@/grand@/-replace@/.py},
144 which performs a regular expression substitution for old-year -> new-year
145 wherever it finds a valid copyright notice.
147 Note that snapshots of third party files such as @file{texinfo@/.tex} should
148 not be included in the automatic update; @file{grand@/-replace@/.py} ignores these
149 files if they are listed in the variable @code{copied_files}.
152 @subsubheading Push git access
154 Git access is given out when a contributor has a significant
155 record of patches being accepted without problems. If existing
156 developers are tired of pushing patches for a contributor, we'll
157 discuss giving them push access. Unsolicited requests from
158 contributors for access will almost always be turned down.
160 @node Administrative mailing list
161 @section Administrative mailing list
163 An mailing list for administrative issues is maintained at
164 @code{lilypond-hackers@@gnu.org}.
166 This list is intended to be used for discussions that should be kept
167 private. Therefore, the archives are closed to the public.
169 Subscription to this list is limited to certain senior developers.
171 At the present time, the list is dormant.
173 Details about the criteria for membership, the types of discussion
174 to take place on the list, and other policies for the hackers list
175 will be finalized during the LilyPond Grand Organization Project,
176 scheduled to begin shortly after the release of LilyPond version