[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Wanting to be involved in lilypond project again
From: |
Fan Ziye |
Subject: |
RE: Wanting to be involved in lilypond project again |
Date: |
Fri, 12 Apr 2013 14:57:28 +0800 |
Thank you very much!
Now I am reading the link in your reply, but I'm a little confused -- I don't
know how the issue system and code review system run. I'm reading related parts
in CG again.
Besides, there is a problem when I try to build lilypond,
1. texinfo-5 causes a build failure of lilypond, texinfo-4.13 is okay.
2. When building documentation, it reports an error: Error in `gs':
free(): invalid pointer: 0x0980e978, and then several memory map. I tried to
use ghostscript-8.60 but nothing changed. Is that a compatibility issue with
libc?
Thanks,
Fan Ziye
-----Original Message-----
From: Janek Warchoł [mailto:address@hidden
Sent: Wednesday, April 10, 2013 10:34 PM
To: Fan Ziye
Cc: LilyPond Developmet Team
Subject: Re: Wanting to be involved in lilypond project again
2013/4/10 Fan Ziye <address@hidden>:
> Dear list,
>
> Hi, I introduced myself to you several weeks ago – a fourth-year
> undergraduate student of EECS wanting to be involved in lilypond’s
> developing. And then Mike told me to read the CG. (Thank you very much!).
>
> But sorry for my absence in recent time, I was busy with my graduate
> project. Luckily my project is about to be finished now, so I want to
> come back and find something I can do.
>
> I have just read through the CG and set up my developing environment (
> archlinux in a virtualbox, lily-git ). Is there any bug that would be
> instructive to start with? Thanks! J
That's great, and welcome back!
I suggest you to start by reviewing some of currently discussed patches
http://code.google.com/p/lilypond/issues/list?can=2&q=patch%3Dcountdown%2Creview
This may sound surprising, but i think reviewing patches can be a good way to
learn lilypond codebase. You can find a link to a codereview issue
(http://codereview.appspot.com/*) inside each tracker issue; find an issue that
seems not very complicated and read the code it's related to. If you don't
understand what the patch is doing after reading it twice, it's quite probable
that the description and/or comments are not detailed enough - it's perfectly
ok to ask questions!
Even if they may sound silly.
As for bugs, i think that one of these three would be a reasonable starting
point - just so that you'll get familiar with the system.
We'll get to more interesting things after that.
http://code.google.com/p/lilypond/issues/detail?id=1367
http://code.google.com/p/lilypond/issues/detail?id=1749
http://code.google.com/p/lilypond/issues/detail?id=1462
hth,
janek