[MEI-L] Hosting MEI on GitHub

[Adrian Holovaty]

+1 from me. In case it's helpful, here are my notes about migrating a
reasonably large open-source project (Django) to GitHub a few years ago:
http://www.holovaty.com/writing/django-github/

Aside from the obvious advantages in usability and collaboration, there are
some non-obvious advantages such as the fact that it gives people "credit"
for their contributions in an ecosystem that many employers are looking at.

Adrian

--
Adrian Holovaty
Soundslice: http://www.soundslice.com/
Personal: http://www.holovaty.com/



On Sat, May 24, 2014 at 1:15 AM, Andrew Hankinson <
andrew.hankinson at mail.mcgill.ca> wrote:

> Hello,
>
> At the MEI Hack Day today we discussed the pros and cons of moving MEI
> development from Google Code hosting (
> https://code.google.com/p/music-encoding/) to GitHub. Both of these tools
> are used to share and collaborate on open source projects. However, it was
> felt by some that GitHub offers more possibilities for easy collaboration
> and participation than the Google Code platform, and as such we should
> consider moving our hosting platform.
>
> To see if this was possible we experimented with moving both the code (and
> its complete version history) and our issue tracker. The results of our
> testing are available here:
> https://github.com/music-encoding/music-encoding. All of the code and
> issues seem to have been migrated without a problem.
>
> Before we make the final decision to switch, however, we wanted to put it
> to the community to gather any questions or comments about this switch, and
> to give people an opportunity to voice any concerns they may have.
>
> After a period of discussion the technical team will make a final decision
> and notify the community. This will not be a long period of discussion,
> since it will be hard (and confusing) to manage two issue trackers and
> repositories, so please do not wait.
>
> Thank you,
> -Andrew
>
>
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20140524/51573457/attachment.html>