[MEI-L] Github considerations

[Andrew Hankinson]

Hi Urs,

Thanks for your thoughts! We’re still discussing the Github move among the technical team, but it’s helpful hearing from the wider community.

Issues of terms of services for free content is always tricky. Currently we’re using the Google Code service, and, being ignorant of their own stance, I just looked them up. They have a similar restriction to being able to close their services willy nilly. I guess that’s the cost of “free.” 

-Andrew

On Jul 3, 2014, at 2:35 PM, Urs Liska <ul at openlilylib.org> wrote:

> Joining the party late ...
> 
> I am referring to this thread:
> https://lists.uni-paderborn.de/pipermail/mei-l/2014/001244.html
> 
> I don't know if there has been a decision in the meantime and how it turned out in the end, but I wanted to point to a intense discussion we had about moving LilyPond's source code to Github.
> 
> While most people agree that Github's interface and collaborative possibilities are awesome (apart from a few people who actually prefer exchanging patches via email) it was pointed out that Github's Terms of Service are questionable when it comes to Free or Open Source software. In particular they reserve the right to close their free services or restrict access to projects or revoke contracts at will and at any time.
> 
> Although I personally use Github very much I think these are issues that should be considered for a project of MEI's intent.
> 
> Best regards
> Urs Liska
> 
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l