Meego Wiki
Views

SDK/Meetings/1st Documentation

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Initial draft)
(Possible topics for the kick off meeting)
Line 1: Line 1:
= Documentation Team Kick Off Meeting Agenda =
= Documentation Team Kick Off Meeting Agenda =
-
== Possible topics for the kick off meeting ==
+
== Agenda for the kick off meeting ==
* Introductions
* 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?
 +
 +
 +
===Other topics proposed: ===
* API documentation
* API documentation
** who owns this?  
** who owns this?  

Revision as of 13:17, 27 September 2010

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?


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 ?
Personal tools