<div class="gmail_quote">On 9 October 2010 11:33, <span dir="ltr"><<a href="mailto:email@example.com">firstname.lastname@example.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">Quoting Edward Cherlin <<a href="mailto:email@example.com" target="_blank">firstname.lastname@example.org</a>>:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I have a partial draft of a "textbook" on the subject at<br>
<a href="http://www.booki.cc/discovering-discovery/" target="_blank">http://www.booki.cc/discovering-discovery/</a> It encourages XO owners to<br>
explore on their own and find out what questions they have before we<br>
give them answers.<br>
I like the idea. It encourages users to jump in and take risks, experiment, not worry if they have incomplete understanding.<br></blockquote><div><br>Me too, and have added some feedback to NZ educators on why open source can aid education in ways that closed source can't.<br>
<br>From :<br><p><font class="fixed_width">Here is one way that I can think that that open source benefits
<br> learners, based only on my own experience however. What I've witnessed
<br> from many computer uses is a sense of frustration and helplessness
<br> when something doesn't work as they think it should. People who buy
<br> software are trained to wait for automatic updates, or worse they are
<br> forced onto purchasing the next version. Processes inside
<br> organisations say, "If you're having problems, call the helpdesk."*
<br> The feedback loop might be an automated report that is generated and
<br> sent to an anonymous server.
<br> </font></p><p><font class="fixed_width">I would like to think that open source software would enable a sense
<br> of critical analysis, exploration and problem solving. For me, when I
<br> have a problem with a piece of software that I use, I tend to go
<br> through a process of reflection:
<br> </font></p><p><font class="fixed_width"> "Is this issue something other people might be having?"
<br> "Can I reproduce the problem?"
<br> "Why is the system built like this, there must be a reason? It must
<br> be useful for something."
<br> "Is the hassle of the computer problem larger than the hassle of my
<br> time to send feedback?"
<br> "How can I word a report to developers that explains what's going
<br> </font></p><p><font class="fixed_width">In short, I have the impression that users of paid software feel like
<br> they don't have the skills to contribute. They don't see themselves as
<br> a participant in a computer system. By computer system, I mean a
<br> system that includes software, hardware and the user to generate some
<br> useful output.
<br> </font></p><font class="fixed_width">Open source software has helped me by creating a sense of empowerment
<br> and discovery. I use the software that I want to run. When there's a
<br> problem, my involvement forms part of the solution.
</font><br><br></div> <a href="http://groups.google.com/group/mle-reference-group/browse_thread/thread/3caf7421439020d6">http://groups.google.com/group/mle-reference-group/browse_thread/thread/3caf7421439020d6</a> (scroll to bottom)<br>