I agree with Valerio's (humble) opinion. Having a static manual would have problems due to the dynamic situation of the software. (The reason wiki's were born!) We need to have an official forum, as questions will be asked and it will strengthen the community.
<a href="http://forums.openmoko.org">forums.openmoko.org</a> I believe is the way to go.<br><br>When people start asking questions over and over again, a) ask them to search the forums somewhat better next time, and b) make it a wiki article.
<br><br>This is a pretty important issue...<br>opinions?<br><br>Kyle Bassett<br><br><br><div><span class="gmail_quote">On 7/22/07, <b class="gmail_sendername">Valerio Bruno</b> <<a href="mailto:valerio.bruno@torlug.org">
valerio.bruno@torlug.org</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;">Giles Jones ha scritto:<br>> The number of these users can me minimised by having a very good manual.
<br><br>This is false imho.<br><br>> I know that people don't read manuals often but that's because<br>> troubleshooting sections are always stuck at the back. Have a special<br>> separate troubleshooting manual and they may read it.
<br><br>Remember you're talking about a free customizable smartphone where you<br>can install lot of applications developed around the world. Not a static<br>pre-installed software super-branded phone.<br>As customization capacity/functionality increase, people questions
<br>increase too imho.<br><br>Valerio<br><br><br><br>_______________________________________________<br>OpenMoko community mailing list<br><a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community">http://lists.openmoko.org/mailman/listinfo/community</a><br></blockquote></div><br>