Dear LilyPond afficionado,
As you might have noticed, LilyPond has been improving at a breakneck speed for the last year, which is a good thing. We hope to continue that trend by unleashing an enormous source of development potential, and that is ...
You!LilyPond already has seen an increase contributions over the past months, from packagers, bugfixers, proofreaders, etc. We love your help, and we can't have enough of it so we are seeking help. Join LilyPond development for riches, eternal fame, and getting your name in the THANKS file :-)
There are plenty of ways to get into the THANKS file, for example, by taking care of documentation, bug reports, releases, etc. We have compiled a list of tasks that we would love to be helped with. Have a look to see if there is something for you!
Many of the tasks are not very technical, so don't dismiss yourself too quickly. We have plenty of experience with these tasks, so there is always someone to guide you and get you started.
The list of tasks is not exhaustive. If you have good ideas on how to get more people involved, or how to use our energy more efficiently, don't hesitate to drop a note on the development mailing list
lilypond-devel@gnu.orgOf course, if you have an itch to scratch, you can also send patches to this mailinglist :-)
Come help us with
- release/build meister (vacancy)
- code janitor (vacancy)
- newsletter editor (vacancy)
- Implementation documenter (vacancy)
- code janitor (vacancy)
- An overview of all editing environments available.
- Feature pages for part-combining/auto-cue notes, tweaking, and other nice features of LilyPond.