Meego Wiki
Views

SDK/Documentation/MeetingMinutes/20101005

From MeeGo wiki
< SDK | Documentation | MeetingMinutes
Revision as of 09:51, 4 October 2010 by Tittav (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Attendees

Agenda

  • Adding content directly into Drupal - possible 4.10.2010 (AP Ronan: confirm the date)
  • Initial content structure status
  • Backlog (storing requirements and following task progress) - use wiki for now, move to Bugzilla for 1.2
  • First rough draft of a content plan
    • Status from area owners
  • Agreeing on an approval process (testing, reviews)
    • 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

  • Terminology/glossary (Titta)
  • Release overview, description of the developer offering (Ronan)
  • Overview of MeeGo websites and their purpose (Ronan)
  • Setup/Getting started instructions for application developers (from installation to first app, divide into smaller areas in meeting) (Bob, Veli)
  • Setup/Getting started instructions for platform developers (community-driven area)
  • Other tool instructions (e.g. linking to information on Qt tools, MADDE, MAD-Developer, Packaging tools, OBS use, appstore submission tools, performance tools) (Elliot)
  • Architecture overview (Titta)
    • Sunil / Arjan and Sakari updating. Representation changing.
    • Titta: Initial idea on how the changes affect the API reference site drafted. I'm following the discussions on architecture team side.
  • API reference and API overview : Qt 4.7, Qt mobility 1.0, Meego Touch (MTF), WRT (Murali Punaganti)
    • Need to follow-up on platform API. How will it be presented.
    • Titta: we should be able to freeze API content for 1.1 after 4.10.
  • UI guidelines
    • Elliot: I verified with the design team in the UK that the design guidelines for handset are current and valid; they were written by Nokia and are the basis of the reference handset UX design. No similar guidelines for netbook are planned.
    • Elliot: whether we want to move this content to developer.meego.com is an open issue
  • Samples (existing hello world level examples for Qt, Qt mobility, MeeGo Touch, and WRT) (Elliot and Kerry Jiang (PRC SDK mgr))
  • Packaging and publishing (covered in other tool instr.)
  • Release notes (Veli, Bob)
  • Productization (covers all areas to some extent, but should this be a separate item?) (Titta, Ville)

Other topics proposed

  • Sample applications
    • Need sample for each major type of task (eventually). e.g. How to create mutlimedia app, how to use telephony apis, how to use social web services, etc.
  • What do we do with the current documentation in wiki.meego.com ?
  • look-and-feel (Style Guide exists, but CSS available on 4.10.
  • define a process for adding new material to sites
Personal tools