Talk:Objective:Co-production of official & community documentation

Moved from 2010 Agenda

--dneary 15:57, 4 June 2008 (UTC)
 * See Edd Dumbill's appraisal of developer.gnome.org:
 * Audience - clearly separate documentation for tablet users, application developers and core platform hackers
 * Provide tutorials and quizzes for core API components
 * API documents and tutorials should be dated to make it clear whether they are current
 * Editor - ensure that the content is maintained, coherent, correct
 * Content - identify resources which are necessary and have them written
 * Evangelism - we need to have more ISDs creating software for maemo, and an outreach program is needed

This objective is now listed in the maemo.org development backlog. Nemein pushes but you can help out already today.


 * Documentation System. (Help system???)
 * getting started is way to difficult and will detour many great minds
 * outsource to the blogger types in the group
 * voice record "dictate to the typers"
 * video and slide w/audio help for many
 * cut out the opinions where are the real facts (make an easy to find location)
 * Clearer UI guidelines for 3rd party developers.
 * Introducing newcomers to the platform is definitely a core case, since we expect lots of them coming. And not with a Linux and open source background necessarely. Again, what is expected and ideal, then the details to be worked out in separate pages.--qgil 09:05, 2 June 2008 (UTC)