Meego Wiki
Views

SDK/Documentation/MeetingMinutes/20110112

From MeeGo wiki
< SDK | Documentation | MeetingMinutes(Difference between revisions)
Jump to: navigation, search
(→Content areas (according to features in Bugzilla))
(→Content areas (according to features in Bugzilla))
 
(19 intermediate revisions not shown)
Line 1: Line 1:
==Attendees==
==Attendees==
 +
 +
Bob Spencer, Taru Laine, Titta Väyrynen, Veli Kaksonen.
==Agenda==
==Agenda==
Line 7: Line 9:
* Architecture documentation status (publishing of docs?)
* Architecture documentation status (publishing of docs?)
* Assigining responsibilities on SDK content areas
* Assigining responsibilities on SDK content areas
 +
* MeeGo SDK 1.1.2 status: comments on release notes needed, blog post to be created
 +
-> Taru to send the blog post and release notes for review after the meeting.
 +
* Day and time for the weekly meeting:
 +
Taru's suggestion: Thursday at this same time?
=== Content areas (according to features in Bugzilla) ===
=== Content areas (according to features in Bugzilla) ===
Line 12: Line 18:
Question: are we talking about updates, or are these new docs people are requesting? Many of these areas are covered in the SDK docs for 1.1; API refs are on apidocs.meego.com; some docs are elsewhere in the wiki but could be brought into the MeeGo SDK 1.2 TOC. It may be worth discriminating three cases by adding more comments to the bugs: (1) new content; (2) updates to existing content; (3) migration of content to the Developer Guide. -- [[User:Elliot|Elliot Smith]] 11:20, 12 January 2011 (UTC)
Question: are we talking about updates, or are these new docs people are requesting? Many of these areas are covered in the SDK docs for 1.1; API refs are on apidocs.meego.com; some docs are elsewhere in the wiki but could be brought into the MeeGo SDK 1.2 TOC. It may be worth discriminating three cases by adding more comments to the bugs: (1) new content; (2) updates to existing content; (3) migration of content to the Developer Guide. -- [[User:Elliot|Elliot Smith]] 11:20, 12 January 2011 (UTC)
-
Below listing has been taken from MeeGo 1.2 developer documentation related features in Bugzilla:
+
Note: There is a Documentation component for the MeeGo SDK product, which I'd suggest we use for any documentation bugs; some of the below are filed under Tools, which makes them difficult to find. -- [[User:Elliot|Elliot Smith]] 11:33, 12 January 2011 (UTC)
 +
 
 +
Below listing has been taken from MeeGo 1.2 developer documentation related features in Bugzilla. At the meeting we decided that Taru can start assigning the features to the responsible persons.
 +
 
 +
Here is the initial suggestion for the divisions of content areas by Taru:
* 9479 Developer documentation: Appropriate documentation shall be provided to developers
* 9479 Developer documentation: Appropriate documentation shall be provided to developers
-
** Responsibility for this area:  
+
** Responsibility for this area: Taru
* 9480 Getting started with MeeGo application development: Introductory document for getting started with development.
* 9480 Getting started with MeeGo application development: Introductory document for getting started with development.
-
** Responsibility for this area:  
+
** Responsibility for this area: Ronan
* 9481 Installation instructions (OBS): How to install an OBS server & client.
* 9481 Installation instructions (OBS): How to install an OBS server & client.
-
** Responsibility for this area: OBS server is probably out of scope (but covered by [[OBS setup]] anyway); client docs exist already (incomplete) - [[Build Infrastructure]] -- [[User:Elliot|Elliot Smith]] 11:14, 12 January 2011 (UTC)
+
** Responsibility for this area: Community/Elliot
 +
**: OBS server is probably out of scope (but covered by [[OBS setup]] anyway); client docs exist already (incomplete) - [[Build Infrastructure]] -- [[User:Elliot|Elliot Smith]] 11:14, 12 January 2011 (UTC)
* 9482 Installation instructions (application SDK): How to install the application SDK.
* 9482 Installation instructions (application SDK): How to install the application SDK.
-
** Responsibility for this area:  
+
** Responsibility for this area: Taru for Linux and Elliot for Windows
* 9483 Device provisioning instructions: How to take a device into use as a development target.
* 9483 Device provisioning instructions: How to take a device into use as a development target.
-
** Responsibility for this area:
+
** Responsibility for this area: Elliot for Netbook and Taru for handset
* 9484 Packaging instructions (OBS): How to package an application in the OBS.
* 9484 Packaging instructions (OBS): How to package an application in the OBS.
-
** Responsibility for this area: see [[Build Infrastructure]] -- [[User:Elliot|Elliot Smith]] 11:20, 12 January 2011 (UTC)
+
** Responsibility for this area: Community/Elliot
 +
** see [[Build Infrastructure]] -- [[User:Elliot|Elliot Smith]] 11:20, 12 January 2011 (UTC)
* 9485 Packaging instructions (application SDK):How to package an application in the application SDK.
* 9485 Packaging instructions (application SDK):How to package an application in the application SDK.
-
** Responsibility for this area:  
+
** Responsibility for this area: Taru
* 9486 Publishing instructions: How to publish software.
* 9486 Publishing instructions: How to publish software.
-
** Responsibility for this area:  
+
** Responsibility for this area: Taru/Elliot/Community
* 9487 Handset UX guidelines: User experience documentation for the handset vertical.
* 9487 Handset UX guidelines: User experience documentation for the handset vertical.
-
** Responsibility for this area:  
+
** Responsibility for this area: Ronan
* 9488 Netbook UX guidelines: User experience documentation for the netbook vertical.
* 9488 Netbook UX guidelines: User experience documentation for the netbook vertical.
** Responsibility for this area: Elliot?
** Responsibility for this area: Elliot?
* 9489 Architectural overview: Architectural overview of the MeeGo software platform.
* 9489 Architectural overview: Architectural overview of the MeeGo software platform.
-
** Responsibility for this area:  
+
** Responsibility for this area: Taru
* 9490 API reference (MeeGo API): API reference documentation for the future-proof MeeGo API interfaces.
* 9490 API reference (MeeGo API): API reference documentation for the future-proof MeeGo API interfaces.
-
** Responsibility for this area:  
+
** Responsibility for this area: Murali/Janne?
* 9491 API reference (Platform API): API reference documentation for the potentially unstable platform interfaces.
* 9491 API reference (Platform API): API reference documentation for the potentially unstable platform interfaces.
-
** Responsibility for this area:  
+
** 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.
+
* 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?
+
** 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?
* 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)?//
 +
** I suggest we decide a set of "other" docs we need or would like, then prioritise them - at the moment I don't really have a feel for what's missing, what we think is important to developers, what's going to migrate from Nokia's site or internal processes, what content developer.meego.com will have etc.; on the other hand, I do have a good idea what's on the wiki -- [[User:Elliot|Elliot Smith]] 10:45, 17 January 2011 (UTC)
** Responsibility for this area: Taru and Elliot
** 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.//  
* 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
** Responsibility for this area: Taru
-
+
 
=== New features (to be added to Bugzilla during week 2) ===
=== New features (to be added to Bugzilla during week 2) ===
* Release notes
* Release notes
Line 53: Line 67:
* Troubleshooting  
* Troubleshooting  
** Responsibility for this area: Taru and Elliot
** Responsibility for this area: Taru and Elliot
-
* Glossary
 
-
** Responsibility for this area: Taru
 
* 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.
* 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)
** Responsibility for this area: Taru (with Tero Kojo)
Line 65: Line 77:
* Qt Simulator instructions (is this needed?)
* Qt Simulator instructions (is this needed?)
** Responsibility for this area: Elliot?
** Responsibility for this area: Elliot?
 +
 +
 +
===Other issues===
 +
 +
* API categories, proposal compiled by Sakari Poussa and Janne Sormunen.
 +
* Owner for Platform API: To be discussed with Murali and then decided
 +
* Additional doc team members? -> Bob to revisit if we notice more people are needed.
===Live BugzillaReports on SDK docs features===
===Live BugzillaReports on SDK docs features===
-
It is possible to show a live lookup of SDK docs in the wiki: view the page source to see the required code.
+
It is possible to show a live lookup of SDK docs issues in the wiki: view the page source to see the required code (some of the arguments may still need to be tweaked).
 +
 
 +
====Features====
 +
 
 +
{{#bugzilla:
 +
  |columns=id,status,to,severity,version,summary
 +
  |component=Documentation,Tools
 +
  |product=MeeGo SDK features
 +
  |status=NEW,NEEDINFO,ASSIGNED,REOPENED,ACCEPTED
 +
  |lastcomment=1
 +
}}
 +
 
 +
====Bugs====
{{#bugzilla:
{{#bugzilla:

Latest revision as of 10:45, 17 January 2011

Contents

Attendees

Bob Spencer, Taru Laine, Titta Väyrynen, Veli Kaksonen.

Agenda

  • Documentation-related features listed in Bugzilla for MeeGo 1.2 SDK release.
  • 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?)
  • Assigining responsibilities on SDK content areas
  • MeeGo SDK 1.1.2 status: comments on release notes needed, blog post to be created

-> Taru to send the blog post and release notes for review after the meeting.

  • Day and time for the weekly meeting:

Taru's suggestion: Thursday at this same time?

Content areas (according to features in Bugzilla)

Question: are we talking about updates, or are these new docs people are requesting? Many of these areas are covered in the SDK docs for 1.1; API refs are on apidocs.meego.com; some docs are elsewhere in the wiki but could be brought into the MeeGo SDK 1.2 TOC. It may be worth discriminating three cases by adding more comments to the bugs: (1) new content; (2) updates to existing content; (3) migration of content to the Developer Guide. -- Elliot Smith 11:20, 12 January 2011 (UTC)

Note: There is a Documentation component for the MeeGo SDK product, which I'd suggest we use for any documentation bugs; some of the below are filed under Tools, which makes them difficult to find. -- Elliot Smith 11:33, 12 January 2011 (UTC)

Below listing has been taken from MeeGo 1.2 developer documentation related features in Bugzilla. At the meeting we decided that Taru can start assigning the features to the responsible persons.

Here is the initial suggestion for the divisions of content areas by Taru:

  • 9479 Developer documentation: Appropriate documentation shall be provided to developers
    • Responsibility for this area: Taru
  • 9480 Getting started with MeeGo application development: Introductory document for getting started with development.
    • Responsibility for this area: Ronan
  • 9481 Installation instructions (OBS): How to install an OBS server & client.
    • Responsibility for this area: Community/Elliot
      OBS server is probably out of scope (but covered by OBS setup anyway); client docs exist already (incomplete) - Build Infrastructure -- Elliot Smith 11:14, 12 January 2011 (UTC)
  • 9482 Installation instructions (application SDK): How to install the application SDK.
    • Responsibility for this area: Taru for Linux and Elliot for Windows
  • 9483 Device provisioning instructions: How to take a device into use as a development target.
    • Responsibility for this area: Elliot for Netbook and Taru for handset
  • 9484 Packaging instructions (OBS): How to package an application in the OBS.
  • 9485 Packaging instructions (application SDK):How to package an application in the application SDK.
    • Responsibility for this area: Taru
  • 9486 Publishing instructions: How to publish software.
    • Responsibility for this area: Taru/Elliot/Community
  • 9487 Handset UX guidelines: User experience documentation for the handset vertical.
    • Responsibility for this area: Ronan
  • 9488 Netbook UX guidelines: User experience documentation for the netbook vertical.
    • Responsibility for this area: Elliot?
  • 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)?//
    • I suggest we decide a set of "other" docs we need or would like, then prioritise them - at the moment I don't really have a feel for what's missing, what we think is important to developers, what's going to migrate from Nokia's site or internal processes, what content developer.meego.com will have etc.; on the other hand, I do have a good idea what's on the wiki -- Elliot Smith 10:45, 17 January 2011 (UTC)
    • 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

New features (to be added to Bugzilla during week 2)

  • Release notes
    • Responsibility for this area: Veli, Bob
  • Download site
    • Responsibility for this area: Veli, Bob
  • Troubleshooting
    • Responsibility for this area: Taru and Elliot
  • 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)
  • Links to relevant Qt documentation.
    • Responsibility for this area: Taru
  • MeeGo development best practices (community)
    • Responsibility for this area: Taru and Ville
  • 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?


Other issues

  • API categories, proposal compiled by Sakari Poussa and Janne Sormunen.
  • Owner for Platform API: To be discussed with Murali and then decided
  • Additional doc team members? -> Bob to revisit if we notice more people are needed.

Live BugzillaReports on SDK docs features

It is possible to show a live lookup of SDK docs issues in the wiki: view the page source to see the required code (some of the arguments may still need to be tweaked).

Features

IDStatusAssigneeSeverityVersionSummary (126 tasks) ⇒
9479*
9479 Setting for release planning.
ACCEPTEDmariannelvenhancement1.2[FEA] Developer documentation
9480*
9480 Having both of these guides seems redundant, so perhaps they can be merged into one, taking the important bits of both, like here at developer.meego.com: http://developer.meego.com/guides/getting-started/meego-application-development-process
?		ACCEPTEDmacronenhancement1.2[FEA] Getting started with MeeGo application development
9481*
9481

This should be scoped to installing osc (the command line client), probably adequately covered here: http://wiki.meego.com/Build_Infrastructure/Packagers_Developers/CLI_Part_1

We don't want to explain setting up an OBS server.

It is related to #9484.
ACCEPTEDelliotenhancement1.2[FEA] Installation instructions (OBS)
9482*
9482

The responsibilities for this feature are divided as follows: Supported guest operating system: Bob Spencer Installing and configuring MeeGo SDK for Linux: Elliot Smith Checking your system's graphics capabilities: Bob Spencer Installing and configuring MeeGo SDK for Windows: Max Yu

Setting up the emulator: Elliot Smith
?		ACCEPTEDbspencerenhancement1.2[FEA] Installation instructions (application SDK)
9483*
9483

Instruction for setting up the handset is now ready at:

http://wiki.meego.com/SDK/Docs/1.2/Setting_up_handset
?		ACCEPTEDbspencerenhancement1.2[FEA] Device provisioning instructions
9484*
9484

The OBS content is at: http://wiki.meego.com/Build_Infrastructure/Packagers_Developers

But part 3 of this links out to an openSUSE page on OBS (http://en.opensuse.org/openSUSE:OSC). This makes it inconsistent with parts 1-2 and 4; also, an openSUSE page is obviously not tailored to MeeGo.

I'd say this is still a gap, but I may not get round to filling it.
ACCEPTEDelliotenhancement1.2[FEA] Packaging instructions (OBS)
9485*
9485

We need at least basic guidelines and a pointer to the compliance recommendations.

Mats Wichmann (Intel SDK team) can help along with John Chen
ACCEPTEDmwichmannenhancement1.2[FEA] Packaging instructions (application SDK)
9486*
9486 Initial content with summary and links to currently open or planned vendor developer areas (where more instructions can be found). Also link to open-source repository apps.meego.com (work in progress). Are the current instructions sufficient for MeeGo 1.2 SDK? Can be completed by MeeGo 1.2 SDK release.
ACCEPTEDbspencerenhancement1.2[FEA] Publishing instructions
9487*
9487 Needs to be reassigned in Bugzilla.
ACCEPTEDbspencerenhancement1.2[FEA] Handset UX guidelines
9488*
9488

(In reply to comment #3)

Not that I'm aware of. I also checked with Chris Liu (who heads the design team in London which worked on netbook) and he said they don't exist and aren't likely to any time soon.
ACCEPTEDrbradfordenhancement1.2[FEA] Netbook UX guidelines
9489*
9489 Assigning to an architect. Arjan and Sunil to define. Bob to help document as needed.
?		ACCEPTEDsunilsaxenaenhancement1.2[FEA] Architectural overview
9490*
9490 Assigned to Taru.
?		ACCEPTEDkrishmuenhancement1.2[FEA] API reference (MeeGo API)
9491*
9491 Assigned to Taru.
?		ACCEPTEDkrishmuenhancement1.2[FEA] API reference (Platform API)
2681*
2681 The feature's description has been updated.
ACCEPTEDvelienhancement1.2[FEA] MeeGo SDK
9398*
9398 Linux and Windows are available. TBD: Mac OS X.
ACCEPTEDvelienhancement1.2[FEA] OBS host support
9400*
9400 Is OBS already supported on Windows?
ACCEPTEDmaxayuenhancement1.2[FEA] OBS on Windows
9401*
9401

Re-assign it to Bob. Bob may re-assign it to TBH.

Thanks,

Max
ACCEPTEDbspencerenhancement1.3[FEA] OBS on Mac OS X
9403*
9403 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Integrated development environment
9404*
9404 Setting for release planning.
ACCEPTEDmauricekenhancement1.2[FEA] Qt SDK
9405*
9405 I think it also depends on how you define "supported". At least for now there are changes in the MeeGo.com Creator, which are not available / compatible with the vanilla one. Those need to get integrated to enable support. But this is in relation to another task.
ACCEPTEDmauricekenhancement1.2[FEA] Qt SDK version
9412*
9412 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] SDK update information
9413*
9413 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] SDK installed tools information
9414*
9414 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] SDK installation log
9415*
9415 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] SDK extensibility
9416*
9416 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Development devices management
9417*
9417 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Firmware query
9418*
9418

Does this feature mean that there is a tool to flash the device? If yes, what is this tool called?

Or does the feature mean this:

http://meego.com/devices/handset/installing-meego-nokia-n900
ACCEPTEDbspencerenhancement1.3[FEA] Flashing in device management tool
9419*
9419 This FEA# was listed in aegis-certman (mssf-certman) which was pushed into Trunk on the 12th of Dec. But the release field says this is for 1.3?? If the releases is corrected this might be set as released.
ACCEPTEDbspencerenhancement1.3[FEA] Certificate handling in device management tool
9420*
9420 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device management log
9421*
9421 Can you please elaborate...
ACCEPTEDbspencerenhancement1.2[FEA] Device provisioning tool
9423*
9423 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Project templates
9426*
9426 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] multiple builds
9427*
9427

Did we have any good solutions available for this? What is the status?

My suggestion is that we study the possibility to remove sysroots as they are today and introduce a new way of creating a sysroot from Qemu/device images with e.g. rsync. This would mean that the developer boots the Qemu or device and uses predefined rsync command which copies the needed files to the host system from the target. For performance purposes we could of course do that on our build servers and provide installable sysroots. Syncing one library should be pretty fast. This would anyhow mean that we would not need any additional components for extending the sysroots.

Advantages of this solution: 1) No need for building sysroots with OBS 2) No need for additional error prone tools for updating the sysroots (just use target package management system)

Disadvantages of this solution:

1) It is probably a bit slower to install new packages as the developer needs to boot Qemu or device for that. Anyhow maybe we could have a possibility to boot Qemu without UI and thus get it up pretty fast.
ACCEPTEDwwhbuaaenhancement1.2[FEA] sysroot extension
9430*
9430

Documentation should be available inside Qt Creator.

Documentation is also available on the website.
ACCEPTEDbspencerenhancement1.2[FEA] API documentation
9432ACCEPTEDmauricekenhancement1.2[FEA] QML development
9433*
9433

I have small query

Other than arm and ia32 ,what are the other CPU architectures?
ACCEPTEDvelienhancement1.2[FEA] Build for supported architectures
9438*
9438 Setting for release planning.
ACCEPTEDvelienhancement1.2[FEA] Debug
9440*
9440

The Debugging Framework inside Qt Creator already allows to implement additional debugger backends. So the questions rather are:

- Which ones are missing?

- Who is implementing those?
ACCEPTEDmauricekenhancement1.2[FEA] Additional debuggers
9442*
9442 Setting for release planning.
ACCEPTEDhaitaoenhancement1.2[FEA] System QEMU as target
9445*
9445 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Chroot/xephyr
9448*
9448 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Multi-target connectivity
9449*
9449 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Multi-QEMU connectivity
9450*
9450 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Testing
9451*
9451 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Performance tunning tools
9452*
9452 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Unit test automation
9453*
9453 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Compliance checher tool
9454*
9454

I'm trying to do test case about this feature and I need more information about it.

How logs should be easily browsed? By QT creator or something else?
ACCEPTEDbspencerenhancement1.2[FEA] Device log access
9455*
9455 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] tcpdump
9456*
9456

We can promote open source tool and provide a wiki tutorial.

DPD is working on formal tools for MeeGo in 1.3 timeframe.
ACCEPTEDbspencerenhancement1.2[FEA] memory profiler
9457*
9457 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] energy profiler
9458*
9458 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Publish
9459*
9459 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] IDE Plugins
9460*
9460 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] IDE plugin framework
9462*
9462 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] MADDE plugin
9463*
9463 Setting for release planning.
ACCEPTEDjohnchenenhancement1.3[FEA] IDE/OBS cross-use
9464*
9464 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Oprofile-plugin
9465*
9465 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] valgrind-plugin
9466*
9466 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] flasher-plugin
9467*
9467 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] platform security tools
9468*
9468 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] store submission plugin
9469*
9469 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] compliance checker plugin
9470*
9470 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Project template for IDE plugin
9471*
9471

Could you please specify what vanilla Qt SDK means ( the content of vanilla Qt SDK)? like which version of Qt Creator to be included. (In reply to comment #3)

> Please, move the feature for MeeGo 1.3.
ACCEPTEDfaboenhancement1.2[FEA] use vanilla Qt SDK
9472*
9472 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] IDE agnosticity
9475ACCEPTEDbspencerenhancement1.2[FEA] Application SDK host support
9476ACCEPTEDbspencerenhancement1.2[FEA] Application SDK on Linux
9477*
9477 Assigning to Ville.
ACCEPTEDlavonardoenhancement1.2[FEA] Application SDK on Windows
9478*
9478

Bob,

How about I to piolot it first before TBH onboard? I have just built an ARM tool chain, host as Mac OS X. I will test it as soon as I get a system from Kerry.

Thanks,

Max
ACCEPTEDbspencerenhancement1.3[FEA] Application SDK on Mac OS X
9492*
9492

Hi ,

Can u please elloberate the functionality .

and also i have a small query , so each sample applications should be licensed ?
ACCEPTEDdlawlorenhancement1.2[FEA] Sample Applications
9494*
9494 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device Simulation
9495*
9495 Do we need to support both GL ES 1.1 and ES 2.0?
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - OpenGL ES 1.1
9496*
9496 Setting for release planning.
ACCEPTEDhaitaoenhancement1.2[FEA] Device simulation - OpenGL ES 2.0
9497*
9497 GL has gone and been replaced with GL ES
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - other OpenGL versions
9498*
9498 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Keyboard / Kpad / DPad / Trackball / Platform buttons / Mouse
9499*
9499 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Touchscreen
9500*
9500 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Multitouch
9501*
9501 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Landscape and portrait modes
9502*
9502 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Screen Rotation
9503*
9503 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Audio
9504*
9504 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Network
9505*
9505 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Battery level & charging
9506*
9506 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Camera (still images)
9507*
9507 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Camera (video capture)
9508*
9508 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Bluetooth
9509*
9509 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - GPS
9510*
9510 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Telephony
9511*
9511 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Incoming calls
9512*
9512 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Incoming SMS
9513*
9513 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Device simulation - Incoming email
9514*
9514 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device simulation - CF/SD/MSP/XD, including plug-in/pull-out
9515*
9515 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device simulation - USB connectivity
9516*
9516 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device simulation - Flexible Resolutions
9517*
9517 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device simulation - Sensors
9518*
9518 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device simulation - Accelerometer
9519*
9519 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device simulation - Magnetometer
9520*
9520 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device simulation - Ambient light
9521*
9521 Setting for release planning.
ACCEPTEDbspencerenhancement1.3[FEA] Device simulation - Gyroscope
9522*
9522 Setting for release planning.
ACCEPTEDjuntianenhancement1.2[FEA] Device skins
9402*
9402 Need more information regarding all talks in the workflow (what are the tasks involved in workflow).
REOPENEDvelienhancement1.2[FEA] Command line environment
8469*
8469 Move to MeeGo feature list
NEWbspencerenhancement1.2[FEA] Feature request about "Delete Project" in Qt Creator
8470*
8470

http://meego.gitorious.org/meego-developer-tools/madde/commit/4c20f636e3afe2a85d6f8de58bde9c1d18860c31

fixes this bug ('mad-admin remove (-f|-n) all' implemented).

I cannot change 'Status:' though.
NEWtooenhancement1.2[FEA] Remove all the targets/runtimes with one mad-admin command
12241*
12241 Ongoing, terms need to be added and definitions modified according to current SDK content. Can be completed by MeeGo 1.2 SDK release.
ACCEPTEDmariannelvenhancementunspecified[FEA] Glossary for MeeGo 1.2 SDK
12461*
12461 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.
?		ACCEPTEDvelienhancementunspecified[FEA] Release notes for MeeGo 1.2 SDK
12462*
12462 Good idea. We should have a community troubleshooting page.
ACCEPTEDbspencerenhancementunspecified[FEA] Troubleshooting information for MeeGo 1.2 SDK
12463*
12463 Not started. -> can this be moved to a later MeeGo SDK release?
ACCEPTEDtarulaineenhancementunspecified[FEA] Linking from MeeGo 1.2 SDK developer documentation to relevant Qt documentation
12464*
12464 Ongoing. Planned to be completed by MeeGo 1.2 SDK release.
ACCEPTEDtarulaineenhancementunspecified[FEA] Best practices documentation for MeeGo 1.2 SDK
12788*
12788 Create a page that provides developers with links to the SDK and other relevant installers.
?		ACCEPTEDbspencerenhancementunspecified[FEA] Download site for MeeGo 1.2 SDK
13215*
13215

Nokia has opened, packaged and integrated the Policy framework into the MeeGo images, and now apps like dialer, music and video must port/integrate with it. This will be done by linking with and calling into libresourceqt.

Source repo for the project is at: http://meego.gitorious.org/maemo-multimedia/libresourceqt

The MeeGo package that contains the docs can be installed with the following command:

  1. zypper in libresourceqt-devel
ACCEPTEDbspencerenhancementunspecified[FEA] Add libresourceqt API docs
14994*
14994

(In reply to comment #3) > (In reply to comment #2) > > > Dominig, does that have something to do with this request to put the API > > documentation online? > > What I wanted to say is that having the input method documentation made > independent of the touch framework would be the first step to get it reuse by > other MeeGo vertical which would not use the touch framework. > > -- Dominig That has already happened :) www.maliit.org

Announcement: http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html
ACCEPTEDbspencerenhancementunspecified[FEA] API reference for Meego Input Methods for 1.2 (platform)
15307*
15307

Below link contains the instructions to convert normal images to the one that could be used by QEMU for 1.1 release:

http://wiki.meego.com/SDK/Docs/1.1/Building_QEMU_Tools

1.2 release will add the description for Tablet I guess.
?		ACCEPTEDkarimianenhancementunspecified[FEA] Instructions for building MeeGo image/QEMU image
15308*
15308 Create instructions for debugging Qt applications running on a remote MeeGo device, using Qt Creator.
?		ACCEPTEDelliotenhancementunspecified[FEA] Debugging instructions for MeeGo 1.2 SDK
15310*
15310 How do we handle this feature?
?		ACCEPTEDdlawlorenhancementunspecified[FEA] Creating a Hello world application
5661*
5661 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] Maintaining of tools
5936*
5936 Setting for release planning.
ACCEPTEDbspencerenhancement1.2[FEA] System mode QEMU
11386*
11386

I get the message blew too: Starting QEMU runtime meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime This may take some time ...

but I had qemu-gl installed and in my PC /usr/lib/madde/linux-i686/runtimes/meego-handset-ia32-qemu-1.1.2-runtime/information contains : 

 1 qemu='/usr/lib/madde/linux-i686/tools/qemu-meego/bin/qemu-meego'
 2 qemu_path_native='/usr/lib/madde/linux-i686/tools/qemu-meego/bin/qemu-meego'
 3 libpath='LD_LIBRARY_PATH=/usr/lib/madde/linux-i686/tools/qemu-meego/lib'
 4 qemu_args='-hda meego-handset-ia32-qemu-1.1.20110110.1026-sda.raw -name      MeeGo -m 1024 -boot c -enable-kvm -vga std -enable-gl -device virtio-gl-p    ci -soundhw ac97 -skin /opt/meego/qemu-gl/share/qemugl/meego/skin/handset/skin.xml -usbdevice tablet -net nic -net user,hostfwd=tcp:127.0.0.1:666   6-:22,hostfwd=tcp:127.0.0.1:13219-:13219,hostfwd=tcp:127.0.0.1:14168-:14168'
 5 ip='127.0.0.1'
 6 sshport='6666'
 7 redirport2='13219'
 8 redirport3='14168'

not same as yours.

And when I try to run qemugl like : sudo /opt/meego/qemu-gl/bin/qemugl I get

Could not initialize SDL - exiting

What should I do ? Thanks.
NEWzhiyuanenhancementunspecified[FEA] Madde/QT Creator should report error if QEMU was not started successfully
11644*
11644 Moving to SDK Features context
NEWbspencercriticalunspecified[FEA] Request enable USB ethernet driver for real device debugging in MeeGo SDK
12794*
12794

BUILD IMAGE meego-sdk-1.2-0123-2

HARDWARE MODEL: Windows XP, 32 bit

BUG DETAILED DESCRIPTIONS
===========================================================
Once you install the meego-sdk executable package you cannot just execute the QtCreator and start developing application. You need to enter the command-line and start downloading sysroot and run-environments

EXACT STEPS LEADING TO PROBLEM:
===========================================================
1. Install meego-sdk by using the executable file 2. Open QtCreator


EXPECTED OUTCOME:
===================
You should have a GUI menu which you can use to install/remove sysroots/targets rather than having to use the command-line strictly.

ACTUAL OUTCOME:
===================
No such menu exists

USER IMPACT:
===================

Users cannot use the QtCreator directly, they need to read the tutorial and enter command-line. Otherwise they won't know why it does not work (make command fails)
NEWlavonardoenhancementunspecified[FEA] Possibility of installing sysroot/run-environment from QtCreator GUI interface
13086*
13086

Compiling MTF Applications for the Qt Simulator is out of scope. Qt Components should rather be the way to create your applications.

Also note that MTF is not part of the core API set.
NEWmauriceknormalunspecified[FEA] Qt Simulator doesn't support MTF applications
13148*
13148

Hmm

I have to check the behaviour...

Yes. files paths must start with / (if not, ignored silently :( )

I think the glob patterns are not fully accepted, but just plain '*'.

I'll check and fix these (in near future).
NEWtoomajorunspecified[FEA] The rrpmbuild script should be able to figure out which files to put into the package.
13159*
13159

BUG DETAILED DESCRIPTIONS
===========================================================
EXACT STEPS LEADING TO PROBLEM: (Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message Connection Failed appears))
===========================================================
1. Install Meego SDK 2. Install Intel AppUP cross compiler (we did this on a Linux host) 3. Start Qt Creator by executing /opt/intel/appup-meego-tools/icc-meego-<version>/bin/launch_sdk.sh (this sets the environment for icc) 4. Build a default Meego Touch Framework Application w/ default g++ - this should work. 5. Switch to the Intel compiler. Change the Build Settings->qmake command line and add -spec linux-icc-v12 6. Build with the Intel compiler. Rebuild All.


EXPECTED OUTCOME:
===================
Expected outcome is that compilation and rpm packaging should work.

ACTUAL OUTCOME:
===================
Instead: the compiler reports that it cannot find MApplication and compilation fails.

USER IMPACT:
===================
REPRODUCIBILITY: (always, less than 1/10, 5/10, 9/10)
=====================================
Always.

EXTRA SOFTWARE INSTALLED:
============================
Intel AppUP-MeeGo-Tools SDK

OTHER COMMENTS:
===================
The issue is that the sample has some include directories specified with the full path to the sysroot and some without. -I/usr/lib/madde/linux-i686/meego-tablet-ia32-madde-sysroot-1.1.80.9.20101207.1-fs/usr/include/qt4/QtCore for example has a full path (as do many others). -I/usr/include/meegotouch is specified, but really needs to be -I/usr/lib/madde/linux-i686/meego-tablet-ia32-madde-sysroot-1.1.80.9.20101207.1-fs/usr/include/meegotouch.

This may be a 'feature', but as an aside it leads to the fact that the pretty printer inside of Qt Creator doesn't know where the include is located. Notice the squiggly lines under the #include <MApplication> - this means Qt Creator doesn't know where the file is located and cannot do things like argument completion inside of the GUI.

The fix will most likely be one of two things: 1) Fix all of the samples/wizards so they use the full path or 2) help icc get all of these paths preprended the same way g++ is able to do so (something in Qt Creator's Toolchain class perhaps?).
NEWbspencercriticalunspecified[FEA] Meego API includes cannot be seen by Intel Compiler
13604*
13604

this feature is not implemented in mainstream project, see: http://bugreports.qt.nokia.com/browse/QTCREATORBUG-16

http://bugreports.qt.nokia.com/browse/QTCREATORBUG-3004
NEWbspencernormal1.3[FEA] User should be able to select entire folder or multiple files for removal
15979*
15979

BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - MeeGo SDK 1.3 preview

HARDWARE MODEL (on what HW this bug is uncovered): IA-32

BUG DETAILED DESCRIPTIONS
===========================================================
Feature Request for DPD Tools. The AppUp SDK Suite for MeeGo superinstaller will install a set of libraries, compiler qmake.conf, and library .prf files into defined locations of the sysroot. At installation time, we will do this for all sysroots already installed on the host.

When users employ MADDE (or the visual package manager) to install new sysroots to the host, we need a method of copying these same libs, qmake.conf, and .prf files to the newly installed sysroot.

DPD will provide a document specifying the precise files and default from/to locations of the files at a later agreed upon date.


EXPECTED OUTCOME:
===================
A design, agreement on design, schedule and implementation for the feature.

ACTUAL OUTCOME:
===================
USER IMPACT:
===================
Important. We desire a user invisible method for copying these files to new sysroots. A fallback is to provide a script that the user would manually invoke after adding a sysroot, however this is undesirable.

REPRODUCIBILITY: (always, less than 1/10, 5/10, 9/10)
=====================================
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:


===================
NEWbspencerenhancementunspecified[FEA] Support to copy DPD tools configuration to installed sysroot/toolchains
16564*
16564

BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - (e.g.: meego-netbook-ia32-1.0.90.0.20100831.1)):

HARDWARE MODEL (on what HW this bug is uncovered):

BUG DETAILED DESCRIPTIONS
===========================================================
EXACT STEPS LEADING TO PROBLEM: (Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message Connection Failed appears))
===========================================================
1.Current MeeGo SDK only provide the MADDE target and runtime image in tablet, handset and netbook. Customer can't run QEMU to simulate IVI home UX when they develop their application. 2. 3. 4. 5.

EXPECTED OUTCOME:
===================
Add IVI target and runtime image when using madde

ACTUAL OUTCOME:
===================
No image can't install relate to IVI

USER IMPACT:
===================
No Target to compile application within Qt creator, No image to run in QEMU simulate IVI home

REPRODUCIBILITY: (always, less than 1/10, 5/10, 9/10)
=====================================
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:


===================
NEWbspencerenhancementunspecified[FEA] Provide IVI target/runtime image in SDK
17968*
17968

DESCRIPTION OF FEATURE:
========================
AppUp SDK provides a set of head files and static libraries.

The Qt Creator of MeeGo SDK should be able to include and link to AppUp SDK header files and libraries which is NOT installed in MeeGo SDK target / sysroot folder.


DETAILED LIST OF PACKAGES:
===========================
PKG-NAME: PKG-VERSION: PKG-MAINTAINER: LICENSE: URL: SUMMARY DESCRIPTION:


OTHER COMMENTS:


===================
NEWbspencercriticalunspecified[FEA] Support interoperability with AppUp SDK which is NOT installed in target / sysroot folder

Bugs

no bugzilla tickets were found
Retrieved from "http://wiki.meego.com/SDK/Documentation/MeetingMinutes/20110112"
Personal tools