Changes

Jump to navigation Jump to search
946 bytes added ,  12:16, 15 January 2011
Good questions and bug reports
Line 3: Line 3:  
</noinclude>
 
</noinclude>
   −
Some ideas are not easy to discover; the concept of guided [[discovery]], where a mentor helps point a learner in a fruitful direction, can accelerate the pace of learning. Some Sugar features are not easy to discover and while we are working to improve upon this, we provide some guides to discovery below.
+
Some ideas are not easy to discover; the concept of guided [[discovery]], where a mentor helps point a learner in a fruitful direction, can greatly accelerate the pace of learning. Some Sugar features are not easy to discover and while we are working to improve upon this, we provide some guides to discovery below.
    
Eventually, as editors have sufficient material, the official documentation at  
 
Eventually, as editors have sufficient material, the official documentation at  
Line 306: Line 306:  
This is presently only relevant to OLPC XO hardware, which uses Open Firmware instead of a BIOS.
 
This is presently only relevant to OLPC XO hardware, which uses Open Firmware instead of a BIOS.
   −
On an unlocked XO,
+
On an unlocked XO, either
    
* At boot time, press and hold the escape key to get into Open Firmware.
 
* At boot time, press and hold the escape key to get into Open Firmware.
Line 316: Line 316:     
Be careful with OFW. You can seriously mess up or brick your XO with it. You might want to experiment in gForth first.
 
Be careful with OFW. You can seriously mess up or brick your XO with it. You might want to experiment in gForth first.
 +
 +
==Trouble reports==
 +
 +
There is a bit of an art to writing descriptions of problems so that others can tell what went wrong when you don't know. It is part of the more general art of asking useful questions.
 +
 +
* [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively], by Simon Tatham
 +
* [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way], by Eric Steven Raymond and Rick Moen
 +
 +
You can apply these lessons to writing bug reports on various bug trackers, trouble reports to the Support Gang forum, and discoveries of more of The Undiscoverable here. In brief,
 +
 +
* Identify the hardware and software, including the versions used.
 +
* For the undiscoverable, describe the person who could not make the discovery (age, education, language...)
 +
* State what you did.
 +
* State what you expected to happen.
 +
* State what happened instead.
 +
* What did you try to fix the problem?
 +
    
==Subpages==
 
==Subpages==
    
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
 
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
1,009

edits

Navigation menu