Lots of 'ifs' and 'shoulds' in your responses in the last note Jim, and as you know I'm on the ground with the troops, and I deal with the way things are, regardless of how it should be, but mindful of how we'd like it to be. Yes our system is challenging at times and has lots of issues that may or may not be common (and I try not to air too much dirty laundry), but as I reminded Jim in a previous email, if some parents and teachers and a principal hadn't taken control of a non-functional system in our school from the admins and jumped out of the box, he wouldn't have had the architect's job. A little rebellion from your users can be a good thing, and could lead to a new paradigm, as it did in Atlanta.
James P. Kinney III wrote:
Again, the classroom is generally not a test server environment. That is where the plan is for the teacher to look the most competent and having students wade through buggy software is just a respect-loosing process.
Keeping in mind the classroom server we're talking about serves only the teacher's room, I eagerly await Marilyn's response to this one...
In the situation where only a single class uses a single machine, rebooting to access a known stable image is OK. But for larger scale situations it is completely unacceptable for teacher A to reboot the server that teachers B-F are using!
Agreed to the latter (was never supporting that idea) and halleluia to the former Jim!
Daniel -- Daniel Howard President and CEO Georgia Open Source Education Foundation