Hi there, some quick idea such that Sage dominates our lives even more:
1. We should have "Doc Days" (*) in addition to "Bug Days". For these sessions we would focus on (a) finding new bugs by (b) writing doctests. Also our Wiki might need some care and the manuals always need updates. 2. Also, a "Busfactor/Code-Review Day" might be a good idea. There are areas in the Sage codebase where basically only one developer feels comfortable poking around. This is usually not because of scary math only one person cares about but because nobody else every sat down and read the code. A "Bus Day" (y'know what if that developer gets run-over by a bus) would basically mean that we sit down and read chunks of code by other developers. If we are stuck the authors are right there on IRC to discuss the random questions we come up with. The coercion model, libSingular and cremona.spkg are examples for this kind of code in my mind. This would also mean that we review the code which is a very very nice thing to have. (*) William just indicated on IRC that we should probably move away from the idea of a whole day to devote to bugs and stuff. Instead a Sage Morning/Evening (depending on your favourite timezone) might allow more people to participate. E.g. weekends are usually a bad choice for me. Thoughts? Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _www: http://www.informatik.uni-bremen.de/~malb _jab: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
