[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Manipulating instrument names and staff group names

From: Jean Abou Samra
Subject: Re: Manipulating instrument names and staff group names
Date: Wed, 3 Nov 2021 21:07:31 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.2

Le 03/11/2021 à 14:40, Kieren MacMillan a écrit :
2. I’m hoping to increase my Lilypond pay grade in the [very] near future, so 
if there’s any way I can roll up my sleeves and get involved with actual 
coding, please let me know.

Well, I would say it depends on what you intend to
do. Help out in implementing this particular feature?
The StaffCollection ancestor to StaffGroup might be
a good first contribution. For completeness you could
also add the intermediate type StaffMonoid.

Help out with LilyPond in general? There is no
shortage in tasks. One area where a beginner
can profitably spend time is the documentation.
There are loads of improvements to make there, by
completing existing material, restructuring it,
clarifying it, adding index entries where missing, ...
There is literally zero knowledge to acquire when
you are already a power user -- just look at the
surrounding material for how to write Texinfo, and
follow the cheat sheet in the Contributor's Guide
for Git usage. So take your pet peeve section and
start working. If you lack inspiration, scroll through
this list:[]=Doc

Now if what you want is really coding, there are
heaps of open issues waiting for you. Here are a
few that I believe (NB no warranty) would be feasible
for a power user with some minimal understanding of

Feel free to ask anything on the lilypond-devel
list or to me personally.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]