It has been some time since I last reminded people that I currently work on LilyPond a contingency basis, with several community members keeping me afloat with donations.
I am not overly happy that the bulk of monetary contributions comes from people who also contribute and contributed a lot of time and energy to LilyPond. I'd prefer to have more supporters carrying less of a personal weight with my monetary support, in particular if they are already doing a lot of other things for LilyPond. What's the return of investment if you aren't just doing your part in making free software work out by keeping its cash-flow non-zero and thus not exclusively dependent on people working after-hours, something which is a problem for a large project like LilyPond? In the past months, I have made book-local variables a reality (a wish-list item for some larger projects for quite a while). That change appeared in version 2.27.3. By now I have completed my work in tackling issue #34 which leads to surprising behavior when combining grace music with parallel music. Our current issue count is somewhere in the 6000s and issue #34 has been around for more than 20 years by now while still triggering maybe 5% of typical problem cases on StackExchange and our own bug lists. Getting rid of it (made viable by previous work on LilyPond's code base that I wasn't involved with) is likely to cause a huge sigh of relief to several developers. This work is likely to appear in LilyPond version 2.27.5 (version 2.27.4 should come out any moment now). Both of those changes were of the "actually not that hard to do if you don't deal with the fallout" kind, warranting significant amounts of refactoring existing code in order to let the change actually fit in reliably. This was particularly noticeable with the book-local variable code where the actual implementation was contained in about two dozen lines of code while ironing out the problems exposed in LilyPond's use of Scheme modules took a lot of additional work. Apart from the big changes, there were various smaller ones and a more active involvement of myself in discussions and code review. I am probably not the best candidate for that, but it kind of comes with the job. At any rate: if you have not already done so, consider sending me a monthly contribution that, if nothing else, helps to keep the amounts other LilyPond developers feel obligated to send me at a polite level. I can accept payments via SEPA or Paypal, and through WISE locally in a number of countries in the native currency. Feel free to contact me per mail for payment details. Happy LilyPonding! -- David Kastrup
