<div dir="ltr"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
> A lot of effort already went into a hardware troubleshooting manual,<br>
> and it is already translated into Spanish and being field tested.<br>
> See <a href="http://wiki.laptop.org/go/XO_Troubleshooting_Guide" target="_blank">http://wiki.laptop.org/go/XO_Troubleshooting_Guide</a><br>
> Please don't duplicate, move, or fork this effort.<br>
</div></blockquote><div><br>The hardware troubleshooting guide is completely your project and I would *not* fork that project without a clear understanding with all parties involved. The guide does need some work for readability and flow, but the actual information is present. It just needs some serious polishing and formatting work.<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
</div>We're aware of the dissasmbly, repair, and troubleshooting sections<br>
you mention and intend to leverage them fully. For some of the<br>
information, the goal is to use the FLOSS Manuals API to embed it back<br>
into <a href="http://wiki.laptop.org" target="_blank">wiki.laptop.org</a>. It's good to know that some people at <a href="http://laptop.org" target="_blank">laptop.org</a><br>
are not aware of this intention.<br>
</blockquote><div><br>I'm doing my best to spread the word, but there is a *lot* of email that goes around here. How exactly the content is going to be distributed back may not involve our wiki at all. I see little problem with linking them to static and polished html somewhere other than the wiki. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
As Adam said, FLOSS Manuals has been selected for all docs, especially<br>
docs that can be shipped with the OS.<br>
<div class="Ih2E3d"></div></blockquote><div><br>Let's not get ahead of ourselves. Adam Hyde is an outside party to OLPC, Adam Holt runs support at OLPC, and Wad is the VP of Hardware Development (correct title wad?). If Wad has other plans for troubleshooting docs for repair that's outside of the sphere of this project.<br>
<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><div class="Ih2E3d"><br>
> Repair instructions are included as part of the Troubleshooting guide<br>
> (which references the Disassembly Guide).<br>
</div></blockquote><div><br>That would be excellent content for Repair centers and other users, either printed or available in several forms (exactly where FM shines). But that isn't needed to ship at the moment, and isn't exactly relevant to the SugarLabs volunteers for this event. I feel this can be skipped for now.<br>
</div> <br>All the best,<br>Seth<br></div><br></div>