kcrisman wrote: > > Fascinating discussion. > > I just want to emphasize two things as a representative of those who > knew virtually nothing about programming or open source when we > started. > > 1) If you're serious about this doctesting (esp. on different > platforms) thing, there has to be a way to make it drop-dead easy - > like, "when you click submit on Trac, it starts testing on fresh > builds of the latest rc on five different chips". Maybe not that > quick, but something that does not require a contributor to have > access to any computer but their own. For many of us, that's enough > of a struggle!
The best I have seen in open-source development for this sort of thing is the wireshark developers list. Join that for a week and see what messages you get. If a build goes wrong, the bot notifies everyone, lets them know the files that have changed, lists the people that have made changes etc. It appears to work very well. Setting up such a build-bot is not something I have ever attempted. I would imagine is quite a bit of work to get it right. I do not know what William's criteria for granting an account on any machine except t2 is. But on t2, if someone needs access to develop code that is used by Sage, they can have an account. So for example libtool and autoconf developers have accounts. I do not myself see it a big deal to copy a few files to another machine and check it builds and tests ok. I will personally test the changes I make on * Solaris SPARC (my own machine) * Linux (sage.math) * OS X (bsd.math) * HP-UX (my own machine) * Possibly AIX. I don't own all that hardware, but I can use 'scp' Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
