| [Top][Contents][Index][ ? ] |
Table of Contents
- 1. Introduction to contributing
- 2. Quick start
- 3. Working with source code
- 3.1 Manually installing lily-git.tcl
- 3.2 Starting with Git
- 3.3 Basic Git procedures
- 3.4 Advanced Git procedures
- 3.4.1 Merge conflicts
- 3.4.2 Advanced Git concepts
- 3.4.3 Resolving conflicts
- 3.4.4 Reverting all local changes
- 3.4.5 Working with remote branches
- 3.4.6 Git log
- 3.4.7 Applying remote patches
- 3.4.8 Sending and receiving patches via email
- 3.4.9 Cleaning up multiple patches
- 3.4.10 Commit access
- 3.4.11 Pushing to staging
- 3.5 Git on Windows
- 3.5.1 Background to nomenclature
- 3.5.2 Installing git
- 3.5.3 Initialising Git
- 3.5.4 Git GUI
- 3.5.5 Personalising your local git repository
- 3.5.6 Checking out a branch
- 3.5.7 Updating files from ‘remote/origin/master’
- 3.5.8 Editing files
- 3.5.9 Sending changes to ‘remotes/origin/master’
- 3.5.10 Resolving merge conflicts
- 3.5.11 Other actions
- 3.6 Repository directory structure
- 3.7 Other Git documentation
- 4. Compiling
- 4.1 Overview of compiling
- 4.2 Requirements
- 4.3 Getting the source code
- 4.4 Configuring
make - 4.5 Compiling LilyPond
- 4.6 Post-compilation options
- 4.7 Problems
- 4.8 Concurrent stable and development versions
- 4.9 Build system
- 5. Documentation work
- 5.1 Introduction to documentation work
- 5.2 Documentation suggestions
- 5.3 Texinfo introduction and usage policy
- 5.4 Documentation policy
- 5.5 Tips for writing docs
- 5.6 Scripts to ease doc work
- 5.7 Docstrings in scheme
- 5.8 Translating the documentation
- 6. Website work
- 7. LSR work
- 8. Issues
- 9. Regression tests
- 10. Programming work
- 10.1 Overview of LilyPond architecture
- 10.2 LilyPond programming languages
- 10.3 Programming without compiling
- 10.4 Finding functions
- 10.5 Code style
- 10.6 Warnings, Errors, Progress and Debug Output
- 10.7 Debugging LilyPond
- 10.8 Tracing object relationships
- 10.9 Adding or modifying features
- 10.9.1 Write the code
- 10.9.2 Write regression tests
- 10.9.3 Write convert-ly rule
- 10.9.4 Automatically update documentation
- 10.9.5 Manually update documentation
- 10.9.6 Edit changes.tely
- 10.9.7 Verify successful build
- 10.9.8 Verify regression tests
- 10.9.9 Post patch for comments
- 10.9.10 Push patch
- 10.9.11 Closing the issues
- 10.10 Iterator tutorial
- 10.11 Engraver tutorial
- 10.12 Callback tutorial
- 10.13 Understanding pure properties
- 10.14 LilyPond scoping
- 10.15 Scheme->C interface
- 10.16 LilyPond miscellany
- 11. Release work
- 12. Build system notes
- 13. Modifying the feta font
- 14. Administrative policies
- 14.1 Meta-policy for this document
- 14.2 Environment variables
- 14.3 Meisters
- 14.4 Patchy
- 14.5 Administrative mailing list
- 14.6 Grand Organization Project (GOP)
- 14.6.1 Motivation
- 14.6.2 Ongoing jobs
- 14.6.3 Policy decisions
- 14.6.4 Policy decisions (finished)
- 14.6.4.1 GOP-PROP 1 - python formatting
- 14.6.4.2 GOP-PROP 2 - mentors and frogs
- 14.6.4.3 GOP-PROP 3 - C++ formatting
- 14.6.4.4 GOP-PROP 4 - lessons from 2.14
- 14.6.4.5 GOP-PROP 5 - build system output (not accepted)
- 14.6.4.6 GOP-PROP 6 - private mailing list
- 14.6.4.7 GOP-PROP 7 - developers as resources
- 14.6.4.8 GOP-PROP 8 - issue priorities
- 14.6.4.9 GOP-PROP 9 - behavior of make doc
- 14.7 Grand LilyPond Input Syntax Standardization (GLISS)
- 14.8 Unsorted policies
- A. LilyPond grammar
- B. GNU Free Documentation License
| [Top][Contents][Index][ ? ] |