Attendees
Elliot Smith, Bob Spencer, Murali, Titta Väyrynen, Ronan MacLaverty
Agenda
- Adding content directly into Drupal is now possible
- In the Infostructure, documentation for MeeGo 1.1 belongs under Guides and Reference sections
- AP Ronan: can API docs be also added to Drupal already?
- AP Ronan: editing Drupal site, provide instructions and info
- AP Ronan: check the copyright statement
- How to determine between stable and unstable API content? Only stable API doc to be added for now.
- Defining a backlog to wiki (storing requirements and following task progress) for 1.1
- Destination to be added to plan (area under developer.meego.com for example)
- AP ALL: Comments to Titta this week (week 40)
- Content status from area owners (see section Content areas, below)
- Agreeing on an approval process (testing, reviews)
- Testing the documentation: testing step-list instructions is enough. Try and add this into the normal testing process. QA: http://wiki.meego.com/SDK/QA
- AP Titta and Bob: gather a list of reviewers per content area
- Who gives final approval? (General website: Imad/Valterri. Final: Bob/Veli, right before release)
- Release updates after the official release day
- Check update needs in connection of the MeeGo 1.2 requirement planning
- E.g. 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.
- Wiki.meego.com
- Source, community enabler, open for everyone to edit
- Team activities (meeting minutes, plans)
- What do we do with the current documentation in wiki.meego.com ? -> Go through, see what to transfer to developer.meego.com,
- look-and-feel (Style Guide exists, but CSS available on 4.10.
- define a process for adding new material to sites
- Suggestion for process of transferring docs from wiki to developer.meego.com ("official"):http://wiki.meego.com/SDK_documentation_guidelines
- Idea: when new wiki content is created, file a bug to have this added to developer.meego.com, or add the link to a "Proposed content" wiki page
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) Bob has some material that he will review with 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 (doublecheck with Ville and Maurice), performance tools, WRT 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). Possibly also OpenGL ES 1.x, 2.1 . "MeeGo Advanced API" (platform API): gstreamer, pulseaudio
- look-and-feel to be tested with Drupal site
- Need to follow-up on platform API. How will it be presented.
- Titta: we should be able to freeze API content for 1.1 on week 40
- 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 -> decision: move to developer.meego.com. Find a new owner for this content?
- 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)