2013/4/10 Fan Ziye <fanzi...@gmail.com>: > 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 _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
