[Swift-devel] Migrating to github
Ketan Maheshwari
ketan at mcs.anl.gov
Tue Feb 4 13:32:24 CST 2014
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.
On Tue, Feb 4, 2014 at 1:16 PM, Yadu Nand <yadudoc1729 at gmail.com> wrote:
> I think moving to Github is a great idea, also makes sense to merge
> cog and swift into one repo.
>
> Part of the reason for the popularity of Github is the social/open
> aspect of development. Going
> forward we'd definitely need that, and the sooner we migrate, the better.
>
> It also looks like there's some nice documentation here
> http://git-scm.com/book/ch8-1.html
> about git-svn interoperability.
>
> -Yadu
>
> On Tue, Feb 4, 2014 at 12:00 PM, Wilde, Michael J. <wilde at mcs.anl.gov>
> wrote:
> > In in favor of considering this, and putting Swifts /K and /T in close
> > proximity in the repo.
> >
> > I think its a step to becoming a more open open-source project.
> >
> > - Mike
> > --
> > Michael Wilde
> > Mathematics and Computer Science Computation Institute
> > Argonne National Laboratory The University of Chicago
> >
> > ________________________________
> > From: swift-devel-bounces at ci.uchicago.edu
> > [swift-devel-bounces at ci.uchicago.edu] on behalf of David Kelly
> > [davidkelly at uchicago.edu]
> > Sent: Tuesday, February 04, 2014 11:44 AM
> > To: swift-devel
> > Subject: [Swift-devel] Migrating to github
> >
> > Right now we have two repos - cog on sourceforge, and Swift on
> > svn.ci.uchicago.edu.
> >
> > Sourceforge's SVN commit hooks are broken, so we do not get email updates
> > automatically from them when a change is made. Instead I rigged a cron
> job
> > that runs every 5 minutes, checks for changes, and emails them out. It's
> a
> > little ugly.
> >
> > Developers wanting to make contributions to Swift need a CI account. This
> > may discourage new developers from getting involved.
> >
> > Having two repos makes branching, tagging, and building more tedious
> than it
> > needs to be.
> >
> > This may need more discussion, but I would like to propose that starting
> > with 0.95, let's merge cog and Swift and move to github.
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
> >
>
>
>
> --
> Yadu Nand B
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20140204/2b9aa4cb/attachment.html>
More information about the Swift-devel
mailing list