Quim, I understand what you mean - don't forget that we covered quite a bit at the weekend - the ToC only represented a small part of the results. I think it would be wrong to take it as anything more than a data point and some general "focus group" opinion.

I am pleased that some of the things we came up with have resonated though - hopefully that'll be useful.

To your particular point: I don't think what ended up summarised in the wiki represents quite what we meant

So I think that was just hasty cut'n'pasting from a badly formatted email

Better would have been:
2. Flow Suggestion
3. Reference: Start with 'upstream' and core linux

ISTR wanting to have "flow suggestions" as a set of targeted flows for devs from different backgrounds or wanting to do different things (we just had app vs platform but adding web in there makes sense)

Then I think we wanted reference material in 2 parts.

First to see what maemo additions there are to standard linux frameworks (as per examples - and frankly, the less Nokia diverge from upstream, the less content there is here). Much of this would refer out to existing reference docs and would only really discuss local modifications. Essentially Nokia are not authoritative for this.

Then on to the meaty stuff: the maemo specific docs where if Nokia doesn't document it then we don't have a clue

This section was expected to be a reference, not really a book/narrative.