lilypond-user
[Top][All Lists]
Advanced

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

Re: Efficient transposition


From: David Kastrup
Subject: Re: Efficient transposition
Date: Tue, 31 Dec 2013 01:01:17 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Thomas Morley <address@hidden> writes:

> Hi David,
>
> 2013/12/31 David Kastrup <address@hidden>:
>> Colin Tennyson <address@hidden> writes:
>>
>>> I have created my first LilyPond file, using Frescobaldi.
>>> (LilyPond 2.18, Frescobaldi 2.0.12)
>>
>> That must be the first documented use of LilyPond 2.18.
>
> well,
> http://www.lilypondforum.de/index.php?topic=1639.msg9145#new
> :)
>
> Again, 1000 thanks for your fabulous work,

Well, let's keep the perspective: LilyPond 2.18 is the work of a large
number of volunteers, including several who have contributed
organizational work rather than code.  In numbers of commits, I might be
the single largest contributor.  But for one part that is due to me
splitting contributions into separate commits more than others, for
another, the majority of commits is done by others, and I am not
involved with every part of LilyPond.  And of course I am in the unique
position of getting paid for the work I do, enabling me to put in more
time than others.

And Mike is correct that we want and need more active contributors.
I'll try to make some proposals early next year how we may increase the
number of people willing and able to improve LilyPond.  We also need to
revise our release and branching strategies in order to maximize
quality, output, and work morale.  We also need to work on LilyPond's
architecture to avoid the situation where it is falling apart as fast as
we are adding new functionality to it.

The backend is in a particularly unhealthy state regarding the
difficulty of adding new functionality without breaking existing
functionality.  This holds for both additions made by the user in
documents and include files as well as for extensions of the core C++
code.

2.18 is not revolutionary, but it still shows several sizable steps
forwards, both in output quality as well as usability.

And if you take a look at
<URL:http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_19_0>,
it is clear that 2.19 already is off to a running start.

-- 
David Kastrup



reply via email to

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