Documentation Team Kick Off Meeting Agenda

Agenda for the kick off meeting

• Introductions
• MeeGo 1.1 release: target format/s and site/s
  • Ronan to provide the latest info on developer.meego.com
• Agreeing on ways of working
  • Meetings, communication channels
  • Backlog (storing requirements and following task progress)
  • Sharing work-in-progress drafts
• First rough draft of a content plan
  • Discussion
  • Dividing content into areas and assigning owners for the areas
  • Possibly roadmapping some content areas for later releases?
• Agreeing on an approval process (testing, reviews)
  • When should the content be ready for reviews and for testing?
  • Test procedural information (step-list instructions)
  • Suggestions for reviewers?
  • Who gives final approval?
• Release updates after the official release day
  • How to manage updates to content? Sprints?

Content areas (for discussion, to be updated in the meeting)

• Terminology/glossary
• Release overview, description of the developer offering
• Overview of MeeGo websites and their purpose
• Setup/Getting started instructions for application developers (from installation to first app, divide into smaller areas in meeting)
• Setup/Getting started instructions for platform developers
• Other tool instructions (what is needed here?)
• Architecture overview
• API reference and API overview
• UI guidelines
• Samples
• Packaging and publishing
• Release notes
• Productization (covers all areas to some extent, but should this be a separate item?)

Other topics proposed:

• API documentation
  • who owns this?
  • layout (still not here)
  • how are netbook & handset documentation harmonized?
  • content (limited to Qt & mobility + OpenGL ES)
• Other documentation
  • who owns this?
  • is there an agreed plan how to move forward?
  • what architecture documentation will be provided?
• Sample applications
  • will there be some extended examples?
• What do we do with the current documentation in wiki.meego.com ?