One central task is identifying who might want to use MeeGo and who'll be using the developer documentation. We should always bear the audience in mind when writing documentation, and try to provide coherent narratives for each type of developer. This means making the goals of the developer as easy as possible to achieve.
An example would be: Don't require an application developer to build a MeeGo image or compile a development tool (unless they really have to).
This means we need to be very clear about the audience for any given document. Some suggestions for audience types:
There will obviously be overlap, but keeping these (or similar) in mind helps focus.