10.13.3 How purity is defined and stored.10.11.6 Engraver declaration/documentation.10.11.3 Preventing garbage collection for SCM member variables.10.11.1 Useful methods for information processing.10.9.4 Automatically update documentation.10.6 Warnings, Errors, Progress and Debug Output.10.4.4 Searching on the git repository at GitLab and Savannah.7.5 Fixing snippets in LilyPond sources.Managing documentation translation with Git.Maintaining without updating translations.5.9.3 Documentation translation maintenance.Translating the Web site and other Texinfo documentation.5.9.2 Documentation translation details.5.9.1 Getting started with documentation translation.Stripping whitespace and generating menus.Building only one section of the documentation.5.7.1 Scripts to test the documentation.5.4 Texinfo introduction and usage policy.4.8 Concurrent stable and development versions.Building documentation without compiling.Documentation editor’s edit/compile cycle.4.6.1 Installing LilyPond from a local build.4.5.2 Saving time with the ‘ -j’ option.4.2.3 Requirements for building documentation.4.2.2 Requirements for compiling LilyPond.4.2.1 Requirements for running LilyPond.3.6 Further Git documentation resources.3.1.2 Cloning and forking the repository.Project administrators are Han-Wen, Jan, and Graham. Time+energy on bug fixes and new features instead of Trust+consensus for at least the next 2-3 years, and spent more

I would rather that we kept on going with I think we’re still smallĮnough, and there’s enough trust and consensus decisions, that weĬan avoid that. “core developers”, with set term limits and elections and Many projects have an official board of directors, or a list of Posted to a public mailing list, because the candidate's feelings You can't have votes about potential committers In fact, Karl Fogel’s “Producing Open Source Software”Įxplicitly suggests a private mailing list for some circumstances:īut here is one of the rare instances where secrecy isĪppropriate. The idea of private mailing lists is hardly uncommon inĮvery security team of every GNU/Linux distribution and OS Graham put an enormous amount of work into organizing and expanding a very complex project, and he has high hopes for its continued development. There is some unhappy history about this idea in our development Interested readers should consult the relevant traffic in the LilyPond mail-list archives and contact the development team (see the LilyPond Web site for contact adresses). The lilypond-hackers mailing list will be removed. Graham those three will always be CC’d on any important He will then decide who should discuss the matter on anĪd-hoc basis, and forward or CC them on future emails.įor emphasis, the project administrators are Han-Wen, Jan, and Potentially sensitive or private matters will be referred to 13.5.4.6 GOP-PROP 6 - private mailing list

Lilypond mailing list