kcrisman wrote: > > > On Feb 16, 12:05 am, "William Stein" <[EMAIL PROTECTED]> wrote: >> On Feb 15, 2008 8:27 PM, kcrisman <[EMAIL PROTECTED]> wrote: >> >> >> >>> The bottom line is this: If William's goal is really to have *every* >>> user be a developer (or at least to contribute very minor >>> documentation corrections or tests, if that counts as developing), as >>> he's stated numerous times, and if the rest of the main Sage >>> development team agrees, then somewhere down the line there needs to >>> be something created as user-friendly with respect to this as the >>> "Evaluate" button or the extra info about Shift-Enter which has been >>> discussed recently is for end users. >>> I really do want to contribute in whatever way I can, but trying to >>> figure it all out myself in limited evening time away from a network >>> connection is just too big a challenge. Hence, thanks for any and all >>> responses. >> Precisely what sort of Sage development do you intend to do? >> Please outline some of the specific things you would do were >> the "mercurial hurdle" completely removed. Thanks! >> >> -- William > > Well, of course eventually it would be nice to add functions. My main > current interest in Sage, given time constraints, would be to add more > computationally uninteresting but pedagogically useful functions and > methods for calculus or other undergraduate courses (as I think I've > conveyed in other posts). But for now I would just like to do what > Robert asked me to a few weeks ago: > >> You have found a documentation typo. You should fix that and submit a patch. > > And I just don't know what I did wrong in trying to follow his > instructions from the Sep. 20 discussion. Documentation is not too > hard to fix, neither is adding tests, but I can't figure out what to > do with the changed code. I don't mind using mercurial - in fact, I > am really enjoying learning all this new developer information, > otherwise I wouldn't bother to spend time on it! I'm not suggesting > that there is a "develop" button! But either I made a big mistake > (which is likely) or those instructions assumed some sort of knowledge > about the revision process which I am not familiar with, so I (and > probably many others) need more detailed instructions if we are to > help.
Thank you for working with us on this! I hope people like you help us become more new-user friendly, especially with regards to contributing code back. Have you looked at the Sage Programmer's guide on the documentation page? The direct URL is: http://sagemath.org/doc/html/prog/index.html As I glanced through the book, I realized that it's probably overwhelming to read through it all just to see how to add some code. The Mercurial tutorial (chapter 7) sounds like what you want. What are your thoughts about how easy the tutorial is to understand? As I look through it, it seems to presuppose some understanding of source code revision systems, but I'd like to hear your point of view. You're always welcome to post a new function here or on sage-devel and we'll help you get it refereed and into Sage if it is appropriate. As you know, we can definitely use help in the calculus and high school/undergraduate levels of Sage. I'd like it to be easy enough to add functions that a high school or college student could sit down and write out a function their teacher covered in class and easily get it submitted. Thanks for your patience and understanding, Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
