Great to have you guys aboard! There are two lists I know of that you might find interesting. These lists are mostly about priority - identifying the most *important* issues to address. And a lot of them will probably turn out to be particularly messy, or they'd have been fixed by now. But still, there are doubtless some good candidates to be found here.
First, here is lasconic's list: http://musescore.org/en/project/issues/musescore?tag=2.0 and here is mine: http://musescore.org/en/issue-hit-list-marc-sabatella Looking over the lists, not much jumps out as all that easy for someone not already familiar with the code. But I'd think of your first bug fix as an investment. You'll probably spend way longer on it than what it might take someone else, but you'll have learned something about that part of the code, and the next bug in the same area will go easier, etc. So maybe choose based on what particular area of the code interests you the most. Marc ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
