Fri Dec 12 12:07:52 CET 2008
1. For the nature of wiki system, everything is changeable , so we will keep fast changing thing on wiki. But we also need something static , like "Manual" , focus on hardware (case and electronics), libraries (EFL and framework), environment (Hosting, crosscompiling, OE). This is what exactly Openmoko wants. Maybe we can start by a list that meet criteria we list above ? Where is the best place we should start?
2. yes we are looking to hire someone , like technical editor, who can rewrite technical stuff for us. Any interested people , please contact us.
Minh really give us very valuable ideas , I hope I can make it real together with the people of documentation list. The list I posted on wiki last week , I already deleted it. And I suggest we start over it .
Minh Ha Duong æå°:
>> know where you are so let's get GPS going at the same time. A chapter
>> describing and debating the distros would be a good start and then a
>> chapter for each distro ending up with phones in the same sort of
>> state would then be a good second.
>>> The problem is, the distro's change so quickly that you wouldn't get
>> anything printed before it was out of date...
> Absolutely. Documenting fastchanging matters is better left to the wiki.
> The Manual would rather focus on hardware (case and electronics), libraries
> (EFL and framework), environment (Hosting, crosscompiling, OE). Then
> description of subsystems with sample applications. I would also like it to
> include some human/social aspects: OM's history, philosophy, politics,
>> As a result of my posting, I'm already building up the chapter on
>> getting SHR running so I'll volunteer that if it would be wanted.
> Cool. Every help is wanted.
>> BTW. If you need to go from Wiki to a print quality PDF we have a tool
>> that does just that via some simple CSS styles using the Prince XML to
>> HTML converter (http://www.princexml.com). We haven't yet written a
>> complete published book with it but have used it for fully illustrated
>> manuals. Let me know if this is of interest. Sure saves messing with
> I am certain that this is of interest. I suspect that if beyond the software
> itself, you offer additional editorial services, like technical (re)writing
> or workflow management, OM may be interested too.
More information about the documentation