SDK/Documentation/MeetingMinutes/20110120

Revision as of 08:29, 18 January 2011

This is the proposed agenda for the Documentation status meeting of week 3. After the meeting the agenda will be updated accordingly, and this page will include the minutes for the meeting.

Attendees

Agenda

• Assigned responsibilities for documentation-related features listed in Bugzilla for MeeGo 1.2 SDK release.

-> Are these OK with the team members?

• Getting help from the MeeGo Community on documentation related issues: OBS instructions, sample applications -> how to get this started?
• Architecture documentation status (publishing of docs?)
• MeeGo SDK features for documentation -> should we list these under Tools or components?
• API categories, proposal compiled by Sakari Poussa and Janne Sormunen.
• Owner for Platform API?

Content areas (according to features in Bugzilla)

//division into categories ongoing// Here is the initial suggestion for the divisions of content areas by Taru: New documentation

• 9486 Publishing instructions: How to publish software.
  • Responsibility for this area: Taru/Elliot/Community
• 9488 Netbook UX guidelines: User experience documentation for the netbook vertical.
  • Responsibility for this area: Elliot?

Updated documentation

• • Responsibility for this area: Taru
• 9487 Handset UX guidelines: User experience documentation for the handset vertical.
  • Responsibility for this area: Ronan
• 9489 Architectural overview: Architectural overview of the MeeGo software platform.
  • Responsibility for this area: Taru
• 9490 API reference (MeeGo API): API reference documentation for the future-proof MeeGo API interfaces.
  • Responsibility for this area: Murali/Janne?
• 9491 API reference (Platform API): API reference documentation for the potentially unstable platform interfaces.
  • Responsibility for this area: ?
• 9492 Sample Applications: IDE shall provide a set of sample applications. Each sample shall be buildable using both the application SDK and an OBS instance, each sample shall be usable on the supported set of execution environments (with deficiencies explicitly listed, if some functionality is not available). Each sample shall be covered with a license that enables building both open source and commercial software based upon it.//Should this be divided into four features: Example applications from community, sample applications included in the IDE, and tutorials for both?//
  • Responsibility for this area: Ville/Community/?
• 9493 Other documentations: Shall provide some documents like How to install and setup SDK, 'Hello World", Sample applications, FAQ, Debuging and performance tunning, How to build MeeGo image/QEMU image: To be divided into separate features to facilitate tracking?

  //(should this be divided into several features)?//

  • Responsibility for this area: Taru and Elliot
• 12241 Glossary: Create a glossary with relevant terms for MeeGo 1.2 SDK. Use the Glossary for MeeGo 1.1 (http://wiki.meego.com/SDK/Docs/1.1/Terminology) as the basis and update accordingly. //added by Taru on 11 January.//
  • Responsibility for this area: Taru
• 12461 Release notes: Create release notes that describe the contents of MeeGo 1.2 SDK. The release notes will be published on the http://meego.com web site.
  • Responsibility for this area: Veli, Bob
• 12462 Troubleshooting: Provide useful tips and solutions to potential problems that application developers may face when using MeeGo 1.2 SDK.
  • Responsibility for this area: Taru and Elliot
• 12463 Links to relevant Qt documentation: Add links to relevant sections of Qt documentation (especially tutorials and similar material) in the MeeGo 1.2 developer documentation in MeeGo Wiki.
  • Responsibility for this area: Taru
• 12464 MeeGo development best practices (community): Provide developers with practical instructions for developing applications with MeeGo 1.2 SDK. There could be tips and advice e.g. on performance, power management, backup and restore, testing, packaging guidelines, and UI implementation.
  • Responsibility for this area: Taru and Ville

New features to be added

• Download site
  • Responsibility for this area: Veli, Bob
• Using OBS server through Web interface (community) ): To be discussed with Tero Kojo what would be the best way to kick-start the cooperation with the community.
  • Responsibility for this area: Taru (with Tero Kojo)
• WRT instructions (is this needed?) - not really core, as WRT is a platform API and effectively deprecated for MeeGo -- Elliot Smith 11:26, 12 January 2011 (UTC)
  • Responsibility for this area: Elliot?
• Qt Simulator instructions (is this needed?)
  • Responsibility for this area: Elliot?