kcrisman <kcris...@gmail.com> writes: > On Mar 1, 9:20 am, Keshav Kini <keshav.k...@gmail.com> wrote: >> The main thing I want for Sage's development process is a push/pull >> architecture of some kind. I don't mind if that ends up meaning that we >> finally start using Mercurial in the way it was "meant" to be used, > > Using HG in this way has been a request for at least three or four > years, and probably since when Sage switched from darcs to hg. > > Is doing all this stuff in Mercurial an option, especially for folks > like sage-combinat who have spent a lot of time taking people who are > *not* hard-core programmers, but want to do research math, up to speed > in hg? This seems like a potential halfway point, assuming that there > is a site which would want to host this all - Sage seems so huge, I'm > kind of surprised even github would want to host it for free, though I > guess it's GPL...
I am very far from convinced that sage-combinat developers have been learning anything substantial about *Mercurial*. Going by what I see on the wiki pages about combinat, what a lot of time has been spent on is taking people who are not hard-core programmers and teaching them how to plant in and help to fertilize a colorful garden of *patch files*. Learning git will be about equal to learning "real" Mercurial in terms of head-scratching required, in my estimation (though of course I could be wrong). Furthermore I intend to write a script called $SAGE_LOCAL/bin/sage-dev which will walk people through the process of using git to work on Sage - basically a "wizard", asking yes/no questions and soliciting input with ample explanatory text - which I believe will be pretty intuitive and simple, though we'll see how true that is once I set out concrete design goals and ask for feedback. For what it's worth, I have emailed the main sage-combinat developers a little while ago and asked them for an overview of what I should keep in mind when designing this SEP, so don't worry too much about sage-combinat :) They will be kept informed at every step and included in our planning discussions. As it happens, the Sage library isn't that huge. The git repo of the Sage library is just 30 MB (incidentally, only about half the size of our Mercurial repository). Github offers 300 MB of space to non-paying members, and even that is just a "soft limit" (i.e. if you have a reasonable excuse, you may use more than 300 MB). We are of course not going to be using github to host the src/ directories in our SPKGs of external programs. However, hosting the spkg-install files, SPKG.txt, etc. is something that might be on the table, though probably farther in the future than switching to git and a push-pull system for the Sage library proper. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- 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
