Hi Jaap
I've added de-wolff to Sourceforge with Developer permissions. You may
now update and create Issues as well as reading them.
Next step is to initiate discussion about your patch under Issue 665 at
Sourceforge, and upload a patch as a proposal to Rietveld for a code
review. Instructions for doing this are in the Contributor's Guide
http://lilypond.org/doc/v2.19/Documentation/contributor/quick-start .
I see the patch would be quite large, so a code review will be
difficult. I'll leave it to the experienced code developers to take it
from here.
Thanks for working on this - hope it all goes well!
Trevor
------ Original Message ------
From: [email protected]
To: "'Trevor'" <[email protected]>
Sent: 16/11/2019 16:53:36
Subject: RE: Working on issue 665, how to proceed?
I already have an sourceforge account: my username is de-wolff
Jaap
-----Original Message-----
From: Trevor <[email protected]>
Sent: Saturday, November 16, 2019 3:44 PM
To: [email protected]; [email protected]
Subject: Re: Working on issue 665, how to proceed?
[email protected] wrote 15/11/2019 23:31:33
Subject: Working on issue 665, how to proceed?
Hi Jaap
You wrote
>In the last weeks I did write a start of a lilypond -> musicxml solution.
>
>As this is an (old) issue, there is need to put this in lilypond, but how?
>What level of quality is needed? Who can help me to join the lilypond
>developer group?
The first step is to obtain a username at sourceforge.net and post it to the -
devel list so we can add you as a Developer. Then you'll be able to add your
comments and code to Issue 665.
Trevor
