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

[Patrick McCarty]

On 2009-08-29, Graham Percival wrote:
> On Fri, Aug 28, 2009 at 04:56:12PM -0700, Patrick McCarty wrote:
> > On 2009-08-28, Graham Percival wrote:
> > > Alternatively, we could split all those 2ly scripts (other than
> > > xml2ly) off to a separate project.  Make another of those
> > > abandoned sourceforge projects.  :)
> > 
> > Or we could just improve midi2ly...
> > 
> > This is another project I want to tackle eventually, so don't remove
> > it!  :-)
> 
> Yeah?  What about etf2ly or abc2ly?  We're still left with
> unmainted scripts, so the general problem remains.

I'm just thinking out loud here...

So it seems we have two options for the unmaintained scripts:

1) Keep them in the LilyPond source tree, hoping that someone will
improve them in the future.

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.


I don't know which approach would be better.

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.  :-)


-Patrick