On Thu, Mar 1, 2012 at 6:20 AM, Keshav Kini <keshav.k...@gmail.com> wrote: > IPython is also on github, > and Fernando has strongly recommended we consider moving Sage to github > (and has been doing so for at least 8 months, as far as I can recall).
If that's how you understood my posts, I wasn't clear enough then. I've told the sage team about how *our* experience in ipython with git/github has been on the net extremely positive, despite some real drawbacks (chiefly their sub-par bug tracker). Our development pace has greatly accelerated and I'm convinced the fluidity of the github workflow has been a factor there (though certainly not the only one, since not every project that moves to github automatically picks up speed). But I have never said "sage should move to git/github", because I don't actually know the sage development process well enough to meaningfully make such a statement. I know sage uses patches, there's the management of SPKG files, and an elaborate workflow that has evolved over the years. I have no clue if any or all of this would map well or not to git/github. That is a decision that only you guys can make, and it would be foolish for me to propose or try to push you in any particular direction. Besides, I should add that I have no stake whatsoever in whether Sage moves to git, github, bitbucket or anything else: I'm not affiliated with any of those organizations other than by having an account with them and liking github for my projects. If one of them helps Sage get better, I'll be happy; if a self-hosted solution is better for Sage, then so be it. I have no horse in this race, really. Cheers, f -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org