Hi Federico,
Glen graciously added instructions on how to setup your github fork, and basic
workflow involved in maintaining existing pieces in Mutopia using github.
He also a started a document to highlight LilyPond coding practices for new
submissions to Mutopia, which enhance the maintainability moving forward.
Today, I drafted a new doc covering new submissions:
https://github.com/chrissawer/The-Mutopia-Project/wiki/Guidelines-for-new-score-submissions-using-github
Github has proven to be a great environment for code collaboration, and we
welcome contributors using pull-requests.
Javier Ruiz-Alma
On Tuesday, May 13, 2014 8:29 AM, Federico Bruni <f...@inventati.org> wrote:
I've just given a quick glance to the pull requests sent today by
>ksnortum.
>I see a lot of merge commits which are unnecessary. I don't know how
>this is sorted out when merging..
>
>I'm writing here to get some feedback on how to improve our wiki:
>https://github.com/chrissawer/The-Mutopia-Project/wiki/Setting-up-for-Contributions-via-GITHUB
>
>I usually try to avoid any merge commit in my pull requests. I think
>that it's all about rebasing instead of merging, right?
>It should be quite easy for us, I think, since we usually organize and
>book the files to be added/updated.
>
>Suggestions are welcomed.
>Thanks
>Federico
>
>_______________________________________________
>Mutopia-discuss mailing list
>Mutopia-discuss@mutopiaproject.org
>http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
>
>
>
_______________________________________________
Mutopia-discuss mailing list
Mutopia-discuss@mutopiaproject.org
http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
