On Wed, Oct 14, 2009 at 2:12 AM, Dr. David Kirkby <david.kir...@onetel.net> wrote: > 2) When submitting a patch, they attach logs showing building on all > platforms, *except* the one they normally work on, since one can assume > they have probably got their patch working there. > > This really is no more than an extension of the review process, where > the submitter of a patch has to convince the reviewer the code works on > the other platforms. That should increase the number of positive reviews > where the code actually makes it into Sage.
Think of the "random undergraduate I got to start working on Sage last week". It is enough of a hurdle for that person to post a patch, but to require them to build/install Sage on 6 platforms, test their patch on all of them, etc. is unrealistic. Many young people today don't even know the UNIX command line at all, and yet they can make great contributions to Sage. Implementing the above suggestion would reduce their probability of contributing substantially. I hope soon we'll have a web-based interface that allows one to easily change Sage code using Bespin (that code editor), make patches, test changes (on 10 platforms), etc., all trivially from a web browser via a webapp. -- William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
