Re: merging philomelos musicxml2ly-dev

[James]

On 13/07/14 13:36, Federico Bruni wrote:
> 2014-07-11 0:20 GMT+02:00 James <address@hidden
> <mailto:address@hidden>>:
>
>     I'm not sure a single tracker to 'keep track of progress' is that
>     useful
>     for the long term vs. say a tracker each time we get a fix or patch
>     submitted, I don't mind helping test/push fixes through our normal
>     processes, I just don't have the programming skills to do that - only
>     the 'admin' ones.
>
>
> I wanted to give interested users/developers a pointer to the tracker
> and let them know about philomelos...
> Another solution is using this label to mark the musicxml2ly issues:
> https://code.google.com/p/lilypond/issues/list?q=label:musicxml2ly
>
I have no preferences either way - we have done this for articulate.ly
for instance - but unless we know that philomelos and LilyPond's
versions are reasonably close to start with we could end up with each
version becoming so far apart in terms of codebase that nothing gets
fixed or that LilyPond's musicxml2ly becomes so far behind philomelos to
be worse than useless and we might as well remove musicxml2ly from the
code and just point to Philomelos.

General users just get confused (and general users don't look at tracker
issues) when they are told to use this 'other' musicxml2ly file on this
'other' website.

I don't know how much work is involved to merge the differences between
the two, but I am happy to help Patrick (and his colleagues) to get
LilyPond's version up to date, whatever it takes to do.

James