[MEI-L] Hosting MEI on GitHub

[Johannes Kepper]

Given that almost everyone argues in favor of moving there, and even Perry says he's not aversed, I think we should go there. But I also think that Perry's argument is important. During the members meeting, Raffaele pointed out that the organizational structure should be reflected into the rights of the versioning system. Therefore, I would second the two of them and suggest to wait with the transition until we have a board in place. This gives us time to prepare both the data and ourselves…

just my 2c…

Johannes



Am 28.05.2014 um 20:19 schrieb Roland, Perry D. (pdr4h) <pdr4h at eservices.virginia.edu>:

> 
> I'm not opposed to hosting MEI on GitHub.  However, I don't want to rush headlong into the switch.  As I see it, there is good reason to stay the current course during the determination of MEI's organizational structure.  Once a new Board/Technical Group is in place, it/they/we can take up the GitHub vs. SVN discussion.
> 
> --
> p.
> 
> 
> 
>> -----Original Message-----
>> From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of
>> Eleanor Selfridge-Field
>> Sent: Tuesday, May 27, 2014 6:15 PM
>> To: Music Encoding Initiative
>> Subject: Re: [MEI-L] Hosting MEI on GitHub
>> 
>> +1 GitHub
>> 
>> Eleanor
>> 
>> -----Original Message-----
>> From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of
>> Andrew Hankinson
>> Sent: Friday, May 23, 2014 10:15 PM
>> To: Music Encoding Initiative
>> Subject: [MEI-L] Hosting MEI on GitHub
>> 
>> 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
>> 
>> _______________________________________________
>> mei-l mailing list
>> mei-l at lists.uni-paderborn.de
>> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> 
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l

-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : signature.asc
Dateityp    : application/pgp-signature
Dateigr??e  : 496 bytes
Beschreibung: Message signed with OpenPGP using GPGMail
URL         : <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20140528/b5911305/attachment.sig>