> > Our point is that the new blood you are looking for will have to come with a > > knowledge of mercurial if they want to know what's going on. > > I agree.
That's too bad. Remember, this is a *math* project, not a computer project per se. Some of your developer base (maybe not ever a "main" developer, but the long tail) will come in with zero programming experience, and will view HG as a very scary thing to begin. They might still want to help with spkg updating; that shouldn't be reserved to "expert" Sage developers. > > > If in spkg.txt, or even in the README file at the top level, there are easy > > to > > follow instructions on how to extract useful info from mercurial log that > > may > > not be so bad. > > That's a great idea. This seems like a reasonable compromise. A boilerplate added to any SPKG.txt which explains how to invoke HG from within Sage, which directory you want to be in, etc., should only take a paragraph or two, and could even be at the end of the file, referred to in a one- liner near the top. The key is that there should be some way to get from a plain text file to the result of helping make Sage better! > In fact, I learned some things in this thread about how to use the hg log. +1 - kcrisman -- 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
