Hi, in the meantime i saw Graham's email, so just a short reply:
2013/9/16 David Kastrup <d...@gnu.org>: > [github] can cause tool lock-in and so on, every tool can. In this case, i think that the degree of lock-in is small and probably negligible (as Graham said, git repositories are portable). Note that i'm *not* proposing to move LilyPond development to Github. I just want to organize stuff that's already there, and give LilyPond wide exposure by hosting a "semi-official" repository clone there. > With Savannah, we have system > administrators sympathetic to our cause rather than their business > model. And the LilyPond project is quite beyond a "don't care" size for > them. That's good, and i'm not saying that we should abandon Savannah! I want LilyPond to be present on Github because it's a very widely known platform (according to Wikipedia, it's two orders of magnitude more popular than Savannah: http://en.wikipedia.org/wiki/Comparison_of_open-source_software_hosting_facilities#Popularity). Together with ease of use mentioned by Graham this can result in more contributors joining Lily development. best, Janek _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
