Good points. The OLPC is designed around collaboration. The model really works well where every child in a class has his/her own laptop, uses it in and out of school, and lives in close enough proximity to other class members to make the Mesh work. In class one kid discovers how to do something and teaches the other kids (and teachers as well).
<br><br>In an address at Harvard Law, Negroponte said something like: "People ask me who is going to teach the teachers to teach the children how to use the XOs --- and I wonder what planet are they on? ..."<br>
<br>A child who gets one through G1G1 in isolation will not be able to fully benefit from collaboration and thus, along with parent/tutor, would definately benefit from user documentation in lieu of help from others in class. Likewise, the Carlos Slims approach of putting them in Mexican libraries.
<br><br>If G1G1 goes big-time in November, you can sure bet that there will be "OLPC for Dummies" books, etc. by Christmas.<br><br><div><span class="gmail_quote">On 10/15/07, <b class="gmail_sendername">Todd Kelsey
</b> <<a href="mailto:tekelsey@gmail.com">tekelsey@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am amazed and inspired by all the wonderful projects and activities that have arisen from the laptop project -- and though I was skeptical at first, I have also come to appreciate the constructivist approach to education; I didn't "get it" until I came to appreciate the notion of allowing children to come to "aha" moments on their own. The fact that children do fine without manuals at the present level of interaction is a testament to the design of the computer and the philosophy behind it. As generation xo grows older, I think they will want to get deeper into
the systems, and as they do, I think they will want more information,
and I'd like to help make that freely available.<br><br>I think a user manual or documentation will be more helpful for adult
learners who will end up participating in the laptop community, and who
would find it helpful to have something to refer to. Perhaps users
could learn many things simply by exploring, and yet they might
appreciate having something to turn to. Other people may not have
personal possession of a laptop, but would be interested in learning
how they could support the project. Some people who order the laptops
through <a href="http://www.xogiving.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">www.xogiving.org</a> will get frustrated with the laptop if they
have no resources to turn to, and I'd like to help them have fun.<br><br>I think the idea of encouraging children to help each other learn is
wonderful; I also appreciate the principle of inclusiveness, and I
think that one way to be inclusive is to address various learning
styles. <div><span class="e" id="q_115a6b4123224760_1"><br><br><div><span class="gmail_quote">On 10/15/07, <b class="gmail_sendername">Steve Fullerton</b> <<a href="mailto:fullerton.steve@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
fullerton.steve@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Ed and all,<br><br>I fully appreciate the detail. However, IMHO I think that there is some re-thinking required re: the traditional "user" documentation. The core of the OLPC (literally one laptop per child; the model does not work as well if there is not possession of a laptop for each child) is that of collaboration.
<br><br>One child learning something and then teaching his/her classmates. OLPC machines are not meant to be used in isolation. You could actually make a credible argument that user manuals are bad for the project.<br><br>
The highly intuitive design of Sugar and the experience of the pilots bears this out. The children seem to do just great without manuals, discovery is enhanced, and many of the constructionist ideals are realized.<br><br>
What do you think?<div><span><br><br><div><span class="gmail_quote">On 10/15/07, <b class="gmail_sendername">Ed Trager</b> <<a href="mailto:ed.trager@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
ed.trager@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi, Michael,<br><br>Just a few comments for consideration by everyone:<br><br>> ...<br>> Doc writing conventions:<br>><br>> Some linguistic research has been done on "simplified English" as a<br>> subset of English to use for low-level learners, and I think that it
<br>> might be a good place to look for ways to simplify the source_docs.<br>> But just thinking intuitively, I have cooked up the following<br>> suggestions in order to generate discussion:<br>><br>> * Pronouns.
<br>> o Use the first-person singular pronoun "I" to represent the<br>> author of the docs,<br>> o the second-person singular pronoun "you" to represent the<br>> reader of the docs, and
<br>> o the first-person plural pronoun "we" to represent the OLPC project.<br>><br>> o Examples. "We have designed a screen that switches to<br>> black-and-white to conserve energy. I will explain how to switch your
<br>> screen to black-and-white. First, you press the X button on your<br>> keyboard...." Because we want the docs to be easily translated and<br>> easily understood, the tone should be personal, using "I" for the
<br>> voice of the writer. This will be easier for amateur translators to<br>> translate and easier for younger readers to understand. This will also<br>> help the writer avoid the passive construction, which is very
<br>> difficult for some non-native English speakers to understand.<br><br>I agree completely that the English passive construction should be<br>avoided at all times.<br><br>I mostly agree with your suggestion on use of pronouns. Use of "I"
<br>and "we" are fine.<br><br>REGARDING THE PRONOUN "YOU" IN ENGLISH:<br>----------------------------------------------------------<br><br>However, as a native English speaker, I find the use of the pronoun
<br>"you" in the imperative mood often quite jarring.<br><br>Imperative sentences in which the "you" is absent are understood by<br>native speakers of English to convey a softer, less imperative tone.
<br>
Such sentences are considered more polite. Compare:<br><br>(A) "First you press the X button on the keyboard."<br><br> ... versus:<br><br>(B) "First, press the X button on the keyboard."<br><br>One or two instances of "you" in imperatives or directions in spoken
<br>or written English may not seem too bad, but after a series of them,<br>it becomes irritating.<br><br>So while I have no objection to simple English which will be easily<br>understood by younger learners of the language, we must also be sure
<br>that we do not proscribe an incorrect idea regarding the usage of the<br>pronoun "you" in imperative sentences in English.<br><br>In short, it is *not* OK to use "you" repeatedly in a series of<br>
imperatives or directions (such as instructions for using a laptop).<br>The absence of the pronoun "you" is preferred when giving directions<br>in English.<br><br>REGARDING POSSESSIVE PRONOUNS:<br>-----------------------------------------------
<br><br>Look again at the sentances Michael used for his example:<br><br>> I will explain how to switch your screen to black-and-white.<br>> First, you press the X button on your keyboard...."<br><br>English speakers make frequent use of possessive pronouns, as is the
<br>case here with : "your screen" , "your keyboard" .<br><br>But in many other languages (perhaps most other languages?) we would<br>not use possessive pronouns here at all. All of these English<br>
"your"s, if translated quite directly into foreign languages, results
<br>in very annoying and unnatural sounding texts in my experience.<br><br>So I would advise we try to fix the English from the start by avoiding<br>unecessary invocations of possessive pronouns, especially "your":
<br><br> I will explain how to switch the screen to black-and-white.<br> First, press the X button on the keyboard...."<br><br>I basically agree with the rest of Michael's suggestions, so that's<br>
all the comments I have.<br><br>-- Ed Trager<br>_______________________________________________<br>Devel mailing list<br><a href="mailto:Devel@lists.laptop.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Devel@lists.laptop.org</a><br><a href="http://lists.laptop.org/listinfo/devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.laptop.org/listinfo/devel</a><br></blockquote></div><br><br clear="all"><br></span></div>-- <br>Regards,<br><br>Steve<br>____________________________<br>Steven C. Fullerton<br>email: <a href="mailto:fullerton.steve@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
fullerton.steve@gmail.com</a><br>cell/voice mail: 619.339.9116<br>____________________________
<br>_______________________________________________<br>Devel mailing list<br><a href="mailto:Devel@lists.laptop.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Devel@lists.laptop.org</a><br><a href="http://lists.laptop.org/listinfo/devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.laptop.org/listinfo/devel</a><br><br></blockquote></div><br><br clear="all"><br>-- <br></span></div><span class="sg">Todd Kelsey<br>630.808.6444
</span></blockquote></div><br><br clear="all"><br>-- <br>Regards,<br><br>Steve<br>____________________________<br>Steven C. Fullerton<br>email: <a href="mailto:fullerton.steve@gmail.com">fullerton.steve@gmail.com</a><br>
cell/voice mail: 619.339.9116<br>____________________________