Re: Issue 834 in lilypond: midi2ly broken on Windows systems

[Graham Percival]

On Fri, Aug 28, 2009 at 11:03:25PM -0700, Patrick McCarty wrote:
> On 2009-08-29, Graham Percival wrote:
> > Yeah?  What about etf2ly or abc2ly?  We're still left with
> > unmainted scripts, so the general problem remains.
> 
> 1) Keep them in the LilyPond source tree, hoping that someone will
> improve them in the future.

and possibly gaining bad press for the broken/un-optimal scripts.

> 2) Remove them from the source tree and dump them at Github,
> repo.or.cz, Sourceforge, or wherever, and hope that someone will adopt
> and improve them.

Yeah.

> Option 1) provides the convenience of having the scripts available
> with any LilyPond installation.  But if they continue to be
> unmaintained, they are likely to be unused and are wasting space.
> 
> Option 2) *might* be a better way to attract new contributors for
> these scripts.  If we want to move them to another hosting site, I
> wouldn't really mind.  I thought you were talking about eliminating
> them completely.  :-)

Also, option 2)  makes it clear that we're not responsible for
them.  I mean, if it doesn't come with lilypond, then it should be
clear that people shouldn't complain to us.

Cheers,
- Graham