2012/2/10 David Kastrup <address@hidden>: >* Don't get me wrong: it is probably quite enough work for getting someone* >* started. I'm just not sure whether it will be easy to sell it off. The* >* largest part of the work would realistically consist in digging oneself* >* into sparsely documented areas, just in order to be able to come up with* >* a good plan and implementation that would, if you discounted all dead* >* corners, take two days to do.* >** >* It seems a bit like visiting a term of art classes in order to make a* >* convincing sketch at its end. The real deal is not the sketch, but the* >* ability to do so. And if all you are going to do is that one sketch,* >* the exercise seems a bit pointless.* >** >* But of course, if you want to turn sketches into a living, having* >* someone pay what it takes to do the first sketch is going to be a _big_* >* help.*
Like Janek, I'm also thinking of participating in GSoC. If one of us works on that bug during GSoC and moreover while coding also adds some documentation to the poorly commented code, this will result in far more than "one sketch", because we will stay connected with Lilypond after the end of GSoC 2012. If you think that Issue #34 is too little for GSoC, you could add to that some other similar issues with MIDI or grace notes in a form similar to: http://community.kde.org/GSoC/2011/Ideas#Project:_KStars:_Improve_the_observation_planner_and_logging_feature Best wishes, Łukasz
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
