LilyPond Contributor's Guide: proposed revised structure 1. Introduction to LilyPond development 2. Obtaining a LilyPond repository 2.1 Starting with Git 2.1.1 Installing Git 2.1.2 Initializing a repository 2.1.3 Configuring Git * Global settings (1.1.2) * Repository settings 2.2 Initializing Git branches 2.2.1 LilyPond repository sources (1.1.6) 2.2.2 The `master' branch (1.1.3) 2.2.3 The `lilypond/translation' branch (1.1.4) 2.2.4 Other branches (1.1.5) 3. Developing without compiling 3.1 Basic procedures 3.1.1 Staying current * Pulling (1.2.1, .2) * Resolving conflicts (1.2.3) 3.1.2 Working with branches (1.4.2) * Creating and removing branches * Listing branches * Checking out branches * Merging branches 3.1.3 Modifying source files * Making commits * Formatting patches (1.3.1) 3.2 Advanced procedures 3.2.1 Working with remote branches (1.4.3) 3.2.2 Git log (1.4.4) 3.2.3 Applying remote patches (1.4.5) 3.2.4 Pushing to git.sv.gnu.org (1.3.2) 3.3 Git on Windows 3.4 Repository directory structure (1.7) 3.5 Other Git documentation (1.6) 4. Compiling 4.1 Installing build dependencies (2.1.2) 4.1.1 Using `build-dep' 4.1.2 Requirements for compiling LilyPond 4.1.3 Requirements for running LilyPond 4.1.4 Requirements for building documentation 4.2 Configuring `make' 4.2.1 Creating generated files (2.1.1) 4.2.1 Running ./configure (2.1.3) * Configuring target directories * Configuring for multiple platforms 4.3 Compiling LilyPond 4.3.1 Using make (2.1.3) 4.4 Tasks requiring a successful compile 4.4.1 Installing LilyPond (2.1.3) 4.4.2 Generating documentation (2.1.4) * Building documentation * Installing documentation * Building documentation without compiling 4.4.3 Testing LilyPond (2.1.5) 4.5 Concurrent Stable and Development Versions (2.2) 4.5 Compiling on Windows (2.3) 5. Documentation work (3) 6. Website work (4) 7. LSR work (5) 8. Issues (6) 9. Regression tests (7) 10. Programming work (8) 11. Release work (9) A. GNU Free Documentation License (A)