<div dir="ltr">Great idea. However, one thing to consider is that there will still be need of svn repos such as SwiftApps and ExM which are too big to migrate to github. So there will be two repo/protocols to manage.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 4, 2014 at 1:16 PM, Yadu Nand <span dir="ltr"><<a href="mailto:yadudoc1729@gmail.com" target="_blank">yadudoc1729@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think moving to Github is a great idea, also makes sense to merge<br>
cog and swift into one repo.<br>
<br>
Part of the reason for the popularity of Github is the social/open<br>
aspect of development. Going<br>
forward we'd definitely need that, and the sooner we migrate, the better.<br>
<br>
It also looks like there's some nice documentation here<br>
<a href="http://git-scm.com/book/ch8-1.html" target="_blank">http://git-scm.com/book/ch8-1.html</a><br>
about git-svn interoperability.<br>
<br>
-Yadu<br>
<div><div class="h5"><br>
On Tue, Feb 4, 2014 at 12:00 PM, Wilde, Michael J. <<a href="mailto:wilde@mcs.anl.gov">wilde@mcs.anl.gov</a>> wrote:<br>
> In in favor of considering this, and putting Swifts /K and /T in close<br>
> proximity in the repo.<br>
><br>
> I think its a step to becoming a more open open-source project.<br>
><br>
> - Mike<br>
> --<br>
> Michael Wilde<br>
> Mathematics and Computer Science Computation Institute<br>
> Argonne National Laboratory The University of Chicago<br>
><br>
> ________________________________<br>
> From: <a href="mailto:swift-devel-bounces@ci.uchicago.edu">swift-devel-bounces@ci.uchicago.edu</a><br>
> [<a href="mailto:swift-devel-bounces@ci.uchicago.edu">swift-devel-bounces@ci.uchicago.edu</a>] on behalf of David Kelly<br>
> [<a href="mailto:davidkelly@uchicago.edu">davidkelly@uchicago.edu</a>]<br>
> Sent: Tuesday, February 04, 2014 11:44 AM<br>
> To: swift-devel<br>
> Subject: [Swift-devel] Migrating to github<br>
><br>
> Right now we have two repos - cog on sourceforge, and Swift on<br>
> <a href="http://svn.ci.uchicago.edu" target="_blank">svn.ci.uchicago.edu</a>.<br>
><br>
> Sourceforge's SVN commit hooks are broken, so we do not get email updates<br>
> automatically from them when a change is made. Instead I rigged a cron job<br>
> that runs every 5 minutes, checks for changes, and emails them out. It's a<br>
> little ugly.<br>
><br>
> Developers wanting to make contributions to Swift need a CI account. This<br>
> may discourage new developers from getting involved.<br>
><br>
> Having two repos makes branching, tagging, and building more tedious than it<br>
> needs to be.<br>
><br>
> This may need more discussion, but I would like to propose that starting<br>
> with 0.95, let's merge cog and Swift and move to github.<br>
><br>
</div></div>> _______________________________________________<br>
> Swift-devel mailing list<br>
> <a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>
> <a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Yadu Nand B<br>
_______________________________________________<br>
Swift-devel mailing list<br>
<a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><br>
</font></span></blockquote></div><br></div>