m (→Backlog) |
m (→Planning and status) |
||
| Line 38: | Line 38: | ||
Release planning is ongoing. Content areas and their owners are listed below: | Release planning is ongoing. Content areas and their owners are listed below: | ||
| + | |||
* Terminology/glossary (Titta) | * Terminology/glossary (Titta) | ||
* Release overview, description of the developer offering (Ronan) | * Release overview, description of the developer offering (Ronan) | ||
* Overview of MeeGo websites and their purpose (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 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) | * 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) | * Architecture overview (Titta) | ||
** Sunil / Arjan and Sakari updating. Representation changing. | ** 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) | * 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. | ** Need to follow-up on platform API. How will it be presented. | ||
| - | * UI guidelines | + | ** 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 [http://meego.com/developers/ui-design-guidelines/handset 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)) | * 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.) | * Packaging and publishing (covered in other tool instr.) | ||
* Release notes (Veli, Bob) | * Release notes (Veli, Bob) | ||
* Productization (covers all areas to some extent, but should this be a separate item?) (Titta, Ville) | * Productization (covers all areas to some extent, but should this be a separate item?) (Titta, Ville) | ||
| - | |||
== Things we need on this page == | == Things we need on this page == | ||
Contents |
MeeGo documentation team is a subteam of the MeeGo SDK team. The MeeGo SDK Documentation Team is responsible of providing documentation about developing for MeeGo platform.
Currently, content planning is carried out in wiki.meego.com: Information structure. Note that the plan is subject to change.
For MeeGo 1.2 release, documentation team will move to using Bugzilla/Featurezilla in tracking release content.
Release content was initially divided into content areas, each with an owner. Content area owners are responsible for planning the content needs of their area.
A buffer of two weeks before a release must be reserved for:
//More information about testing and review process to be added, later.//
This section will later include a backlog for following the MeeGo 1.1 documentation requirements and status.
Release planning is ongoing. Content areas and their owners are listed below: