Re: building from source

[Urs Liska]

Hi Daniel,

we don't have a formal mentorship program. This was intended but AFAICS
this never really worked out. So it seems the CG should be cleaned up in
this respect. The "mentoring" you'll receive is from this mailing list.

If you have reached the state where you can build LilyPond and create
some improvement you're ready to start, I think.

What you *can* do is ask on this list whether your perception of a
possible patch is viable (actually that's what you just did). And if
noone objects you should upload a patch for review - and that's what you
should concentrate on next in the CG.

You will need a SourceForge account and should communicate your user
name, so someone can add you to the issue tracker project. This is
needed for successfully going through the upload process with git-cl.

If your patch is good and reaches (maybe after some iterations) the
"push" status you will have to ask someone (again, here on this list) to
push the patch on your behalf. After a number of successful patches you
can ask for getting push access on the LilyPond repository itself.

HTH
Urs

Am 26.03.2016 um 20:49 schrieb Daniel Birns:
> 1) I have a good build, have made a trivial modification, and it seems to 
> work. (I found a class (Midi-duration) that’s unused. I commented it out, and 
> everything builds fine. Since there’s no references to it, I presume the 
> testsuites will be unaffected, though you never know...
> 2) I’m reading ‘contributor.pdf’. It says I will be assigned a mentor. That’s 
> fine with me either way, but I’m curious if perhaps there’s some formal route 
> I should go through at this point.
> 3) My plan is to work via the C++ files and improve the midi output. I see 
> several .cc files with midi in their name and I think 4 header files with 
> midi in the name. 
> 
> So, at this point, I could use some advice about 1) where to focus in the 
> contributor.pdf, and 2) some idea of the architecture, particularly with 
> regard to midi processing. Of course, I could try to figure that out myself, 
> but that doesn’t seem like the right approach.
> 
> The first thing I need to do is understand what’s going on today before I 
> muck with anything.
> 
> -d
> 
>> On Mar 26, 2016, at 8:54 AM, Carl Sorensen <address@hidden> wrote:
>>
>> On 3/26/16 9:49 AM, "address@hidden on
>> behalf of Daniel Birns" <address@hidden
>> on behalf of address@hidden> wrote:
>>
>>> What is LilyDev?
>>
>> http://www.lilypond.org/doc/v2.19/Documentation/contributor/lilydev
>>
>>
>> A Debian iso ready-to-go for doing LilyPond development.
>>
>> I used to maintain a usable lilypond development site on OS X.  New
>> updates to OS X invariably broke the site and required hours or days of
>> fixing things.  LilyDev in a VirtualBox VM always works, and works easily.
>>
>> I would really recommend using LilyDev in a VM.
>>
>> Carl
>>
> 
> 
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
> 


-- 
Urs Liska
www.openlilylib.org