Re: maintaining advanced power-user Scheme functions

[David Kastrup]

"Phil Holmes" <address@hidden> writes:

> ----- Original Message ----- 
> From: "Janek Warchoł" <address@hidden>
> To: "Thomas Morley" <address@hidden>
> Cc: "lilypond-user" <address@hidden>; "Phil Hézaine"
> <address@hidden>; "David Nalesnik"
> <address@hidden>; "LilyPond Developmet Team"
> <address@hidden>
> Sent: Sunday, August 18, 2013 9:46 PM
> Subject: Re: maintaining advanced power-user Scheme functions
>
>
>> After some thinking, i came to the conclusion that LSR should be
>> redesigned.
>> Fristly, it should be a git repository, to make collaboration easy -
>> when something's a git repository, i have a habit of contributing
>> stuff there on every opportunity, because even if i do something wrong
>> i can undo this.
>
> I'd guess you're in a minority of about 1% of users who would prefer
> using git to using a web interface.  The current web interface allows
> you to copy-and-paste code directly in, or alternatively to type it
> directly in. Both are simple and quick.  To use git propoerly requires
> installing a new program and learning how to use it.  Remember
> yesterday when you recommended a whole book about how it's used?  If
> that doesn't put off casual contributors, nothing will.  I started
> work on LilyPond by adding regtests to the LSR.  If git had been
> required, I wouldn't have done so.

Well, one question may be whether git could be an alternate interface
into the LSR.  In a limited manner, it already is (snippets migrate back
from LilyPond git repository into the LSR).

There is the fundamental problem that snippets differ for different
versions of LilyPond.  But there is also the more fundamental problem of
snippets that are improved over time.  It's not really necessary to
access worse version of snippets, but it might be necessary to access
versions of snippets suitable for different versions of LilyPond.  Using
git for managing snippets corresponding to different versions of
LilyPond is likely a tool mismatch.  git is more slated for maintaining
a development of improvements.

-- 
David Kastrup