MeeGo wiki - User contributions [en]

User:Andre

2011-12-28T15:25:39Z

Andre:

=== About me ===

See https://live.gnome.org/AndreKlapper

=== MeeGo stuff ===

Random unfinished stuff I work(ed) on before MeeGo was dead:
* [[/Surrounds_Bugtracking]]
* [[/Bug_Summary_Prefixes]]

User:Andre

2011-11-10T21:24:29Z

Andre: update

=== About me ===

* Member of [http://wiki.meego.com/Error_Management MeeGo Error Management] and [http://bugs.maemo.org maemo.org] Bugmaster for [http://www.openismus.com/ Openismus GmbH]
* a [http://bugzilla.gnome.org GNOME Bugzilla] Maintainer, member of the [http://live.gnome.org/Bugsquad GNOME Bugsquad], [http://gnome.org/projects/evolution/ GNOME Evolution] Bugmaster Emeritus
* member of the [http://live.gnome.org/ReleasePlanning/ GNOME Release Team] (mostly QA and Schedule)
* member of the [https://live.gnome.org/TranslationProject/CoordinationTeam GNOME Translation Project Coordination team]
* member of the [http://l10n.gnome.org/languages/cs/ Czech GNOME translation team]
* main author and maintainer of the [http://library.gnome.org/users/evolution/3.2/ GNOME Evolution user documentation]
* yet another student

=== Contact ===
* IRC nickname on Freenode: andre__
* [http://blogs.gnome.org/aklapper My blog]

=== MeeGo stuff ===

Random unfinished stuff I work(ed) on (once ready for review it is moved to proper URLs):
* [[/Surrounds_Bugtracking]]
* [[/Bug_Summary_Prefixes]]

ARM/N900/QA

2011-09-19T15:18:12Z

Andre: Transfer useless image that only includes text into text

= Meego Community Edition Quality Assurance =
Quality Assurance for Meego [[ARM/N900|Community Edition.]] [[ARM/N900|Community Edition]] QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]] Monitoring the [[ARM/N900|Community Edition]] maturity is one of the main tasks of [[ARM/N900|Community Edition]] QA. The current maturity status can be found from the [[ARM/N900/Status|Status page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Pylkkä
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [[ARM/N900/Status|General CE N900 Feature status]]
* [[ARM/N900/QA/Performance|Performance results]]
* [http://qa-reports.meego.com/1.2/Handset/Dataflow/N900CE Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Key%20Feature Key Features reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [[MeeGo-Meeting_IRC_Schedule|MeeGo-Meeting IRC Schedule]]

N900 CE (Blocker) Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-09-15-07.03.html Meeting minutes 15-09-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-09-08-07.02.html Meeting minutes 08-09-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-09-01-07.03.html Meeting minutes 01-09-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-08-25-07.01.html Meeting minutes 25-08-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-08-11-06.57.html Meeting minutes 11-08-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-23-06.58.html Meeting minutes 23-06-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-19-06.59.html Meeting minutes 19-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

== Contact ==
* [http://lists.meego.com/listinfo/meego-qa QA-mailing list]
* join #meego-qa at freenode

= QA Tools =
Commumity Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - DONE (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - DONE (sampos)
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - DONE (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]
== Functional Testing ==
====Daily testing====

Acceptance/Sanity test is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in acceptance test reflects the most important and basic functionalities of the distribution. We do the acceptance test against Trunk:Testing repo.

*Acceptance (Trunk:Testing)

*Sanity (Trunk:Daily)

====Weekly testing====
This is QA weekly testing cycle for weekly images released by distribution team. Our testing focus would be *Key feature testing* to cover the key features and ensure MeeGo Handset UX delivered features are basically covered and major issues are exposed in timely fashion, as well as changes introduced from the last build do not break working features. The test covers UX and applications (MeeGo Audio player ,Video player, Dialer, SMS, fennec browser,VKB, Email, Photo Viewer, Calendar, IM and contacts, etc).

*Key Basic Testing

*Data Flow Testing

*Basic Feature Testing

==== Execution Process ====

[[File:Process.PNG]]
 

==== Testing images Community Edition image ====
[http://repository.maemo.org/meego/n900-de/daily/ Community Edition images]

[[ARM/N900/Install/MMC#Linux|Flashing Image to MMC]]
* Daily '''Testing''' image called a Acceptance image
* Daily '''Stable''' image called a Sanity image
* Every Monday stable image is called as '''Weekly Image'''

==== Execution ====

*Download Test Sets from gitorious [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests/trees/master Test Sets] by using git
*List all test cases in a a spreadsheet application (LibreOffice/OpenOffice.org Calc, Microsoft Excel, etc.) and create a .csv file ([http://qa-reports.meego.com/example.csv Example csv file])
*[[Quality/HandsetUXQAGettingStarted#Spirit_of_Testing|Test cases verdict]]
'''Pass''' = If all the steps and Functionality is as per expected
'''Fail''' = If any of the one step or Functionality is not as per expected
'''N/A''' = If the test cases are not executable due to the absence of related package in the image, the test results should be N/A
'''Blocked''' = This is a special value required in the situations where verdict cannot be given due to failure in preconditions
* Upload Test report to with respective Test cycle in QA reporting tool [http://qa-reports.meego.com/ QA Reporting tool]

====Reporting bugs====
*Bugs are reported in [https://bugs.meego.com/ Bugzilla].
*[[Quality/How_To_Report_Bugs|How to report bugs]]
*File a new bug:
** Search for an already existing report in [https://bugs.meego.com/query.cgi Bugzilla].
** If a similar report is found, check the Hardware Platform. If it is the same there is no need to file a new report.
** If the bug is in CLOSED or VERIFIED status and this status was set more than four weeks ago (you can check via the "History" link), file a new report (and mention the bug number of the old report) instead of reopening the existing report.
** If no similar report is found, [https://bugs.meego.com/enter_bug.cgi file a new bug report].

====Questions or Doubts====
Any question please leave your query in #meego-arm (irc.freenode.net) or you can [mailto:meego-qa@lists.meego.com meego-qa mailing list]

Suggestion about updating of this page [mailto:srikanth.4.yarlagadda@nokia.com Srikanth Yarlagadda]

Questions about execution and reporting please ping me in IRC srikanth_rst

= Core Testing =
== QA Tasks For Developer Edition ==
QA tasks for the [[ARM/N900|Developer Edition]] differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in [[ARM/N900#Target|Developer Edition Targets.]] There are currently 2 test sets for the [[ARM/N900|Developer Edition]], these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time, a CPU/Memory benchmark, files system, and power measurement, but this will be explained later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* DE testing
* Bug verification
* Wiki clean/update

==== Backlog ====
* Reliability testset planning
* 1.3 Vanilla vs 1.2 DE current measurements
* DE Filesystem benchmark

==== In progress ====
* DE Hourly Automation improvement

==== Done ====
* Qt API test investigation
* Wiki clean/update (waiting for comments)
* Testcase automation list
* Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.3
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Monday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.3 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script
* Testability for MeeGo1.3 features.

==== In progress ====
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result
* MeeGo1.2 feature verification

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

ARM/N900/QA

2011-09-19T15:13:39Z

Andre: Fix some stuff, see http://lists.meego.com/pipermail/meego-qa/2011-September/002229.html

= Meego Community Edition Quality Assurance =
Quality Assurance for Meego [[ARM/N900|Community Edition.]] [[ARM/N900|Community Edition]] QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]] Monitoring the [[ARM/N900|Community Edition]] maturity is one of the main tasks of [[ARM/N900|Community Edition]] QA. The current maturity status can be found from the [[ARM/N900/Status|Status page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Pylkkä
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [[ARM/N900/Status|General CE N900 Feature status]]
* [[ARM/N900/QA/Performance|Performance results]]
* [http://qa-reports.meego.com/1.2/Handset/Dataflow/N900CE Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Key%20Feature Key Features reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [[MeeGo-Meeting_IRC_Schedule|MeeGo-Meeting IRC Schedule]]

N900 CE (Blocker) Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-09-15-07.03.html Meeting minutes 15-09-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-09-08-07.02.html Meeting minutes 08-09-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-09-01-07.03.html Meeting minutes 01-09-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-08-25-07.01.html Meeting minutes 25-08-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-08-11-06.57.html Meeting minutes 11-08-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-23-06.58.html Meeting minutes 23-06-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-19-06.59.html Meeting minutes 19-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

== Contact ==
* [http://lists.meego.com/listinfo/meego-qa QA-mailing list]
* join #meego-qa at freenode

= QA Tools =
Commumity Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - DONE (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - DONE (sampos)
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - DONE (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]
== Functional Testing ==
====Daily testing====

Acceptance/Sanity test is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in acceptance test reflects the most important and basic functionalities of the distribution. We do the acceptance test against Trunk:Testing repo.

*Acceptance (Trunk:Testing)

*Sanity (Trunk:Daily)

====Weekly testing====
This is QA weekly testing cycle for weekly images released by distribution team. Our testing focus would be *Key feature testing* to cover the key features and ensure MeeGo Handset UX delivered features are basically covered and major issues are exposed in timely fashion, as well as changes introduced from the last build do not break working features. The test covers UX and applications (MeeGo Audio player ,Video player, Dialer, SMS, fennec browser,VKB, Email, Photo Viewer, Calendar, IM and contacts, etc).

*Key Basic Testing

*Data Flow Testing

*Basic Feature Testing

==== Execution Process ====

[[File:Process.PNG]]
 

==== Testing images Community Edition image ====
[http://repository.maemo.org/meego/n900-de/daily/ Community Edition images]

[[ARM/N900/Install/MMC#Linux|Flashing Image to MMC]]
* Daily '''Testing''' image called a Acceptance image
* Daily '''Stable''' image called a Sanity image
* Every Monday stable image is called as '''Weekly Image'''

==== Execution ====

*Download Test Sets from gitorious [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests/trees/master Test Sets] by using git
*List all test cases in a a spreadsheet application (LibreOffice/OpenOffice.org Calc, Microsoft Excel, etc.) and create a .csv file ([http://qa-reports.meego.com/example.csv Example csv file])
*[[Quality/HandsetUXQAGettingStarted#Spirit_of_Testing|Test cases verdict]]
'''Pass''' = If all the steps and Functionality is as per expected
'''Fail''' = If any of the one step or Functionality is not as per expected
'''N/A''' = If the test cases are not executable due to the absence of related package in the image, the test results should be N/A
'''Blocked''' = This is a special value required in the situations where verdict cannot be given due to failure in preconditions
* Upload Test report to with respective Test cycle in QA reporting tool [http://qa-reports.meego.com/ QA Reporting tool]

====Reporting bugs====
*Bugs are reported in [https://bugs.meego.com/ Bugzilla].
*[[Quality/How_To_Report_Bugs|How to report bugs]]
*File a new bug
[[File:Newbug.PNG]]
 

====Questions or Doubts====
Any question please leave your query in #meego-arm (irc.freenode.net) or you can [mailto:meego-qa@lists.meego.com meego-qa mailing list]

Suggestion about updating of this page [mailto:srikanth.4.yarlagadda@nokia.com Srikanth Yarlagadda]

Questions about execution and reporting please ping me in IRC srikanth_rst

= Core Testing =
== QA Tasks For Developer Edition ==
QA tasks for the [[ARM/N900|Developer Edition]] differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in [[ARM/N900#Target|Developer Edition Targets.]] There are currently 2 test sets for the [[ARM/N900|Developer Edition]], these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time, a CPU/Memory benchmark, files system, and power measurement, but this will be explained later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* DE testing
* Bug verification
* Wiki clean/update

==== Backlog ====
* Reliability testset planning
* 1.3 Vanilla vs 1.2 DE current measurements
* DE Filesystem benchmark

==== In progress ====
* DE Hourly Automation improvement

==== Done ====
* Qt API test investigation
* Wiki clean/update (waiting for comments)
* Testcase automation list
* Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.3
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Monday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.3 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script
* Testability for MeeGo1.3 features.

==== In progress ====
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result
* MeeGo1.2 feature verification

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

Build Infrastructure/Packagers Developers

2011-09-14T08:29:45Z

Andre: make clear that for bugzilla you need a meego account

These pages are in preparation - contributions welcome.

Note: See [[OBS|the OBS wiki page]] for explanation of the different OBS services MeeGo offers.

This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com.
Note: You need an account to access build.meego.com.
If you have no account, you can still learn how the OBS works at the upstream project's own instance [http://build.opensuse.org http://build.opensuse.org] .

In this track, you'll learn how to use the web interface, the commandline client and create your first package.
The packaging guidelines and more advanced topics are also covered.

== How to get started ==

You need an account on build.meego.com. To request an account:
# Go to [http://bugs.meego.com MeeGo bugzilla] (which in turn first requires having a [https://meego.com/user/register MeeGo account]).
# Click New in the upper navigational bar to begin filing a bug.
# On the next page, click MeeGo Community Infrastructure.
# On the following page, click Build Service and file your bug.

== How to use the web interface ==
A series of pages will make you familiar with webinterface basics. It's divided into several subpages:
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Part 1 - Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Part 2 - Creating a link and adding a repository]]
* [[Developing_in_a_MeeGo_Environment#Building_your_package:_Step_by_step|Part 3 - Your first own package]]

== How to use the commandline client ==
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout and branch]]
* Part 3 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_3|commit & request]]
* Part 4 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

== MeeGo Packaging guidelines and Howto ==
* [[Packaging|Packaging]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Packaging Tutorial]]

== [[Build_Infrastructure/QA|QA Processes around the OBS]] ==
See the [[Quality]] page.

== Verifying Your Package Changes Locally and Online ==
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]

== Troubleshooting ==

* '''I'm getting "error: Package already exists: %package debuginfo"''' — Disable the debuginfo flag for the repo/arch that gives you this problem. You will probably still get a debuginfo package. This appears to happen when OBS creates debuginfo packages by default, and so this flag causes a sort of doubling-up of the debuginfo package.

== IRC / mailinglists / contact ==

If you need help, you can join #meego on irc.freenode.net . See also [[Community communication|this page]] about all MeeGo IRC channels.

You can join [http://lists.meego.com/listinfo/meego-dev MeeGo-dev] and [http://lists.meego.com/listinfo/meego-packaging MeeGo-packaging] mailing lists [http://lists.meego.com/mailman/listinfo over here].

[[Category:Build Infrastructure]]

Quality

2011-09-05T14:50:12Z

Andre: Rename Q&A to the one specific question answered there

= Quality =

This page is for MeeGo Quality Assurance related material.

== Getting Started ==
* [[Quality/Getting started|How Can I Contribute]]
== Projects ==

For all test reports see [http://qa-reports.meego.com http://qa-reports.meego.com]

{| border = 1 valign="top"
! Release
! Core OS
! Handset UX
! Tablet UX
! Netbook UX
! SDK
! In Vehicle Infotainment
|-
| Release 1.3
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.3/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
* [[/meego core feature/1.3 | Core Requirements]]
|
* [[Quality/Plans/Handset UX test plan|MeeGo HandSet UX Test Plan]]
* [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests Test Suite]
* [http://qa-reports.meego.com/1.3/Handset Handset Test Reports]
|
* Tablet UX Test Plan
* Tablet UX Test Suite
* [http://qa-reports.meego.com/1.3/Tablet Tablet Test Reports]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.3/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.3/SDK SDK Test Reports]
|
* [[/Plans/IVI Test Plan | MeeGo IVI Test Plan]]
* IVI Test Suite
* [http://qa-reports.meego.com/1.3/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|-
| Release 1.2
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.2/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [[Quality/Plans/1_2_Handset_UX_test_plan|MeeGo HandSet UX Test Plan]]
* [[Quality/TestSuite/handset-test-suite|Test Suite]]
* [http://qa-reports.meego.com/1.2/Handset Handset Test Reports]
* [[Quality/HandsetQualityMetrics|Quality Metrics]]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/Tablet Tablet Test Reports]
* [[Quality/TabletQualityMetrics | Quality Metrics]]
|
* [[Quality/1.2NetbookTestPlan|1.2 SW Update Test Plan]]
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.2/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.2/SDK SDK Test Reports]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
* [http://www.casinoenligne555.net casino en ligne francais]
|}

== QA tools ==

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
* [[Quality/QA-tools|Find our tools and contact information]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet)
* [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution.
* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions how to automate test execution and image installations.

== Procedures and best practices ==

* [[Quality/Plans/Testability-checklist|Feature Testability Checklist]]
** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** This is a guide for QA contacts about how to comment on feature testability so as to provide as much information as possible to test developers.
*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

* [[/defects | Defects Management]]
* [[/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[/Bugzilla_Fields|Fields in a bug report]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [[/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]] -- WORK IN PROGRESS, please contribute
* [[/SysDebug | MeeGo Sys-Debug]] (finding the right component for a report)
* [[/triageteam_assignee | Process to deal with bugs assigned to triageteam@meego.bugs]]
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|MeeGo Bugzilla Customization Features]]
* [https://gitorious.org/meego-bugzilla Bugzilla Codebase repository] (move not finished yet)
* [[/MeeGoBugzillaRequestProcess|How to requests changes in Bugzilla code/UI itself]]
* [[/error_manager | MeeGo Error Managers]]

== Compliance Program ==
[[Quality/Compliance | MeeGo Compliance Program]] - the compliance spec (initially)

== Contact ==

* Mailing List: [http://lists.meego.com/listinfo/meego-qa MeeGo-QA]
* IRC: Channel #meego-qa on irc.freenode.net

== Meetings ==

General QA Meetings are held weekly on Tuesdays 07:00 UTC in the channel #meego-meeting on irc.freenode.net. [[Quality/Meetings|Click here for more information.]]

QA Tools meetings are held weekly on Tuesdays 08:00 UTC in the channel #meego-meeting2 on irc.freenode.net. [[Quality/QA-tools/Meetings|Click here for more information.]]

For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]].

== See also ==

* [[/Glossary | QA Glossary ]]
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]]
* [[Quality/Plans/Quality-considerations|Quality Considerations / Testing Quality Characteristics]]
** Some ideas around testing quality characteristics hopefully helping you identify what kind of things could be checked from applications - can be used as a frame to define test considerations – as a set of logical test cases - for applications targeting to run on MeeGo.

== Tasks of the "QA Contact" ==

* QA contact work with/support/advice/help package maintainers (see [http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility|Fedora example] or [[Packaging/Guidelines#Maintaining_a_Package|MeeGo guidelines for maintaining package]]) and other users on QA related issues/questions for component in case.
** Features ("Once a requirement is integrated, MeeGo QA verifies it by running the corresponding test cases." from [[https://meego.com/developers/requirements ]])
*** make testability analysis for features (yes or no value to testability field) and
*** identify "feature acceptance tests" together with product management and package maintainers that could be used at the end as a criteria for feature status to be changed as "VERIFIED".
** Bugs ("QA Contact or Bug Submitter verifies bug fixing with the "how to re-produce" instructions in the original bug report when the bug is marked as RELEASED - FIXED." from [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Handling page]])
*** facilitate the whole bug life-cycle from QA perspective, including ensure bug report completeness, follow up bugs by providing helpful or required information in timely fashion to accelerate bug fixing and verify the issue after fix is integrated, especially when the original reporter is not responsive or has difficulty to follow the bug up.
*** actively follow-up the bugs. Making sure the bug is attended properly, ping the default assignee or assignee or reporter to get visibility and comments on the progress, triage bugs, verify and close them whenever possible.

[[Category:QA]]

Working Group Process

2011-08-09T13:08:11Z

Andre: add link to list of Bugzilla keywords

Process approved in the [[Technical Steering Group meetings|Technical Steering Group Meeting]] on [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-20.00.html January 26, 2011]. Please do not make changes to this process, but you can make any suggestions on the discussion page.

== Goals this proposal aims to achieve: ==
* Consistency across all MeeGo Working Groups
* Ease of participation in Working Groups and integration with implementation work
* Lightweight and transparent process

== Role of the Working Group ==
The Working Groups are devoted to discussions related to their specific vertical and are accountable to provide input and guidance about market requirements. They are responsible for collecting market requirements from organizations and companies participating in the Working Groups. They identify gaps and develop requirements that detail the need for capabilities. The Working Groups do not manage the projects, but rather support product evolution by providing market requirements.
A high-level description of some of the Working Group tasks include collecting market requirements and prioritize them, provide a compliance profile and a hardware profile for the specific vertical.

== Working Group Governance ==
* The [http://meego.com/about/governance/working-groups Working Group] is led by one person, the Working Group chair who is appointed by and reports to the Technical Steering Group (TSG).
* Each Working Group includes a project manager and a product manager (both appointed and report to the TSG). Their role is to oversee the MeeGo vertical from an implementation point of view and they participate in the specific Working Group of their MeeGo vertical. The product manager oversees the requirement management process on a daily basis concludes discussions about requirements implementation.
* Companies are invited to the MeeGo Working Groups by the TSG.
* The TSG can delegate incremental membership to the Working Group.
* Working Groups use lightweight governance to be effective and efficient. Decisions within the Working Group follow the IETF-like rough consensus model as explained in [http://tools.ietf.org/html/rfc2418 http://tools.ietf.org/html/rfc2418]:

<blockquote>
Working Groups make decisions through a "rough consensus" process. IETF consensus does not require that all participants agree although this is, of course, preferred. In general, the dominant view of the working group shall prevail. (However, "dominance" is not to be determined on the basis of volume or persistence, but rather a more general sense of agreement). Consensus can be determined by a show of hands, humming, or any other means on which the Working Group agrees (by rough consensus, of course). Note that 51% of the working group does not qualify as "rough consensus" and 99% is better than rough. It is up to the Chair to determine if rough consensus has been reached (IETF Working Group Guidelines and Procedures).
</blockquote>

* Conflicts around architecture/requirement decisions will be handled by the project team (i.e. architects and product managers and subsystem maintainers). Only conflicts which otherwise can not be resolved will be reported to the TSG, which has the final say.
* A voting mechanism can be used when needed.
** A company can have more than one participant active and involved in the Working Group.
** A company has only a single vote, regardless of number of participants.

== Working Group Logistics ==
Working Groups will have their own area within the MeeGo wiki where they publish list of participants, meeting information and minutes, mailing list informations, and post data relative to that Working Group, etc.

== Working Group Membership ==
* Working Groups will be kicked-off with a small number of committed members - membership in Working Groups will grow over time.
* Membership in the Working Group is decided based on:
** Meritocracy and contributions to the overall MeeGo project.
** Commitment to create a MeeGo product in that specific vertical.
* Working Group representatives are suggested to the TSG and the Working Group by their respective organizations.
* The Product Manager and Project Manager are members of the Working Group as well as the Project Team. They are nominated for these role by the TSG, as mentioned earlier.

== Working Group Process ==
[[File:Keyword_categories.png|thumb|400px|Keyword categories]]
# Working Group participants submit their companies' requirements / market requirements / feature requests / etc to the MeeGo project via [http://bugs.meego.com bugs.meego.com].
#* Working Group requirements are submitted by [http://bugs.meego.com/enter_bug.cgi creating a bug report] and, using the [https://bugs.meego.com/describekeywords.cgi "Keywords" field], tagging the bug using the appropriate keyword.
#* The bug report must include the following information:
#** ''Requirement title''
#** ''Explanation of the need for the requirement''
#** ''Description of its use''
#** ''A use case description for complex requirements''
#** ''Implementation resources the company is willing to provide ''
#* Companies submitting requirements must acknowledge that they will support the implementation of the requirement.
# The participants of the Working Group will discuss the requirement and leave comments in the bug.
#* Discussions can also take place in other media such as IRC, mailing list and conference calls.
# If a requirement wins the consensus of the Working Group participants for its need and usefulness, and there are resources available to support its implementations, it will be prioritized for a specific MeeGo release, and moved to the project team.
#*The requirement will then move from a "Working Group Requirement" into the queue of the MeeGo release for which it is targeted.
#*The resources to implement it will be allocated, and work will begin.
#* The product and project manager of the MeeGo vertical must participate in these discussions as they drive the implementation work.
# If a requirement wins the consensus of the Working Group participants for its need and usefulness, but there are no resources immediately available for implementation, it will be prioritized as low for a given MeeGo release, pending the availability of resources.
#* Once resources are available, the requirement will be prioritized as high for a given MeeGo release, and implementation work can begin.
# If a requirement does not win the consensus within the Working Group as needed to be implemented in MeeGo, it will remain tagged as "Working Group Requirement" in bugs.meego.com for a specific amount of time, to be decided by the Working Group. After a specific wait period, such requirements are revisited for a second look. If no change is made regarding this specific requirement, the bug is closed and the requirement is discarded until further notice. Otherwise, it will progress within the process as documented earlier.

== Miscellaneous ==

=== The role of the TSG: ===
The TSG sets the direction, tone, and vision for MeeGo, speaks on behalf of the project, and is responsible for project level decisions and overall leadership. Currently, the members of the TSG are Imad Sousou (Director of the Intel Open Source Technology Center) and Valtteri Halla (Director of MeeGo Engineering at Nokia). The TSG meets every two weeks. These meetings are public and open to all. Minutes of the TSG meetings are also public and available at TSG meeting logs. Participate in the TSG meetings at [http://wiki.meego.com/Technical_Steering_Group_meetings http://wiki.meego.com/Technical_Steering_Group_meetings].

=== To participate in a MeeGo Working Group: ===
# Contact the Working Group Chair for the specific MeeGo vertical, who will introduce you to the Working Group, help integrate you/your team with the Working Group and project team of the MeeGo vertical, direct you to the Working Group mailing list and wiki, and provide you with information about regular meetings, ongoing activities, etc.
#* MeeGo IVI Working Group Chair – Rudolf.Streif (at) linuxfoundation.org - [http://meego.com/users/rudolfstreif rudolfstreif]
#* MeeGo Handset Working Group Chair – Ibrahim (at) linuxfoundation.org - [http://meego.com/users/ibrahim ibrahim]
# You need to identify and assign:
#* A representative from your organization that will participate in the Working Group of interest to you. The representative will be bringing the requirements from your company and driving them to acceptance within the Working Group to be part of MeeGo implementation.
#* Engineering resources from your organization to the Project Team of the MeeGo vertical that is of interest to your organization. These resource will be working with the collective MeeGo.com resources on the implementation of the MeeGo stack (core and vertical).

=== To suggest a new MeeGo Working Group: ===
If you are interested in a MeeGo Working Group that is not kicked off yet, or are interested in having MeeGo support a new device type (i.e. new vertical), please go to [http://bugs.meego.com bugs.meego.com] and create a bug for that request and assign it to user [http://meego.com/users/ibrahim ibrahim].

=== Non-commercial community participation in the Working Groups ===
Community members are welcome to participate, and they are already active members of MeeGo development. Requirements typically come from Community, Working Groups, and Upstream Projects as illustrated in [http://meego.com/developers/requirements http://meego.com/developers/requirements]. The goal of this Working Group process is to put in place a framework that companies can follow, using the same methods and tools that the community members are already using. Community members can submit requirements/feature requests/bugs/etc via [bugs.meego.com http://bugs.meego.com].

== Process Improvements ==
As we start using this process, we anticipate new ideas for practical improvements. If you have any suggestions for improvements, please assign a bug to [http://meego.com/users/ibrahim ibrahim] with your suggestions.

== References ==
* MeeGo Governance http://meego.com/about/governance
* Community Office http://meego.com/about/governance/community-office
* MeeGo IVI Working Group Home Page http://wiki.meego.com/in-vehicle

ARM/N900/QA

2011-08-08T08:20:19Z

Andre: /* Reporting bugs */

= Meego Developer Edition Quality Assurance =
Quality Assurance for Meego [[ARM/N900|Developers Edition.]] [[ARM/N900|Developer Edition]] QA uses many same components as in core Meego, therefore remember to look [[Quality|Meego core quality page.]] Monitoring the [[ARM/N900|Developer Edition]] maturity is one of the main tasks of [[ARM/N900|Developer Edition]] QA. The current maturity status can be found from the [[ARM/N900/Status|Status page.]]

== Organization ==
* Error Management
** Error Manager: Iekku Huttunen
* QA Tools
* Core Testing
* User Experience Testing (UX)

== Reports ==
* [[ARM/N900/Status|General DE N900 Feature status]]
* [[ARM/N900/QA/Performance|Performance results]]
* [http://qa-reports.meego.com/1.2/Handset/Dataflow/N900CE Dataflow reports]
* [http://qa-reports.meego.com/1.2/Handset/Key%20Feature Key Features reports]

== Meetings ==
QA IRC meeting every Tuesday:
* [[MeeGo-Meeting_IRC_Schedule|MeeGo-Meeting IRC Schedule]]

N900 DE Blocker Bug Triage meeting minutes:
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-23-06.58.html Meeting minutes 23-06-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-19-06.59.html Meeting minutes 19-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-12-06.59.html Meeting minutes 12-05-2011]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-07.00.html Meeting minutes 05-05-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-21-07.01.html Meeting minutes 21-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-14-07.00.html Meeting minutes 14-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-07-07.02.html Meeting minutes 07-04-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-31-07.00.html Meeting minutes 31-03-2011]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-24-06.59.html Meeting minutes 24-03-2011]

== Contact ==
* [http://lists.meego.com/listinfo/meego-qa QA-mailing list]
* join #meego-qa at freenode

= QA Tools =
Developers Edition uses same QA Tools as in core Meego. For more information please refer to the [[Quality/QA-tools|Quality/QA-tools]].

== QA-Tools Task List ==
List of tasks the QA-Tools are doing for Meego Developer Edition.
If you need something from QA please tell it to us :)
=== OTS setup ===
(Open Testing System)
* [http://194.136.64.78/logger/view/ OTS server] DONE
* [http://194.136.64.78/logger/view/workers/ OTS worker(s) for core tests]- DONE
* [http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated Reporting of hourly tests to QA-reports] - DONE
* Minimize automatic installation time to 10mins - DONE
* OTS worker for UX tests - NOTSTARTED
* OTS Worker(s) for DE tests - ONGOING (timakima)
* Power consumption measurements - NOTSTARTED

=== Test automation images ===
* Setup hourly image building for autotest image on own setup - Riku Halonen/Timo Harkonen/Ville Ilvonen - DONE (in OTS subnet, see above)
* We need to be able to control included test packages - ONGOING (http://meego.gitorious.org/meego-quality-assurance/handset-hourly-automated-tests)
* Move to use images from release engineering (1. download image, 2. install automation enablers, core dumping enablers etc. using mic-chroot, 3. install image to device 4. test) - NOT STARTED

== Applications for testing ==
* qt-demos already available from the repos
* Small applications that use Qt mobility APIs to access things like sensors to help manual testing

== Test asset ==
We are using mainly MCTS test assets, so please refer to the [[Quality/TestSuite/MCTS|MCTS page.]] You can find list of open bugs also from there.
* [https://bugs.meego.com/buglist.cgi?quicksearch=mcts List of open bugs for MCTS]
** see priorities below - discuss with Iekku about priorities of open bugs for MCTS tests
# WLAN cases
# Call/SMS cases
# Audio policy framework cases (lower priority)
# Camera cases (lower priority)
# Sensor data cases (Qt Mobility, lower priority)

== Crash analysis support for ARM core dumps ==

[[File:Text9867-0-4-8.png|350px|thumb|right|Automated testing and crash reporting]]

Core dump processing and backtraces from crashing ARM processes (click the image on right).

* Rich Core dumping
** Make rich-core dumping to work in MeeGo N900 DE (basic functionality) - DONE (sampos, rikhalon)
*** Changes in MeeGo Gitorious ([https://meego.gitorious.org/meego-quality-assurance/rich-core/commits/meego-n900de meego-n900de] branch).
*** Dumps are generated in /home/meego/core-dumps
*** In file name, string "xxxx" is used instead of IMEI digits (privacy issue)
*** Get latest packages [http://repo.pub.meego.com/home:/rha/Project_DE_Trunk_Testing_standard/armv7l/ here]
*** Add "-corewatcher" and "-corewatcher-applet" to .ks file to remove overlapping corewatcher.
** Fix core-reducer (https://bugs.meego.com/show_bug.cgi?id=17134) - DONE (alkuznet)
** Oopslog (and lifelog) functionality - NOT STARTED

* Set up back-end server for core processing - ONGOING (rikhalon, sampos, timakima)

* Image building and test run triggered from cron - trigger-testrun.sh -u <URL> - DONE (timakima)

* Implement OTS Conductor plugin to fetch debug package list (before test run) and upload rich-core dumps to post-processing (after testrun )- DONE (rikhalon)

* testrunner-lite sets a UID for each test case on DUT kernel core pattern. So that a coredump can be matched with a test case - DONE (rikhalon)

* Debug image is built (simultaneuosly) on the core proscessing backend server - build-autotest-image.sh -f fs -d -p debug-packet-list -s 8000 -u <URL>, and saved as target for core prosessing - DONE (sampos)

* After each test case, cores matched against the UID are fetched from the DUT by testrunner-lite. - DONE (sampos)
** testrunner-lite needs to write unique identifier to results.xml e.g. md5 hash from rich-core.
[[File:backend.png|350px|thumb|right|Core Processing Backend]]
<crashes>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
<crash-id>1234567890ABCDEF</crash-id>
</crashes>

* The core processing backend extracts the rich core and looks for proper target (if not available waits...) - PofC DONE (sampos)

* The core processing backend chroots to the target with debug symbols and executes statically linked cross gdb for backtrace - DONE (sampos)

* Upload processed crash data using [[Quality/QA-tools/CrashReports/API|Crash Reports API]] - DONE (rikhalon)

== Boot time measurement ==
* Measure and optimize N900 boot time (timakima, ONGOING)

== CPU load measurement during audio/video playback ==

== Application Manager ==
* Implement an application manager (similar to one in N900/Fremantle) to control install/uninstall/update applications and other packages. (kyranto, ONGOING).

= UX testing =
== Test execution schedule ==
* UX testing schedule: DE / Meego.com testing
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Dataflow
| DE Weekly
| P1
|-
| Monday
| Use cases
| DE Weekly
| P2
|-
|Monday
| Key feature
| DE Weekly
| P3
|-
| Monday
| Performance
| DE Weekly
| P5
|-
| Monday
| Reliability / Iterative
| DE Weekly
| P6
|-
| Monday
| Dataflow
| DE Trunk testing
| P4
|-
| Tuesday
| Dataflow
| DE Trunk testing
| P1
|-
| Tuesday
| Dataflow
| DE Trunk
| P2
|-
| Tuesday
| Acceptance
| Meego Trunk testing
| P3
|-
| Tuesday
| Key feature
| DE Tablet (N900)
| P4
|-
| Wednesday
| Dataflow
| DE Trunk testing
| P1
|-
| Wednesday
| Dataflow
| DE Trunk
| P2
|-
| Wednesday
| Key feature
| Meego.com weekly
| P3
|-
| Wednesday
| Sanity
| Meego.com weekly
| P4
|-
| Thursday
| Dataflow
| DE Trunk testing
| P1
|-
| Thursday
| Dataflow
| DE Trunk
| P2
|-
| Thursday
| Acceptance
| Meego.com Trunk testing
| P3
|-
| Friday
| Dataflow
| DE Trunk Testing
| P1
|-
| Friday
| Dataflow
| DE Trunk
| P2
|-
| Friday
| Acceptance
| Meego.com Trunk testing
| P3
|}

== Performance Testing ==
Performance testing results done from UI can be found [[ARM/N900/QA/Performance|here]]
== Functional Testing ==
====Daily testing====

Acceptance/Sanity test is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in acceptance test reflects the most important and basic functionalities of the distribution. We do the acceptance test against Trunk:Testing repo.

*Acceptance (Trunk:Testing)

*Sanity (Trunk:Daily)

====Weekly testing====
This is QA weekly testing cycle for weekly images released by distribution team. Our testing focus would be *Key feature testing* to cover the key features and ensure MeeGo Handset UX delivered features are basically covered and major issues are exposed in timely fashion, as well as changes introduced from the last build do not break working features. The test covers UX and applications (MeeGo Audio player ,Video player, Dialer, SMS, fennec browser,VKB, Email, Photo Viewer, Calendar, IM and contacts, etc).

*Key Basic Testing

*Data Flow Testing

*Basic Feature Testing

==== Execution Process ====

[[File:Process.PNG]]
 

==== Testing images Community Edition image ====
[http://repository.maemo.org/meego/n900-de/daily/ Community Edition images]

[[ARM/N900/Install/MMC#Linux|Flashing Image to MMC]]
* Daily '''Testing''' image called a Acceptance image
* Daily '''Stable''' image called a Sanity image
* Every Monday stable image is called as '''Weekly Image'''

==== Execution ====

*Download Test Sets from gitorious [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests/trees/master Test Sets]
*List all test cases in Excel and create .csv file [http://qa-reports.meego.com/example.csv example csv]
*[[Quality/HandsetUXQAGettingStarted#Spirit_of_Testing|Test cases verdict]]
'''Pass''' = If all the steps and Functionality is as per expected
'''Fail''' = If any of the one step or Functionality is not as per expected
'''N/A''' = If the test cases are not executable due to the absence of related package in the image, the test results should be N/A
'''Blocked''' = This is a special value required in the situations where verdict cannot be given due to failure in preconditions
* Upload Test report to with respective Test cycle in QA reporting tool [http://qa-reports.meego.com/ QA Reporting tool]

====Reporting bugs====
*Bugs are reported in [https://bugs.meego.com/ Bugzilla].
*[[Quality/How_To_Report_Bugs|How to report bugs]]
*File a new bug
[[File:Newbug.PNG]]
 

====Questions or Doubts====
Any question please leave your query in #meego-arm (irc.freenode.net) or you can [mailto:meego-qa@lists.meego.com meego-qa mailing list]

Suggestion about updating of this page [mailto:srikanth.4.yarlagadda@nokia.com Srikanth Yarlagadda]

Questions about execution and reporting please ping me in IRC srikanth_rst

= Core Testing =
== QA Tasks For Developer Edition ==
QA tasks for the [[ARM/N900|Developer Edition]] differ from the usual N900 approach in that there are less features to be tested. This is described in more detail in [[ARM/N900#Target|Developer Edition Targets.]] There are currently 2 test sets for the [[ARM/N900|Developer Edition]], these are the Sanity Test Set and the Feature Test Set. They are described below.

=== Test Sets ===
==== Sanity Test Set ====
The sanity set should be run automatically on every image. As such it must meet the following requirements:
* 100% automated
* Testing only basic features
==== Feature Test Set ====
The feature set will be run periodically and will test the basic features as well as enablers for those features (e.g. PIM for phoning contacts). Performance will also be analysed, at the moment, this will include browser startup time, a CPU/Memory benchmark, files system, and power measurement, but this will be explained later.

Suggestions are welcome.

=== Testing schedule ===
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release
|-
| Monday
| Feature
| DE Weekly
|-
| Tuesday
| Sanity
| DE Trunk testing
|-
| Wednesday
| Sanity
| DE Trunk testing
|-
| Thursday
| Sanity
| DE Trunk testing
|-
| Friday
| Sanity
| DE Trunk Testing
|-
|}

=== Core QA Team Backlog ===
The Core QA team intends to keep its backlog as public as possible. The limitation on this is the amount of work generated by doing this. We will attempt to keep an up-to-date lists of tasks and progress on these tasks. At the moment, the task list looks like this:

==== Continuous tasks ====
* DE testing
* Bug verification
* Wiki clean/update

==== Backlog ====
* Reliability testset planning
* 1.3 Vanilla vs 1.2 DE current measurements
* DE Filesystem benchmark

==== In progress ====
* DE Hourly Automation improvement

==== Done ====
* Qt API test investigation
* Wiki clean/update (waiting for comments)
* Testcase automation list
* Plan Feature testset (.xml updated)
* Create weekly schedule for MRT (currently in draft form)
* Week 15 DE Sanity Testing
* Maturity statement of Alpha RELEASE (result in QA-report)
* Alpha RELEASE testing

== QA Tasks for MeeGo.com N900 ==

=== Test execution schedule ===
* MeeGo.com N900 Core weekly test schedule for MeeGo1.3
{| cellpadding="5" cellspacing="0" border="1"
! Day !! Test set (status) !! Release !! Priority
|-
| Monday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Monday
| Basic feature test (OK)
| MeeGo.com pre-weekly
| P2
|-
| Tuesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Tuesday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Wednesday
| Dataflow (OK)
| MeeGo.com weekly
| P1
|-
| Wednesday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P2
|-
| Thursday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Thursday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|-
| Friday
| Acceptance test (OK)& test for changes
| MeeGo.com trunk testing
| P1
|-
| Friday
| Sanity test (OK)
| MeeGo.com trunk
| P2
|}

=== META team backlog for MeeGo1.2 N900 ===

==== Continuous tasks ====
* Bug verification
* MeeGo1.3 N900 daily validation

==== Backlog ====
* Optimize acceptance automation script
* Testability for MeeGo1.3 features.

==== In progress ====
* Automation testing for trunk:test and trunk image

==== Done ====
* Publish automation test result
* MeeGo1.2 feature verification

= Usefull links =

* [[ARM/N900/Install/MMC|Flashing instructions]]
Flashing tested with http://download.meego.com/testing-daily/builds/trunk/1.1.90.8.20110318.89/

[[Category:N900]]

User:Andre/Bug Summary Prefixes

2011-08-02T08:37:59Z

Andre: fix typo

= Bug summary prefixes in bugs.meego.com =

{|
| style="background: #ffcc00; color: black" | '''Note:''' First and rough list. Does not mean that the current practice necessarily makes sense, just trying to document it. -- [[User:Andre]] 2011-05-17
|}

== List ==

Feel free to edit, but please keep the alphabetical order.

{| border="1" + Items
! Prefix
! Description
|-
| [CONX]
|
|-
| [CE] and [DE]
| Bug is reproducible only with [http://wiki.meego.com/ARM/N900/DeveloperEdition N900 Development Edition] / Community Edition image
|-
| [FEA]
| Feature request
|-
| GLS -
| outdated, stands for "Global Language Solutions". Replaced by [L10N] and [I18N]
|-
| [Installer]
|
|-
| [I18N]
| For issues in the codebase (not in translations themselves) that are related to using other languages
|-
| [IVI]
|
|-
| [L10N]
| For issues in translations (not in the codebase itself)
|-
| [MCTS-]
| For bug related to MCTS
|-
| [Meta] / [META] / [METABUG]
| For collecting bug reports from same area together (e.g. power management issues) by using 'Depends on'.
|-
| [MTF]
|
|-
| [MWTS-]
| For bug related to MWTS
|-
| [PnP]
| Power and Performance (according to bug 18851 comment 5)
|-
| [REG]
| Regression
|-
| [Trunk:Daily] / [trunk: daily] / [Trunk : Daily]
|
|-
| [Trunk:Testing]
|
|}

[[Category:QA]]

Quality/Triageteam Assignee

2011-07-29T08:16:47Z

Andre: Undo revision 45293 by Ares2012 - Why replace a generic, always up-to-date query by specific bug numbers that need to be manually updated all of the time?

== Why triageteam@meego.bugs account?==
* Bug assignees have the requirement to feedback that the bugs are assigned to wrong person, and they have no idea who should be the right owner.
* Usually no single person has the bandwidth and capability to analyze all of the bugs which are assigned to this account, especially there are some system level bugs which need deep analysis in MeeGo context.

== How bugs are assigned to triageteam@meego.bugs account?==
* "triageteam@meego.bugs" is not supposed to be set as default assignee of any component in bugzilla.
* When developers believe the bugs are assigned to wrong person, and they have no idea who should own the bugs, they will assign bugs to triageteam@meego.bugs account

== Actions to facilitate the lifecycle for bugs assigned to triageteam@meego.bugs ==
* Bugs assigned to triageteam@meego.bugs will be published to wiki so that people have direct visibility of those bugs.
* Bug triage team will try their best to re-triage the bugs
* Bug list will be sent to meego-dev mailing list regularly to see if community developers are interested in taking those bugs
* The target is to get the bugs triaged to a named assignee in 5 business days, and if not, the bugs will be escalated to program managers to help find out the assignee.
* Bugs assigned to triageteam@meego.bugs will be scrubbed every week until they are re-assigned

==Bug List==
{{#bugzilla:
|columns=id,priority,status,to,summary
|to=triageteam@meego.bugs
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
|sort=id
|order=asec
}}

== Contact ==
Please use the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list].
Contacts are [mailto:fan.zhao@intel.com Fan Zhao] and [mailto:jiex.zhou@intel.com Jie Zhou].

== Reference ==
* [[Quality/Bugtriage | MeeGo Bug Triage]]
* QA main wiki: [[Quality]]

Quality/Triageteam Assignee

2011-07-17T19:39:54Z

Andre: Contact: restore email info that I deleted before (sorry)

Quality/Triageteam Assignee

2011-07-15T10:24:36Z

Andre: /* Contact */

== Why triageteam@meego.bugs account?==
* Bug assignees have the requirement to feedback that the bugs are assigned to wrong person, and they have no idea who should be the right owner.
* Usually no single person has the bandwidth and capability to analyze all of the bugs which are assigned to this account, especially there are some system level bugs which need deep analysis in MeeGo context.

== How bugs are assigned to triageteam@meego.bugs account?==
* "triageteam@meego.bugs" is not supposed to be set as default assignee of any component in bugzilla.
* When developers believe the bugs are assigned to wrong person, and they have no idea who should own the bugs, they will assign bugs to triageteam@meego.bugs account

== Actions to facilitate the lifecycle for bugs assigned to triageteam@meego.bugs ==
* Bugs assigned to triageteam@meego.bugs will be published to wiki so that people have direct visibility of those bugs.
* Bug triage team will try their best to re-triage the bugs
* Bug list will be sent to meego-dev mailing list regularly to see if community developers are interested in taking those bugs
* The target is to get the bugs triaged to a named assignee in 5 business days, and if not, the bugs will be escalated to program managers to help find out the assignee.
* Bugs assigned to triageteam@meego.bugs will be scrubbed every week until they are re-assigned

==Bug List==
{{#bugzilla:
|columns=id,priority,status,to,summary
|to=triageteam@meego.bugs
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
|sort=id
|order=asec
}}

== Contact ==
Please use the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list].
Contacts are Fan Zhao and Jie Zhou.

== Reference ==
* [[Quality/Bugtriage | MeeGo Bug Triage]]
* QA main wiki: [[Quality]]

Quality/Bugtriage Stock Answers

2011-07-13T12:18:04Z

Andre: add IM instructions for "meego-app-im-dumplogs"

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

== Communication ==

=== IM (Instant Messaging) ===

Can you please run "meego-app-im-dumplogs" from a terminal and reproduce the problem? It will create several log files; please attach them to this bug report.

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

===Skype===
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

====Missing Service Center field in SMS settings====

Could you attach here the output of /usr/lib/ofono/test/list-modems script?
Is the output of the above script showing anything in ServiceCenterAddress?

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall dialer
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer -prestart --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

Please check https://live.gnome.org/Tracker/Documentation/ReportingBugs for how to provide more information.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

== Power Management ==
Please always provide the output file of "powertop --html" on any power management issues. Thanks!

==SDK / Images==

=== Problems creating images ===

Please attach your config file /boot/extlinux/extlinux.conf in your image to this bug report.
[[Category:QA]]

Quality/Bugtriage Stock Answers

2011-07-13T12:01:05Z

Andre: /* Data */

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

===Skype===
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

====Missing Service Center field in SMS settings====

Could you attach here the output of /usr/lib/ofono/test/list-modems script?
Is the output of the above script showing anything in ServiceCenterAddress?

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall dialer
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer -prestart --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

Please check https://live.gnome.org/Tracker/Documentation/ReportingBugs for how to provide more information.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

== Power Management ==
Please always provide the output file of "powertop --html" on any power management issues. Thanks!

==SDK / Images==

=== Problems creating images ===

Please attach your config file /boot/extlinux/extlinux.conf in your image to this bug report.
[[Category:QA]]

Using Transifex

2011-07-11T10:57:10Z

Andre: fix typo

Go to https://meego.transifex.net/ and register. Once you have done that, select a language team to join. The lead for that team will then contact you and, if you agree on process for that language, you will be approved for that language team. If you don't see a team for your language, please consider starting it and being the lead, at least until you have critical mass.

Ideally, a language team should have a lead, at least 2 translators, and at least two editors/reviewers. It is essential that the same person that translates does not also review and approve their translation!

Once you've joined a language team, you can start translating! Transifex makes it easy for you to get the most up-to-date translation resource, translate, and post it back to the project.

'''Note:''' A few months ago, the MeeGo Transifex site was privately hosted at http://translate.moblin.org, but this site is no longer used. Please update your bookmarks to current site, https://meego.transifex.net/.

#Once approved for a language team, choose a MeeGo release you would like to translate from the [https://meego.transifex.net/ MeeGo Hub]. The latest release will be labeled and will likely receive the most attention.
#The next page displays a large list of translation statistics for all MeeGo language teams. Click on the language code for your team to see all of the resources available for translation.
#If translation has already started for a particular resource, simply click on the resource name to continue translation, or revise existing translations.
#If no translation exists yet for a particular resource, it will be listed at the bottom of the page. Follow the link for the desired resource to translate. Now you have landed on the resource page. Click "Add translation", choose your language from the dropdown menu, and click "Translate Online".
#After you are finished translating, remember to click the "Save and Exit" button near the page bottom.
#Now your translations are available for MeeGo developers to integrate into the distribution.

'''Note:''' If you are finished translating, be sure to unlock the translation so others on your team can work on it.

'''Note:''' Transifex lets you download translation resources so you can translate locally instead of through the web interface. For MeeGo Netbook UX PO files, we highly recommend using [http://www.poedit.net/ Poedit] to translate them. For MeeGo UX TS files, the Qt Linguist tool is recommended. There are other applications that also get the job done. [http://userbase.kde.org/Lokalize Lokalize] is a KDE program that works on Linux and Windows. [http://translate.sourceforge.net/wiki/virtaal Virtaal] is another great program. The biggest plus of these programs is the [http://en.wikipedia.org/wiki/Translation_memory translation memory]. You can load other translations, such as the Gnome translations, in the memory and the application suggests translations when a similar translation exists. This is handy for consistency. Some applications even contain interfaces to automatically query e.g. [http://open-tran.eu/ open-tran.eu] or [http://open-tran.eu/ Google Translate].

== Starting a Translation ==

For those of you familiar with PO Edit and editing po files, skip the next 3 steps.
#Open the bisho.pot file in PO Edit. In the Settings dialog, be sure to put your email address in the file heading (under “Last-Translator”) so we know who did the work and you get the recognition for doing it! Also, please be sure that the Content-Type in the header is "UTF-8." Make sure to enter this in the plural field to avoid corruptions and losing your work when you save: nplurals=2; plural=n!=1;
#Save the settings you just entered.
#Notice that there is a English string and right below it is msgstr “”. Put your translation of the English string inside those quotes.
#You can name your new PO whatever you like on your local drive, but it’s better to use the same name as the file in Transifex for easy identification when you want to upload it back.
#Go back to meego.transifex.net and go to the Bisho project.
#Scroll down until you see your language. (If it does not appear in the list, you will need to click "Add a New Translation." See below.)
#Select the last icon in the row of icons next to your language (the icon has a pencil in it and the mouse-over says "Submit a translation for po/xxx.po.")
#Use the “Browse” button to find your local file and select it.
#Click Send. If all goes well, you will see a message at the top of the screen that the po file was added successfully. You will also see your file appear in the list with the percentage of translation.
#If you have any problems, send the issue to the mailing list.

== Add a New Translation ==

If you are adding a new language for the first time to a project, click Add a new translation. The information that appears is pretty self-explanatory, but it is important to remember the following:

*Use the “Browse” button to find your local po file and select it.
*Ignore the "Select the target file" drop-down list, and enter "po/<languagecode>.po" in the "or enter it here" box.
*Finally, add some message that details what you did.
*Click Send. if all goes well, you will see a message at the top of the screen that the po file was added successfully.

[[Category:Localization]]

Using Transifex

2011-07-11T10:56:10Z

Andre: link recommended translation apps and mention other options

Go to https://meego.transifex.net/ and register. Once you have done that, select a language team to join. The lead for that team will then contact you and, if you agree on process for that language, you will be approved for that language team. If you don't see a team for your language, please consider starting it and being the lead, at least until you have critical mass.

Ideally, a language team should have a lead, at least 2 translators, and at least two editors/reviewers. It is essential that the same person that translates does not also review and approve their translation!

Once you've joined a language team, you can start translating! Transifex makes it easy for you to get the most up-to-date translation resource, translate, and post it back to the project.

'''Note:''' A few months ago, the MeeGo Transifex site was privately hosted at http://translate.moblin.org, but this site is no longer used. Please update your bookmarks to current site, https://meego.transifex.net/.

#Once approved for a language team, choose a MeeGo release you would like to translate from the [https://meego.transifex.net/ MeeGo Hub]. The latest release will be labeled and will likely receive the most attention.
#The next page displays a large list of translation statistics for all MeeGo language teams. Click on the language code for your team to see all of the resources available for translation.
#If translation has already started for a particular resource, simply click on the resource name to continue translation, or revise existing translations.
#If no translation exists yet for a particular resource, it will be listed at the bottom of the page. Follow the link for the desired resource to translate. Now you have landed on the resource page. Click "Add translation", choose your language from the dropdown menu, and click "Translate Online".
#After you are finished translating, remember to click the "Save and Exit" button near the page bottom.
#Now your translations are available for MeeGo developers to integrate into the distribution.

'''Note:''' If you are finished translating, be sure to unlock the translation so others on your team can work on it.

'''Note:''' Transifex lets you download translation resources so you can translate locally instead of through the web interface. For MeeGo Netbook UX PO files, we highly recommend using [http://www.poedit.net/ Poedit] to translate them. For MeeGo UX TS files, the Qt Linguist tool is recommended. There are other applications that also get the job done. [http://userbase.kde.org/Lokalize Lokalize] is a KDE program that works on Linux and Windows. [http://translate.sourceforge.net/wiki/virtaal Virtaal] is another great program. The biggest plus of these programs is the [http://en.wikipedia.org/wiki/Translation_memory translation memory]. You can load other translations, such as the Gnome translations, in the memory and the application suggests translations when a similar translation exists. This is handy for consistency. Some applications even contain interfaces to use e.g [http://open-tran.eu/ open-tran.eu] or [http://open-tran.eu/ Google Translate].

== Starting a Translation ==

For those of you familiar with PO Edit and editing po files, skip the next 3 steps.
#Open the bisho.pot file in PO Edit. In the Settings dialog, be sure to put your email address in the file heading (under “Last-Translator”) so we know who did the work and you get the recognition for doing it! Also, please be sure that the Content-Type in the header is "UTF-8." Make sure to enter this in the plural field to avoid corruptions and losing your work when you save: nplurals=2; plural=n!=1;
#Save the settings you just entered.
#Notice that there is a English string and right below it is msgstr “”. Put your translation of the English string inside those quotes.
#You can name your new PO whatever you like on your local drive, but it’s better to use the same name as the file in Transifex for easy identification when you want to upload it back.
#Go back to meego.transifex.net and go to the Bisho project.
#Scroll down until you see your language. (If it does not appear in the list, you will need to click "Add a New Translation." See below.)
#Select the last icon in the row of icons next to your language (the icon has a pencil in it and the mouse-over says "Submit a translation for po/xxx.po.")
#Use the “Browse” button to find your local file and select it.
#Click Send. If all goes well, you will see a message at the top of the screen that the po file was added successfully. You will also see your file appear in the list with the percentage of translation.
#If you have any problems, send the issue to the mailing list.

== Add a New Translation ==

If you are adding a new language for the first time to a project, click Add a new translation. The information that appears is pretty self-explanatory, but it is important to remember the following:

*Use the “Browse” button to find your local po file and select it.
*Ignore the "Select the target file" drop-down list, and enter "po/<languagecode>.po" in the "or enter it here" box.
*Finally, add some message that details what you did.
*Click Send. if all goes well, you will see a message at the top of the screen that the po file was added successfully.

[[Category:Localization]]

Quality

2011-07-07T19:03:38Z

Andre: Defect tracking: Move two links from deprecated Quality/Error_Management page here

= Quality =

This page is for MeeGo Quality Assurance related material.

== Getting Started ==
* [http://wiki.meego.com/Quality/getting-started How Can I Contribute]
== Projects ==

For all test reports see [http://qa-reports.meego.com http://qa-reports.meego.com]

{| border = 1 valign="top"
! Release
! Core OS
! Handset UX
! Tablet UX
! Netbook UX
! SDK
! In Vehicle Infotainment
|-
| Release 1.3
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.3/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
* [[/meego core feature/1.3 | Core Requirements]]
|
* [[Quality/Plans/Handset UX test plan|MeeGo HandSet UX Test Plan]]
* [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests Test Suite]
* [http://qa-reports.meego.com/1.3/Handset Handset Test Reports]
|
* Tablet UX Test Plan
* Tablet UX Test Suite
* [http://qa-reports.meego.com/1.3/Tablet Tablet Test Reports]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.3/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.3/SDK SDK Test Reports]
|
* [[/Plans/IVI Test Plan | MeeGo IVI Test Plan]]
* IVI Test Suite
* [http://qa-reports.meego.com/1.3/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|-
| Release 1.2
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.2/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/Plans/1_2_Handset_UX_test_plan MeeGo HandSet UX Test Plan]
* [[Quality/TestSuite/handset-test-suite|Test Suite]]
* [http://qa-reports.meego.com/1.2/Handset Handset Test Reports]
* [[Quality/HandsetQualityMetrics|Quality Metrics]]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/Tablet Tablet Test Reports]
* [[Quality/TabletQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/1.2NetbookTestPlan 1.2 SW Update Test Plan]
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.2/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.2/SDK SDK Test Reports]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|}

== QA tools ==

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
* [[Quality/QA-tools|Meet the team and find our tools]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet)
* [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution.
* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions how to automate test execution and image installations.

== Procedures and best practices ==

* [[Quality/Plans/Testability-checklist|Feature Testability Checklist]]
** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** This is a guide for QA contacts about how to comment on feature testability so as to provide as much information as possible to test developers.
*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

* [[/defects | Defects Management]]
* [[/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[/Bugzilla_Fields|Fields in a bug report]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [[/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]] -- WORK IN PROGRESS, please contribute
* [[/SysDebug | MeeGo Sys-Debug]] (finding the right component for a report)
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|MeeGo Bugzilla Customization Features]]
* [https://gitorious.org/meego-bugzilla Bugzilla Codebase repository] (move not finished yet)
* [[/MeeGoBugzillaRequestProcess|How to requests changes in Bugzilla code/UI itself]]

== Compliance Program ==
[[Quality/Compliance | MeeGo Compliance Program]] - the compliance spec (initially)

== Contact ==

* Mailing List: [http://lists.meego.com/listinfo/meego-qa MeeGo-QA]
* IRC: Channel #meego-qa on irc.freenode.net

== Meetings ==

General QA Meetings are held weekly on Tuesdays 07:00 UTC in the channel #meego-meeting on irc.freenode.net. [[Quality/Meetings|Click here for more information.]]

QA Tools meetings are held weekly on Tuesdays 08:00 UTC in the channel #meego-meeting2 on irc.freenode.net. [[Quality/QA-tools/Meetings|Click here for more information.]]

For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]].

== See also ==

* [[/Glossary | QA Glossary ]]
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]]
* [[Quality/Plans/Quality-considerations|Quality Considerations / Testing Quality Characteristics]]
** Some ideas around testing quality characteristics hopefully helping you identify what kind of things could be checked from applications - can be used as a frame to define test considerations – as a set of logical test cases - for applications targeting to run on MeeGo.

== Questions and Answers ==

* What is the QA contact expected to do actually?
** QA contact work with/support/advice/help package maintainers (see Fedora example [[http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility ]] or MeeGo guidelines for maintaining package [[http://wiki.meego.com/Packaging/Guidelines#Maintaining_a_Package ]]) and other users on QA related issues/questions for component in case.
*** Features ("Once a requirement is integrated, MeeGo QA verifies it by running the corresponding test cases." from [[https://meego.com/developers/requirements ]])
**** make testability analysis for features (yes or no value to testability field) and
**** identify "feature acceptance tests" together with product management and package maintainers that could be used at the end as a criteria for feature status to be changed as "VERIFIED".
*** Bugs ("QA Contact or Bug Submitter verifies bug fixing with the "how to re-produce" instructions in the original bug report when the bug is marked as RELEASED - FIXED." from [[http://wiki.meego.com/Quality/Bug_Life_Cycle_and_Handling ]])
**** facilitate the whole bug life-cycle from QA perspective, including ensure bug report completeness, follow up bugs by providing helpful or required information in timely fashion to accelerate bug fixing and verify the issue after fix is integrated, especially when the original reporter is not responsive or has difficulty to follow the bug up.
**** actively follow-up the bugs. Making sure the bug is attended properly, ping the default assignee or assignee or reporter to get visibility and comments on the progress, triage bugs, verify and close them whenever possible.

[[Category:QA]]

Community Office/Community device program/Nokia

2011-07-07T13:44:01Z

Andre: add description for my name

= Nokia Participation Details =
* Program Contact: [[User:qgil|Quim Gil]]
Update: Nokia N950 handsets are ready! https://meego.com/community/device-program/devices/nokia-n9-devkit

== N950 Devkit Program Details ==
* Device: Nokia N950 loaded with MeeGo 1.2 Harmattan
* Quantity: 250
* Additional Criteria / Terms:
** One submission per developer please
** Device to be loaned to participant for [period needed].
** May not be able to ship to certain countries / locations.
** Nokia employees are not eligible.
* Timeframe: distribution active.

'''QUESTIONS / ANSWERS & UPDATES:''' http://forum.meego.com/showthread.php?t=3597

== '''Updated Questions and answer for those people awaiting N950 Dev Kits:''' ==

1) '''If you have registered for the launchpad, please wait.'''
If you want to find out more information you can email the launchpad team, but a quick response is unlikely.
''Also, Quim will be emailing / sending all of the names and accounts across, therefore, if they have any questions / problems contacting devs they'll let Quim know.''

2) '''Timeline - Timescale'''
There is no defined deadline or timescale for this. Keep an eye on the delivered and pending sections below, as people are posting dates / times.
If things start happening and you feel you are being left out - please then email the Nokia Developer launchpad teams. But until then, not much communication if any will be received. Hold tight and please wait.
If your status is similar to someone else's, and in the same batch, and they get a device, wait a few days then fire a message to the launchpad team or here. No point asking the same questions on the forum. Most of the devs mentioned below are also on twitter, so ask there or elsewhere on the forums if really needed.

3) '''Timescale Part 2 - Patience!'''
Arranging, confirming, emailing, packaging and sending 250 devices is not a day's job.
Realistically expect a few weeks once they have started being sent out.
Be clear in all contact emails you send, to speed up the process - include account names and any other IDs requested/required. It is hard for people to swap from real names, nicknames, etc on a list of 250+ people..

4) '''People who already are registered with Launchpad'''
If you have a launchpad account (Lucky you) there is an option which allows you to select available devices, however, nothing is certain as of now, therefore that may not be the route.
Once the team start going through the list, it sounds sensible that they will start emailing / contacting the people on the list with instructions, confirmations and/or queries. (see below! - thank you Jaffa for the update)
Update - It seems the next step once the launchpad section is confirmed may be an email from '''no.reply-developer@nokia.com''', subject "A Nokia N950 is waiting for you".

5) '''Why have I heard nothing from Launchpad?'''
There is no launchpad confirmation email (But if you try to register again it says that there is already an application waiting) - therefore.... re-register if you have to. Just make sure you use the individual and not company registration. (There is however a developer registration email! - and logging in also proves that stage works!)

6) '''"I didn't realize this was happening, can I still apply for one?"'''
Answer- "Short term: register to http://developer.nokia.com and watch Nokia developer activities in your country. "
- '''This program is closed''', but as Quim says, keep your eyes on the internet, as there are other programs and similar things available, and different countries where Nokia reps do things too

7) '''Why is Nokia Developer saying the device program has been closed, and we still do not have our devices? *rant rant*'''
There are other device programs being run separately to the MeeGo DevKit program. The programs are not joined, but the team that sends out the devices is the same. Therefore, any messages you read are not exclusive to this particular set of 250 devices. Other programs may or may not appear across other Nokia sites, they are all separate from this one.

If you have been accepted, don't panic - they have not gone out yet! (As far as we all know!)
''Please do update this section if you feel other questions from the forum have been answered?''

== General thoughts on device program ==

The Nokia N950 is a platform available now for developers targeting the Nokia N9 and MeeGo handset apps in general. Technical details are available at http://developer.nokia.com/swipe

Candidates must be community developers ready to start working on new or existing open source applications, to be published in apps.meego.com and the Nokia Store. Links to your current projects are relevant! Deadline for applications: end of Tuesday, June 28th.

Questions & comments: http://forum.meego.com/showthread.php?t=3597

IMPORTANT: *commercial* developers are encouraged to apply directly at http://developer.nokia.com - thank you for your understanding.

== Results ==

'''WORK IN PROGRESS'''

For the sake of transparency and collaboration:
* Please link your name to a page describing your Nokia N950 related work e.g. a wiki page.
* Add here one line of text summarizing the project(s) and feature(s) you are concentrating.
* We haven't done the 'Nokia employee' check yet. If you happen to be one, contact Quim Gil.

=== Completed ===
Participants that have received the Nokia N950, sorted by meego.com nick. You know this device program is completed when we have reached 250:

# aklapper (Andre Klapper)
#*General testing and bug hunting
# [[User:Jaffa|Jaffa]] (Andrew Flegg)
#*Porting apps from Maemo (Attitude & Hermes), developer tools, and apps.meego.com workflow. [[User:Jaffa|"Want to know more?"]]
# [[user:thp|thp]] (Thomas Perl)
#* [http://gpodder.org/ gPodder] - Integrating gPodder with Harmattan (including specific APIs)
#* Open source work on Python-related APIs (PySide, etc..) + Python tutorials
#* Get [[Games|Mong]] in shape for Harmattan
#* Port over some of my existing [http://maemo.org/profile/view/thp/ Maemo 5 apps]
# Joerg Reisenweber '''ID sent''', '''Accepted for the Nokia Developer Launchpad program''' '''Ordered: OID-052736'''
#* USB hostmode. Give N9(50) access to external storage etc. (co-devels: Thomas B. Ruecker, MohammadAG)
#* Review the core functionality and find other similar fields to tackle (see *# starhash-enabler for N900). To mind comes: user profiles (refer the modest "default" & "silent" on fremantle), dialplans, location aware event triggers (cinema profile triggers automatically on entering the building), improved battery management and monitoring, theft protection and recovery...
#* cablefinder based on fast magnetometer readout detecting 50/60Hz fields (co-devel: alterego)
#* I am contributing/associated to:
#**SnapGo / Ryan Abel [consulting on low level stuff]
# X-Fade (Niels Breet)
#* Set up & Testing Harmanttan building on MeeGo Community OBS

=== Accepted, waiting for the N950 ===

==== Batch One ====

[[User:aaporantalainen|Aapo Rantalainen]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
First goal: [http://www.umsic.org/jammo/ JamMo] (will need some underlying libraries, e.g. [http://www.clutter-project.org/ clutter])

[http://wiki.meego.com/User:Broothy Ádám Balázs]
* '''Sent my Account ID to Quim, i'm already Nokia launchpad member. Awaiting any reply.'''
* [http://store.ovi.com/content/113753 Switchboard]
** [http://www.youtube.com/watch?v=GdskgAfjjxc MobileMind]

Adam Pigg '''ID sent''', '''applied for Nokia Launchpad''', '''waiting for reply''' 
Porting my Qt/QML apps/games from maemo, and further work on Kexi and some more QML games
[http://www.piggz.co.uk My Site]

[[User:captianigloo|Aguirre Nicolas]] (captainigloo) '''ID sent''', '''Launchpad:Accepted(07-Jul-2011)''' | '''N950eMail:Yes''' | ''' Ordered:Yes ''' | '''Received:No''' 
Porting [http://enna.geexbox.org Enna], [http://svn.enlightenment.org/svn/e/trunk/E-MODULES-EXTRA/elfe elfe] and all [http://www.enlightenment.org EFL/Enlightenment] libraries to Meego.

[[User:Qole|Alan M Bruce]] '''ID sent''', '''applied for Nokia Launchpad''', '''waiting for any reply''' 
[http://maemo.org/downloads/product/Maemo5/easy-deb-chroot/ Easy Debian] and other projects as they arise

Oleg Bodnarchuk(bloody)'''ID sent''', '''applied for Nokia Launchpad''' 
Developing Wiki-based offline database.

[[User:mardy|Alberto Mardegan]] (Mardy) 
Developing QML port of [http://www.mardy.it/mappero Mappero], possibly [http://www.mardy.it/oculo Oculo] and [http://neverball.org Neverball] (for the latter I'm now working on a N900 port).

Aleix Pol (apol) '''ID sent''', '''applied for Nokia Launchpad''' 
Porting "horaris" and "kanban" maemo applications, finally get to have a usable KAlgebra Mobile version working on MeeGo, hopefully drag other KDE applications with this effort.

[https://meego.com/users/avis Alexander Terekhov] (Avis) '''ID sent, already a Launchpad member''' 
Porting and improving [http://qt-apps.org/content/show.php/Smart+Shopper?content=139742 Smart Shopper] project.

[[User:amandalam|Amanda Hoi Ching Lam]] (amandalam) '''ID sent''' | '''Launchpad:Accepted(05-Jul-2011)''' | '''N950eMail:Yes''' | ''' Ordered:Yes ''' | '''Received:No''' 
Traditional Chinese language and utility apps for the MeeGo & Harmattan platforms, including but not limited to a Chinese character lookup app, and applications localized for the Traditional Chinese communities in Hong Kong, Macau and Taiwan. [https://sites.google.com/site/amandahoic/Home/ Amanda's Software Projects]

[https://meego.com/users/andreagrandi Andrea Grandi] (Andy80) ''' "A Nokia N950 is waiting for you" email received, device ordered. ''' 
QML native client for Soma.fm radio. Based on the old mSoma: https://gitorious.org/msoma

[https://meego.com/users/andrei1089 Andrei Mirestean] (andrei1089) '''ID sent, applied for Nokia Launchpad, waiting for reply'''
 Develop a pedometer application based on the [http://maemo.org/downloads/product/Maemo5/pedometerhomewidget/ Pedometer Widget for N900]

[[User:fiferboy|Andrew Olmsted]] (fiferboy) '''ID sent''', '''Launchpad activated, order email sent, waiting for delivery details''' 
[http://andrew.olmsted.ca/meego Fiferboy's Projects] (Birdlist, Personal Lexicon, other ideas), porting and packaging some pure Qt apps

[[User:wazd|Andrew Zhilin]] (wazd) '''ID sent''', '''Already a Launchpad member (but my Launchpad account hasn't activated)''' 
[http://tabletui.wordpress.com], OMWeather, Live Wallpapers, BlueMaemo, Ati85, QML gPodder, tons of other design-related stuff

[[User:anidel|Aniello Del Sorbo]] (anidel) '''Sent my IDs to Quim, I was already Nokia a launchpad member. Awaiting any reply.''' 
Porting [http://maemo.org/downloads/product/Maemo5/xournal/ Xournal] from Maemo to Harmattan/MeeGo

Antti Pohjola (Summel1) ''' ID sent, Applied for the Nokia Developer Launchpad program ''' 
Porting [http://www.summeli.fi/?p=2453 AntSnes] and [http://www.summeli.fi/?p=2520 gpSP] from Symbian^3 to Harmattan/MeeGo.

[[User:awhiemstra|Arjen-Wander Hiemstra]] 
Porting [http://gluon.gamingfreedom.org Gluon] to MeeGo/Harmattan.

[https://meego.com/users/djarty Artem Sereda] (DJArty) '''Nokia Developer User ID sent''', '''Applied for the NDL program''' - '''(Done) Launchpad for individuals(05-Jul-2011–05-Jul-2012)''' 
Porting qutIM, openpref, arora, links, groove, microdc, Ukrainian localization.

Assaf Paz (damagedspline) '''ID sent''', '''applied for Nokia Launchpad, Launchpad for individuals (06-Jul-2011–06-Jul-2012)''' 
Adapting [http://code.google.com/p/qwazer/ Qwazer] to also work on Meego, hopefully create an Exchange Webmail client in pure QML (N900 was the initial target), Hebrew support

[[User:Bart-cerneels|Bart Cerneels]](Stecchino) '''ID sent, applied for Nokia Launchpad, waiting for reply''' 
Mobile UX' for Amarok using QML. [http://amarok.kde.org Amarok website]

[[User:khertan|Benoît HERVIER]] (Khertan) '''ID sent''', '''waiting answer from Nokia Developer Launchpad program''' 
Porting [http://khertan.net/khteditor KhtEditor] a source code editor, [http://khertan.net/khweeteur Khweeteur] a twitter/identi.ca client, [http://khertan.net/python_sdist_maemo Sdist_maemo] and developping KhtSync a automated file synchronization application, and KhtDrive an app to measure car and driver performances for eco driving.

[[User:Termana|Bradley Smith]] (Termana) '''ID sent, Launchpad: Accepted, N950 Email: Received, Ordered: Yes, Received Device: No''' 
Developing a karaoke game with built-in pitch correction.

[[User:arfoll|Brendan Le Foll]], '''ID sent''', '''applied for Nokia Launchpad''' 
Porting XBMC + MeeGo TV stuff + doing audio continuums using pulseaudio.

[[User:Stskeeps|Carsten Munk]], '''ID sent''', '''applied for Nokia Launchpad''' (done), Launchpad for individuals (06-Jul-2011–06-Jul-2012) but no mail regarding it yet.

. MeeGo CE N950/N9 contributions and Wayland on these devices.

Christian Pühringer (cip) '''ID sent, already a Launchpad member''' 
[https://github.com/cip/WikiOnBoard/wiki WikiOnBoard] Offline reader for Wikipedia using [http://openzim.org zim] format.

[[User:Clint|Clint Adams]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Libre.fm-related software development and porting, advocacy

[[User:Cpscotti|Clovis Scotti]] (cpscotti) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Developing the "connected snowboarding" [http://www.pushsnowboarding.com Push Snowboarding] application/project. Also, I'll be very happy to port other apps I did (mainly for Maemo) + new projects.

[https://meego.com/users/conny Cornelius Hald] (Conny) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
[http://conboy.garage.maemo.org Conboy] 
[http://thp.io/2011/mong Mong aka Plonk]

[https://meego.com/users/zehjotkah Cosimo Kroll] (zehjotkah) '''ID sent''' | '''Launchpad:Accepted(05-Jul-2011)''' | '''N950eMail:Yes''' | ''' Ordered:Yes ''' | '''Received:No''' 
[http://wiki.maemo.org/MeeGo_Coding_Competition_2011 MeeGo Coding Competition 2011]

Cristian Grozea '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
magnus-plus photo: an application that combines a camera-based magnifier with more advanced image processing techniques, that would enable one to: 
- use it as a magnifier (with optional light from the camera LED). 
- use it as a photo negatives lightbox that automatically inverts the negatives and adjusts the colors for proper display:
the user just have to hover it over the (back-lit) negatives and on the screen the corresponding positive (or magnified part of it) is displayed in real-time. 
- use it as an EVF add-on to SLRs to help with manual focus, leveraging the possibility of amplifying contrast and magnifying. 

Damian Waradzyn '''ID sent''' | '''Launchpad:Accepted(05-Jul-2011)''' | '''N950eMail:Yes''' | ''' Ordered:Yes ''' | '''Received:No''' 
Porting and further development of [http://talk.maemo.org/showthread.php?t=58402 CloudGPS]

Daniel Martin Yerga '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting my Maemo applications: [http://maemo-wordpy.garage.maemo.org/ MaStory], [http://cusl4-cservices.forja.rediris.es/ CasualServices], [http://pyrecipe.garage.maemo.org/ Pyrecipe], [http://maemo.org/downloads/product/Maemo5/copernicium/ Copernicium], [http://stockthis.garage.maemo.org/ StockThis], and developing new ones, like [https://gitorious.org/r-dmobiley R&DMobiley].

David Derby '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting [http://www.6809.org.uk/dragon/xroar.shtml XRoar - Dragon & CoCo emulator] and [http://icculus.org/avp/ Aliens versus Predator (Gold Edition) game engine].

David Galindo

[[User:Lbt|David Greaves]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Mainly CE, Harmattan and Apps to start with. Hopefully Surrounds later.

Diego Marcos '''ID sent''', '''Applied for the Nokia Developer Launchpad program. Waiting for reply''' 
The goal is porting to mobile devices open source data visualization tools of astronomical data aimed at outreach and science communication. I've been previously working on Qt/QML desktop applications based on stellarium.org
http://www.youtube.com/watch?v=COkwscvTnnM&feature=youtube_gdata_player

[[User:Dimitar | Dimitar Pashov]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Port my poppler-qt4 based pdf viewer and see how to make use of the touch screen. Try the abilities of the n9/50 HW with an engineering/scientific 3D model viewer. Implement some other ideas.

[[User:druid23 | Dru Moore]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
To port / create multi-track editing and mixing software to Meego / Harmatten, and multimedia capabilities in general (potentially video editing) 
Additionally, to port remote controls for various networked media players (Singbird, Foobar2000, Squeeze, VLC etc).

[[User:rambo | Eero af Heurlin]] ('''ID sent''' (I think), '''Applied for the Nokia Developer Launchpad program''') 
Port [http://maemo.org/downloads/product/Maemo5/maecalories/ MaeCalories], [http://maemo.org/downloads/product/Maemo5/mobilehotspot/ Mobile hotspot] (possibly, depends on many things and might not be actually neccessary), I'm also looking into some wearable computing and augmented reality stuff, I'll have to see how suitable platform the N9(50) is going to be for that.

[[User:Emocow | Ferdinand Mayet]] ('''Ordered N950 and waiting for arrival''') 
Development of a golf GPS application

Frank Sievertsen '''ID Sent, Launchpad member now''' 
Open-Source Spideroak Mobile Client and other apps

Gary Birkett '''ID Sent, Applied for Nokia Developer Launchpad program, waiting for approval''' 
N9 Qt port of liqcalendar

[http://meego.com/users/garyd Gary Driggs] ('''dev ID sent, already reg'd as Launchpad member''')
Porting [http://www.gnu.org/s/gnash Gnash] to MeeGo ARM devices.

George Ruinelli '''ID sent, Applied for the Nokia Developer Launchpad program''' 
Porting my [http://maemo.org/packages/view/sleepanalyser/ SleepAnalyser] from MAEMO as well as other smaller apps I wrote/ported. See [http://wiki.maemo.org/User:Caco3] for details.

[[User:gbraad | Gerard Braad]] '''ID Sent, Applied for Nokia Developer Launchpad program, waiting for approval''' 
Porting of of Node.JS, phonegap, unhosted and a mobile org-mode editor. Aiming for good integration with the MeeGo API and Qt Mobility. Code will be published on [https://github.com/gbraad github] and described on my [http://gbraad.nl/ blog].

[http://apachelog.wordpress.com Harald Sitter] '''ID sent :: Launchpaded :: Ordered''' 
[http://git.videolan.org/?p=QtMobileVLC.git;a=summary Porting VLC] to handsets and tablets using Qt for UI awesomeness.

[[User:helihyv|Heli Hyvättinen]] '''Device ordered''' 
Porting Ghosts Overboard (a game) and Chess Clock from Maemo and adding new features to the former.

[[User:bergie|Henri Bergius]] 
Porting Buscatcher, Midgard and Node.js -related tools to MeeGo. However, I've withdrawn my device program application because I already got a N950 via Helsinki MeeGo Network.

Hiemanshu Sharma '''ID Sent, Applied for Nokia Developer Launchpad program''' 
Currently working on porting [[http://forum.meego.com/showthread.php?t=3660|Komedia]]. More apps in the pipeline including Quassel (IRC Client), a Google Reader (name suggestions are welcome) and a 'Line of the day' kind of app (a glorified version of cowsay). Also working on getting an opencv port to give way for Face Detection/Facial recognition APIs.

[[User:Divan|Ivan Daniluk]] ''' ID sent, Applied for the Nokia Developer Launchpad program''' 
Porting [[User:Divan|my Maemo5 applications]], adding full Vkontakte support, Russian and Ukrainian localization and developing new apps in progress..

Janne Mäkinen '''ID sent''', '''applied for Nokia Launchpad''' 
Porting/Rewriting Maemo 5 stuff

[[User:Javispedro|Javier de San Pedro Martín]] '''device order placed''' 
Porting my [http://wiki.maemo.org/User:Javispedro Maemo 5 applications and SDL games], and [http://gitorious.org/hsdl/pages/Home SDL] itself.

Jens Persson (xerxes2) '''ID sent''', '''applied for Nokia Launchpad'''
* [http://gpodder.org/panucci Panucci] - Resuming audiobook and podcast player
* Meego CE

[[User:jbos|Jeremias Bosch]] (jbos) '''ID sent''', '''applied for Nokia Launchpad'''
* Bringing Peregrine Communication Client to Harmattan
* http://www.peregrine-communicator.org
* MeeGo CE

[[User:vandenoever|Jos van den Oever]], '''ID sent''', '''got Launchpad for individuals (06-Jul-2011–06-Jul-2012)''' 
Porting [http://webodf.org WebODF] to MeeGo using QML and JavaScript.
[http://www.webodf.org/redmine/projects/webodf/wiki/WebODF_on_an_N950 WebODF on an N950]
Experiment with a semantic logging tool.
Experiment with a [http://blogs.kde.org/node/4161 metronome application] in QML.

[[User:Metropt|Jose Xavier]], '''ID sent''', '''Launchpad for individuals(06-Jul-2011–06-Jul-2012)''' 
My goal is to port the OpenPilot Ground Control Station to the MeeGo platform and adapt the UI for a better mobile experience. You can see more information about OpenPilot GCS here: http://wiki.openpilot.org/display/Doc/Ground+Control+Station+User+Manual

[[User:Bundyo|Kamen Bundev]] (Bundyo), '''ID sent''', '''Launchpad activated, notification email received, device ordered, not received yet''' 
Rewriting Search Tool, porting Maemo 5 work, NodeJS, possible Tear rewrite.

Karl Johan Grøttum

[[User:kemargrant | kemar grant]], '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
My goal is to bring Screen Mirroring to Meego along with playing local files
easily to a desktop. The app is called groundwork and it is opensource. Code will be shifted to Launchpad once I can begin testing on a meego device.
http://code.google.com/p/groundwork/

Ken Young 
Initially I will port the Maemo [http://wiki.maemo.org/Orrery Orrery] program, and add support for the magnetometer. I will
also port some other apps from Maemo 5.'''ID sent''', '''applied for Nokia Launchpad''' 

[[User:Kimitake|Kimitake]] '''ID sent, already a Launchpad member''' 
developing Qt-based micro blogging client for twitter, identi.ca, wassr, jp

[[User:Kulakov|Kirill Kulakov]], '''ID sent''', '''Submitted credentials to Nokia Launchpad''' 
MySocials project - clients, libraries and plugins for frameworks and platforms for social networks

[[User:lostinmirkwood|Kristopher C. Kantor]] (lostinmirkwood) '''ID sent''' | '''Launchpad:Accepted(05-Jul-2011)''' | '''N950eMail:No''' | ''' Ordered:No ''' | '''Received:No''' 
* Continuing Development of [http://ansela.garage.maemo.org/ Ansel-A]: Digital Darkroom for Qt Devices

[[User:shadymilkman|Kyle Thomas]] 
Creating Reedit: [http://www.shadymilkman.com/p/n9-project.html Reedit] A full featured Reddit list browser 
'''Submitted credentials to the N.D.Launchpad for application review, waiting for instructions.'''

[[User:Creamygoodness|Lance Colton]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Working on Proximus during July, I will see what we can do with Conky after that.

Lasse Kärkkäinen '''ID sent''', '''applied for Nokia Launchpad''', '''waiting for reply''' 
Porting [http://performous.org/ Performous] singing/band game from PC to N900 and MeeGo

Lasse Stenberg, '''ID sent''', '''applied for Nokia Launchpad''' 
Porting and further developing [http://talk.maemo.org/showthread.php?t=72982 Mapsi]

Laszlo Papp (Already got one earlier, thus I do not need a new one ;) )

liang wei (foolegg), '''ID sent:Yes''' | '''Launchpad Accepted:Yes''' | ''' Ordered:Yes ''' | '''Received:No''' 
[[Cuteinputmethod]] is a Chinese Input Method, designed for handset device. 

Luis Felipe Strano Moraes '''ID sent''', '''applied for Launchpad membership''' 

Luiz Augusto von Dentz

Marat Fayzullin (fms) '''ID sent''', '''already a Launchpad member''' 
Porting the following:
[http://fms.komkon.org/SlideRule/ SlideRule],
[http://fms.komkon.org/ColEm/ ColEm],
[http://fms.komkon.org/fMSX/ fMSX],
[http://fms.komkon.org/Speccy/ Speccy],
[http://fms.komkon.org/ATI85/ AlmostTI],
[http://fms.komkon.org/MG/ MasterGear],
[http://fms.komkon.org/iNES/ iNES],
[http://fms.komkon.org/VGB/ VGB],
[http://fms.komkon.org/VGBA/ VGBA].
Also expecting to port the FBReader and an IRC client (although most likely not XChat).

[[User:deimos|Marco Bavagnoli]] (deimos) '''ID sent''' | '''Launchpad:Accepted(05-Jul-2011)''' | '''N950eMail:Yes''' | ''' Ordered:Yes ''' | '''Received:No''' 
I'm porting [http://mediadownloader.cz.cc/?page_id=2 mediadownloader] application just ported to [http://mediadownloader.cz.cc/?p=153 maemo] and here a [http://www.youtube.com/watch?v=_Dsj2piBQCw video].

[[User:Mece|Marcus Wikström]] (mece) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
[http://talk.maemo.org/showthread.php?t=73490 Tweed Suit] for N9/50. Probably Qlister and also planning an location based tracking service/app.

Marijn Kruisselbrink '''ID sent''', '''Accepted for the Nokia Developer Launchpad program'''

[[User:mgedmin|Marius Gedminas]] (mgedmin) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Planning to port [http://mg.pov.lt/gtimelog GTimeLog].

Marko Mattila (zchydem) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
QuickFlickr, QML based Flickr client for mobile handsets.

[http://wiki.meego.com/User:Vgrade Martin Brook] (vgrade) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 

I would plan to contnue my contributions to the N900 Community Edition of MeeGo which I assume will push right through into the N9. I am very interested in contributing to the exciting new architecture built on Wayland to give this device the best user experience.

Local Network Meetups, Cambridge, Birmingham, Koln, Dusseldorf

Martin Grimme (pycage) '''ID sent''', '''Launchpad member but device is not listed''' 
Doing the Community Apps installer client. Also targetting Harmattan with my OSS MeeGo apps (which are currently mostly running on the WeTab).

[http://wiki.meego.com/User:Martink Martin Kolman] (MartinK) '''ID sent''', '''applied for the Nokia Launchpad''' 
Porting the modRana GPS navigation system and Mieru manga and comic book reader.

[[User:twoboxen|Matt Hawkins]] (twoboxen) '''ID sent''', '''Already a Launchpad member''' 
Open sourcing and working on my cross-platform OpenGL engine (HawkEngine) and several [https://sites.google.com/site/hawkorn/games games]. This engine builds projects and binaries for Qt, iOS, Android (though the NDK is touchy), WebOS, Glut, etc.

[[User:zas|Matti Henrik Karjalainen]] (zas) '''ID sent, applied for Nokia Launchpad''' 
[http://tols17.oulu.fi/~matkarja/meego/ Projects] (Currently working on Tap 'em (game))

[http://forum.meego.com/member.php?u=9286 Michael Muth] (helex) '''ID sent, already applied for the Nokia Launchpad''' 
[http://talk.maemo.org/showthread.php?p=1001316 ClipMan], [http://talk.maemo.org/showthread.php?t=52589 DreamRemote], TcpKeyboard, something like [http://talk.maemo.org/showthread.php?t=72408 ConkyLayoutSwitcher] (have to see how the UI works in detail - need to create it from scratch)

[http://blog.mikeasoft.com/tag/maemo/ Michael Sheldon] (Elleo) '''ID sent, accepted into Nokia Launchpad''' 
Creating a [http://libre.fm Libre.fm] radio client and porting [http://www.jokosher.org Jokosher] to small screen devices.

[http://blog.cihar.com/ Michal Čihař] (Nijel) '''ID sent, applied for Nokia Launchpad''' 
Creating a [http://wammu.eu/ Gammu] application for phone for data synchronization and backup.

Michele Tameni ( netvandal ) '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''

- Luca's Mirror: It’s a simple app that transform your phone into a hand-held mirror with some other cool addictions.

- Semantic experiment : Experiment with Notification Area mixed with the semantic information stored in tracker, reacting to user action with usefull notification
More info [http://michele.tameni.it/project/meego/ Here]

Mike Choy (mikec): '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''
Porting svgclock, Maesynth and Maelophone from N900 Python to QML and C++. Stress testing the new [https://projects.developer.nokia.com/qtgameenabler Qt Game Enabler] to see if we finally have low latency audio support in Qt. Will also look to see if we can get midi sample support via Wild Midi or equivalent.

Mikko Vartiainen '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''
http://forum.meego.com/showthread.php?t=3607

[https://projects.developer.nokia.com/home/user/mmlado Mladen Milankovic] '''IDs sent''' 
Develop games in QML

Mures Andone '''ID sent'''. '''Waiting answer from Nokia Developer Launchpad program''' 
Develop location-aware apps with Qt/QML, an enhanced e-book reader based on FBReader engine.
Also an enhanced video player with this main feature: start playing video on desktop/laptop, pause, resume playing from device (with output to device screen), continue playing, pause, switch to tv-out, resume, play, pause, switch back to desktop and so on. Current project: Maemo Application Launcher: http://sourceforge.net/p/maplau/code/

[[User:Nielsmayer|Niels Mayer]] '''[https://projects.developer.nokia.com/home/user/NielsMayer Nokia Developer ID] sent''', '''Applied for the Nokia Developer Launchpad program''' 
[http://wiki.meego.com/Tubelet-and-cutetube-port Port cutetube-qml to MeeGo tablet UX/harmattan UX.] 
[http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego YouTube Direct For MeeGo]

[[User:olka|Oleksandr Kachur]] '''ID sent'''. '''Waiting answer from Nokia Developer Launchpad program''' 
Developing cloud music player integrated with Google music, Amazon music and last.fm services.

Olle Tränk (zeamoceq) '''ID sent''', '''Applied for the Nokia Developer Launchpad program - (Done) Launchpad for individuals (05-Jul-2011–05-Jul-2012), N950 Email: Received, Ordered: Yes, Received Device: No''' 
Porting [http://qticksize.zeamoceq.net qTickSize] (interface to Swedish online stock broker)

Oscar Martinez '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Port 2d puzzle board game [http://kde-apps.org/content/show.php/kMagnet?content=109111 kMagnet] or a new 2d board puzzle game

[[User:Lorenzph|Philip Lorenz]] ('''Ordered N950 and waiting for arrival''') 
Development of a hiking application supporting the user when planning and executing the trip.

[[User:Ph5|Philipp Zabel]] (pH5) ''' N950 ordered ''' 
Integration of [https://www.torproject.org/ Tor] support, porting of [http://maemo.org/downloads/product/Maemo5/frogatto/ Frogatto], [https://garage.maemo.org/projects/beifahrer/ Beifahrer] and [https://garage.maemo.org/projects/cinaest/ Cinaest]

Randall Arnold
Application testing, local and regional meetup/event demos, product evangelism, peripheral design

Ravi Vagadia '''ID Sent''', '''Applied for the Nokia Developer Launchpad Program''' 
VLC Remote & Trip Management App.

Ray Donnelly

[[User:Rlinfati|Rodrigo Linfati]] ''' ID send: 30-Jun-2011, Launchpad-Applied: 30-Jun-2011, Launchpad-Accepted: 06-Jul-2011 | N950eMail: 07-Jul-2011 | Ordered: 07-Jul-2011 | Received:No '''

* Upgrade GoogleLatitude to the current API
* Find your Frient: a apps that inform you position directly to you friend without any external server.

Roman Morawek

[http://wiki.meego.com/User:Wonko Ruediger Gad (wonko)] '''ID sent''' | '''got Launchpad for individuals''' | '''N950eMail:Yes''' | ''' Ordered:Yes ''' | '''Received:No''' 
Amongst other things I'll port my existing applications for Maemo5/Fremantle to MeeGo/Harmattan: VU Meter, StultitiaSimplex, Zeecontrol, Advanced Clock Plugin (for details please see my page).

[[User:generalantilles|Ryan Abel]] (GeneralAntilles) '''ID sent''', '''Accepted the Nokia Developer Launchpad program''', '''Ordered device''' 
Working with fiferboy on a photographer's application suite ([http://thousandsparrows.com/meego/ SnapGo], currently) to include feature like a light meter and GPS track recording.

Sam Bristow

[[User:Eipi|Sanjeev Visvanatha]] (EIPI) , '''ID sent''', '''Accepted at Nokia Launchpad (6/7/2011), waiting for Email with ordering instructions''' 
Porting MaeFlight from Maemo 5, and adding functionality for Harmattan

[[User:Seif|Seif Lotfy]], '''ID sent''', '''waiting answer from Nokia Developer Launchpad program''' 
My goal is to port the Zeitgeist to MeeGo with all the fun stuff with it. I already have a Qt port for "El Loco".

Sergey Ivanov '''ID sent, waiting reply of Launchpad program''' 
Developing software for the mobile operating system MeeGo, associated with the processing of audio and video streams.

[[User:Spenap|Simón Pena]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting and enhancing Maevies from Maemo 5 to Meego/Harmattan

Simon Pickering (lardman) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting mBarcode, working on Augmented Reality app (mAR), time and location event app (Proximus), additional location methods (offline cellid, magnetic field line direction)
Page here: http://wiki.meego.com/User_talk:Lardman

[[User:Somnathbanik|Somnath Banik]]: '''Nokia Developer ID sent''' | '''Launchpad:Accepted(06-Jul-2011–06-Jul-2012)''' | '''N950eMail:No''' |''' Ordered:Yes''' | '''Received:No'''

* Porting my existing Symbian^3 multimedia applications to MeeGo/N9 with a new and exciting UI components of Harmattan/MeeGo.
* Creating simple and easy open source application to inspire beginner developers to work on MeeGo/N9 technology.

Stani Michiels

[[User:v13|Stefanos Harhalakis]]: '''Nokia Developer ID Sent''', '''Applied for Nokia Developer Launchpad Program''', Waiting for reply
* Port WifiEye from maemo to meego
* Port MaeGirls from maemo to meego
* Perhaps complete MaeSlap and release it for meego

Stephen Gadsby (sjgadsby) '''ID sent''', '''accepted into Nokia Launchpad''', '''device ordered''' 
writing a [[User:Sjgadsby#Preferred Shopper Card Wallet|not-yet-named wallet for store loyalty cards]]

[[User:vitaminj|Stephen to Spencer]] (VitaminJ) '''ID sent, applied for the Nokia Developer Launchpad program''' 
[http://jenkins.vitaminj.co.uk/job/meex/ Meex], a portable DJing application

Susanna Huhtanen

Tadej Novak '''ID sent''', '''Launchpad:Accepted(06-Jul-2011)''' | '''N950eMail: No''' | ''' Ordered: No ''' | '''Received: No''' 
Porting my desktop IP TV player and schedule to Meego

[http://wiki.meego.com/User:Kenya888 Takahiro Hashimoto(kenya888)] '''ID sent, waiting reply of Launchpad program''' 
porting qimsys/mozc to Harmattan/MeeGo, developing streaming multimedia player with QML

Tasuku Suzuki

Teemu Hukkanen

[http://teom.wordpress.com Teo Mrnjavac] '''ID sent, Launchpad:Accepted | N950eMail:Yes | Ordered:Yes | Received:No 
[http://ur1.ca/4kkwh Porting] [http://amarok.kde.org Amarok] to tablets and handsets running MeeGo/Harmattan.

Thomas Cherryhomes - Lead Developer for LinuxMCE - '''ID and Launchpad ID sent'''
* LinuxMCE is a next generation smart home platform encompassing media, home automation, telecom, and security features. http://www.linuxmce.org/
* A 25 min demo of the software can be seen here: http://video.google.com/videoplay?docid=2176025602905109829
* Nokia N950 will be used as a test platform for the new QML/Qt Quick based qOrbiter we are writing to replace our existing Orbiter software, qOrbiter videos here:
** http://www.youtube.com/watch?v=NDGagn3EciA
** http://www.youtube.com/watch?v=oUHrCdBgoyQ

[[user:harbaum|Till Harbaum]] '''ID sent, applied for the Nokia Developer Launchpad program'''
* First action: Try to get [http://www.harbaum.org/till/cacheme CacheMe] to work nicely
* Might have to work on qt theming (and convince people that this is a good thing :-)
* [https://build.pub.meego.com/project/show?project=home%3Aharbaum Community OBS home project]
* And of course i'd like to port some of my previous Maemo projects ...

[[User:timoph|Timo Härkönen]] (timoph) '''Waiting for post to deliver the device'''
* [http://gitorious.org/random-timoph impuzzle, etc.]
* [http://timoph.fi timoph.fi]
* [https://build.pub.meego.com/project/show?project=home%3Atimoph Community OBS home project]

[http://wiki.meego.com/User:Venemo Timur Kristóf]

* '''Sent my Account ID to Quim, applied at Nokia launchpad. Awaiting any reply.'''
* [http://wiki.meego.com/User:Venemo/HarmattanPlans My Harmattan Plans]
** [http://gitorious.org/colorful-apps/puzzle-master Puzzle Master]
** [http://forum.meego.com/showthread.php?t=3711 Public transportation app] (Click on the [http://forum.meego.com/showthread.php?t=3711 link] and post to the thread if you are interested to contribute.)
** [https://gitorious.org/colorful-apps/memory-game Memory game]
** Labirynth game (No code available yet)

Tom Swindell
* [[User:Tswindell/CommunityApplicationDevelopment]]: Columbus Navigation Toolkit, Media IM Status Updater.

[[User:tlaukkanen|Tommi Laukkanen]] '''ID sent''', '''applied for Nokia Launchpad. Awaiting any reply'''
* Facebook client [http://kasvopus.com Kasvopus], Twitter client [http://twimgo.com TwimGo], Google Reader client [http://newsflow.mobi NewsFlow], FourSquare client [http://nelisquare.com Nelisquare]

[[User:toninikkanen|Toni Nikkanen]] '''ID sent''', '''applied for Nokia Launchpad''', '''order sent'''

[https://meego.com/users/sandst1 Topi Santakivi] '''N950 ordered'''
* Porting FunkeySynth, a MeeGo Tablet synthesizer to Harmattan
* Demo clip and further info in [http://sandst1.wordpress.com/ my blog]

Tuomas Kulve

[https://meego.com/users/vasvlad Uladzislau Vasilyeu] (Vasvlad) '''ID sent, applied for the Nokia Developer Launchpad program''' 
* Porting OMWeather to Harmattan

[[User:drowne|Valerio Di Donato]] '''ID sent, applied for Nokia Launchpad ''' 
Location-Based games and application development, mobile game design. Junomi Developer ( serious game presented at Games for Health Conference in Boston, May 2011 )

Ville Jyrkkä

[[User:Vranki|Ville Ranki]] '''ID sent, applied for Nokia Launchpad ''' 
[http://www.siilihai.com Siilihai web forum reader], [http://www.youtube.com/watch?v=erTAMOzdf0Y&feature=related Drone Taxi], PPCards.

Willem Liu

[[User:ph0b|Xavier Hallade]] '''ID sent, applied for Nokia Launchpad ''' 
Writing tutorials to help other developers to step in MeeGo / Building MeeGo Paris network / Developing an audio player to access to more than 47 000 webradios referenced on AOL shoutcast (by name, genre, current track)

Yann Bieber '''ID sent, applied for Nokia Launchpad ''' 
Porting [http://code.google.com/p/wagic/ Wagic] on Harmattan based on either Qt or SDL

Zaheer Merali '''ID sent''' '''Applied for the Nokia Developer Launchpad (for individuals) program'''
* Porting [http://gstreamer.freedesktop.org GStreamer] plugins not shipped by Nokia to Harmattan
* Porting [http://www.flumotion.net Flumotion] an open source streaming solution to Harmattan taking advantage of the hardware encoding and the camera

Zap Andersson '''ID sent''' '''Applied for the Nokia Developer Launchpad (for individuals) program'''
* Porting [http://maemo.org/packages/view/zaploc/ ZapLoc] app to Qt/Meego (currently pygame/Maemo)
* Porting game "Slightly Annoyed Rodents" (yet to be released) to Qt/Meego (currently pygame/Maemo)

[[User:leafjohn|Lifu Zhang(leafjohn)]] '''ID sent, applied for Nokia Launchpad (request submitted, waiting for review) '''
* Create an opensource Qt astrology app for handset, Project Page: [https://github.com/cardmaster/qastro/tree/develop qastro hosting by github]
* Porting apps on our company page ([http://store.ovi.com.cn/publisher/EB EB OVI Page]) to MeeGo

Zeeshan Ali

==== Batch Two ====

Second batch - to be integrated witrh the list above.

Max Waterman '''ID sent''', '''applied for Nokia Launchpad'''
* Porting ZouBa to MeeGo/H and QML, plust other app ideas.

Sławomir Musiał '''ID sent''', '''applied for Nokia Launchpad'''
* [http://www.swinkels.tvtom.pl/eCards eCards] Application for creating and sending e-cards

[https://meego.com/users/scifiguy Sudheer K.] '''ID sent''', '''applied for Nokia Launchpad'''
* Porting [https://garage.maemo.org/projects/marketstoday Markets Today], a Stock Quotes app to Harmattan
* Evaluate porting of VICaR (Call router application) and new application ideas on Harmattan

[http://wiki.meego.com/User:Mohannad Mohannad Hammadeh] '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Porting mPrayerTime to Meego-Harmattan, updating the UI and adding more features.
* Writing new application ''Spotter'' - exercise tracking app
[https://meego.com/users/antman8969 Anthony Naddeo] (antman8969 here on meego.com, but antman8069 on developer.nokia.com) '''id sent, applied for launch program'''
* [http://umcs.maine.edu/~naddeoa/profile/linkedup-project.html Linkedup] - LinkedIn client for Maemo, Meego, Harmattan..... anything Qt
* [http://umcs.maine.edu/~naddeoa/profile/qtweather-project.html QtWeather] - United States National Weather Service application
Leaf Johnson

[[User:epage|Ed Page]] '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Updating [http://wiki.maemo.org/DialCentral DialCentral], [http://wiki.maemo.org/Gonvert Gonvert], [http://wiki.maemo.org/Ejpi ejpi] for Meego/Harmattan
* Port all other appliations to Qt for Meego/Harmattan
* Continue writing new applications

William Su (sony123) '''ID sent, Applied for the Nokia Developer Launchpad program''' 
[http://talk.maemo.org/showthread.php?p=1019939#post1019939 Stockona] - a google finance client.
Currently working on:
* Local portfolio creation.
* Webview integration: Make in-app news feed reading possible.

Anthony Day '''ID sent''', '''applied for Nokia Launchpad'''
* Porting and extending [http://talk.maemo.org/showthread.php?t=72951 inner-spin] game
* Porting and extending [http://talk.maemo.org/showthread.php?t=73942 Take it away Marco] N900 drum machine
* writing new game and realtime music Apps content for the N9/950

[[User:mattaustin|Matt Austin]] '''ID sent, applied for launchpad, device ordered, waiting for arrival.''' 
Transperth trains live departure boards app, Player numbers AFL footy app, Amazon S3 bucket & file browser

[https://meego.com/users/smoku Tomasz Sterna] '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Port my touch screen [http://tomasz.sterna.tv/maemo/ ports of games for Maemo] (Widelands, Bos Wars, Robbo) and UAE4All, PSX4All emulators
* Port support for SIXAXIS(TM) Controller
* Possibly build and integrate [http://codex.xiaoka.com/wiki/cordia:start Cordia HD] on Harmattan

Olli Laasonen '''ID sent''', '''Accepted in Nokia Developer Launchpad program - waiting for confirmation email to be able to order the device''' 
* Porting apps from Maemo (Who is calling?, Advanced phone lock, Sanakirja.org dictionary client).
* Developing small handy applications.

Ville Syrjälä

Shane Bryan

Jure Repinc

[http://maemo.org/profile/view/rm_you/ Adam Harwell] '''ID sent''', '''Launchpad account active''' 
* Porting [http://maemo.org/downloads/product/OS2008/advanced-backlight/ Advanced Backlight] from Maemo, adding new features
* Helping with photo utility suite project (SnapGo, with GeneralAntilles and others)
* Will help beta test apps for people on IRC

Boris Pohler (emanymton) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
* porting Zeitkonto and HandsOff (not yet released) from Maemo to Meego, maybe a rewrite with QML
* other ideas in pipeline (remote for mythtv, live sports-ticker, ...)
* Helping other users at the german side meego.de (there known as Cermit)

Eike Hein

Jeffrey Malone (ieatlint) - '''ID sent, already a Nokia Launchpad member'''.
Will be creating a transit application around the public NextBus real-time vehicle tracking API for dozens of transit agencies in North America.
Hopefully collaborating with others working on transit applications... :)

thebootroo | Thomas Boutroue '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Making a small and smart mobile widgets toolkit on top of plain QWidget + CSS for styling, named MWTk.
And using this toolkit to make several apps for MeeGo (and runs onto Maemo5 and Symbian too, even on desktop OS) and a new environment, that aims to be a good alternative to default MeeGo Handset UX, bringing it on pair with Harmattan UX, by giving it a successor to the deprecated MeeGoTouchFramework.
Already some testable sources can be found on the project gitorious repos.
https://gitorious.org/meego-community-mobile-ux-ng
And there is a page with some screenshots of the look that MTWk can do (this page will be moved on gitorious wiki soon) :
http://modern-os.projects.servhome.org/mobileApps/

[[User:Theonehumble|Stephan Bulgin]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
- I will be porting NXEngine http://nxengine.sourceforge.net/ to MeeGo/Harmattan. My previews work for Maemo can be found here http://talk.maemo.org/showpost.php?p=971709&postcount=1
Description: A clone/engine-rewrite of the classic jump-and-run platformer Cave Story.
- Right now Im in the process of re-writing DonQt for MeeGo/Harmattan. Previews work for Maemo here http://www.forums.internettablettalk.com/showpost.php?p=976671&postcount=1 (will most likely be a name change and better code.)
Description: Don is a "SDK installer" for developers to compile on the go.
- More ports and some original stuff and looking forward to collaborations.

[[User:mdengler|Martin Dengler]] '''ID sent''', '''Accepted for the Nokia Developer Launchpad program''' '''Ordered: OID-052797''' 
I am working on porting a tron-like game (armegatron preferably or glTron) to the N9, and developing Ringr, a location-based ringtone management application.

[[User:Rafael2k|Rafael Diniz]] '''ID sent''', '''Launchpad for individuals account active ''' 
I plan to develop FM RDS applications with focus in the new standards from RadioDNS like the RadioVIS (partly based in the already existent the N900-fmvis http://code.google.com/p/n900-fmvis/).
I'm a member of a university radio station (Radio Muda FM, 88.5MHz) and my plan is to develop "real life" radio station applications. 
I'll also write one audio and one audio/video icecast2 clients. I can provide icecast2 server access for beta testers at radiolivre.org. I'll take ideas from softwares I already wrote for this purpose, like darknow (a gui for darkice, http://darksnow.radiolivre.org) and theorur, an audio/video icecast2 client (a gui for ffmpeg2theora, http://theorur.sarava.org), all using QT.

Anderson Briglia, '''ID sent, Applied for the Nokia Developer Launchpad program''' 
My idea is to re-write the Carman application for N9/N950, using QML.
There is also an effort to port the current carman daemon and carman
bluetooth communication since Bluez used in Meego is slightly
different from the implemented one. I also want to get rid of
libpurple and implement a more integrated way to communicate with
Google accounts.

[[User:Milhouse|Neil MacLeod]] '''ID sent, Applied for the Nokia Developer Launchpad program''' 
Develop an audio recording application with geo-location support, plus other applications to improve personal productivity utilising the Harmattan notification/event view.

Nilanjan Chakravorty - '''ID sent, Already applied for the Nokia Developer Launchpad program'''
* Leverage my financial background with IT to develop
- Portfolio management application - Bloomberg Pricing data application

[[User:timsamoff|Tim Samoff]]
* [http://thp.io/2011/mong/ Plonk]
* MeeGo Community Apps website design
* A few other things that are brewing (games, sound generators, etc.)

David Perlow '''ID sent, Applied for the Nokia Developer Launchpad program [UPDATE: 110706] Accepted into the Launchpad program [UPDATE: 110707] Ordered device and received order confirmation'''

Pawel Kurdybacha '''ID sent, already a Nokia Launchpad member'''
* Testing and contribution to Qt Mobility on Harmattan platform
* Multimedia Home controller based on gUPnP
* various applications (words trainer, taxi checker, ...)

[[User:Rzr|Philippe Coval (RzR)]] ''' ID sent , [https://www.developer.nokia.com/Profile/?u=www.rzr.online.fr Nokia Developer Launchpad ID ] Sent, waiting to be contacted
* tags: ( qt4, qml, opengl, debian, emulator, pinball, neheglqt, p-uae)
* more: http://rzr.online.fr/q/meego

Philipp Engelhard '''[https://www.developer.nokia.com/Profile/?u=-philipp Nokia Developer ID] sent''', '''Applied for the Nokia Developer Launchpad program''' 
* Develop a maze game for children and adults
* Develop a "Nokia Bots" like program for alarm and battery

[[User:Rnazarov|Ruslan Nazarov]] '''ID sent''', '''waiting answer from Nokia Developer Launchpad program''' 
Porting [https://gitorious.org/titanim TitanIM] (Vkontakte instant messenger)

Moritz Mühlenhoff

[[User:milliams|Matt Williams]] (milliams) '''ID sent. Accepted onto Launchpad. Device ordered.''' 
Creation of a Particle Physics information database (from [http://pdg.lbl.gov/ PDG]) application. Porting of [http://games.kde.org/game.php?game=ksquares KSquares] to pure Qt for MeeGo and creation of other similar simple games. Porting of [http://thermite3d.org PolyVox] to MeeGo and port games built on it when they are ready. Port the [http://falconpl.org Falcon] programming language to MeeGo.

[[User:Asys3|Uwe Koch]] '''ID sent, Applied for the Nokia Developer Launchpad program''' 
* Port hopefully all of my games Lineo,Q,TwinDistress,Sokoban and Jooleem

Frank Banul '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Port TabletBridge and RadioTimeToGo

Felipe Erias Morandeira '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Design user interfaces using QML and collaborate with the MeeGoTouch project.

[[User:kojacker|Ryan Faulkner]] '''ID sent, Already a Lunchpad member''' 
* Various applications, bits and bobs (links coming)

[[User:hopbeat|Arkadiusz Stopczynski]] '''ID sent, Accepted for the Nokia Developer Launchpad program'''
* Various academic projects, including novel user interfaces, social web, BCI and portable cognitive sensors. All the crazy stuff mentioned here: http://www.milab.imm.dtu.dk
* Some utility applications that make your everyday tasks easier, such as shortcutd or lockdaemon for Maemo

[[User:feri|Ferenc Székely]] (ferenc)
* Working on [http://apps-beta.meego.com MeeGo Apps], an "app store" for open source, free apps for MeeGo
* Will help packaging and porting Maemo -mainly location based- apps to MeeGo

[[User:w00t|Robin Burchell]] (w00t) '''ID sent''', '''Already a Launchpad member (but my Launchpad account hasn't activated)''' 
meego.com hackery, meego-ux in particular. Qt Components. Anything else I find interesting - see [[User:w00t/N950Development]] for plans, as I think of anything interesting to write.

Mohammad Abu-Garbeyyeh '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Planning a wiki page with a todo list, main project here: http://bt-messenger.com

[[User:sebas|Sebastian Kügler]] (sebas) '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Bringing Plasma Active ( http://community.kde.org/Plasma/Active )to MeeGo

Juha Ristolainen '''ID sent, already a Launchpad member''' 
Heiaheia fitness-service application for MeeGo. Untappd.com client for MeeGo.

Ilya Skriblovsky '''[https://www.developer.nokia.com/Profile/?u=IlyaSkriblovsky Nokia Developer ID] sent, applied for Nokia Developer Launchpad, Order placed''' 
* Port NWTBible (Bible reader), Planaris (Hierarchical Todo list) to MeeGo

Rich Jones

[[User:Bemasc/N950_Project|Benjamin Schwartz]] '''ID sent, applied for Nokia Launchpad ''' 
I will attempt to convert [http://sugarlabs.org Sugar] [http://activities.sugarlabs.org Activities] into MeeGo apps, and hopefully in the process acquire some insight into the potential for MeeGo to form the basis of future Sugar revisions

[[User:Nicolai|Nicolai Hess]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Got the Mail:"A Nokia N950 is waiting for you" 
Port my [http://maemo.org/packages/view/scout scout] application to Qt (Application to search contacts, calendar and conversations)

Hussain Shafiu '''ID sent''', '''LaunchPad account activated.''' 

Shan Yafeng '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
An education program for exchange information between students and teacher in class. And port some programs to the nokia N900/N950 device. The progress can be found here : http://cuckoohello.wordpress.com

[[User:vitna|Vaselli Vittorio]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program. Device ordered in date: 07/07/2011''' My actual project is http://forum.meego.com/showthread.php?t=3652, but i have in program to develop much more game for the Harmanattan platform

==== Batch Three ====

Reggie Suplido '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Custom MeeGo web development related to meego.com and forum.meego.com.

Koos Vriezen 
Will port the popular [http://maemo.org/downloads/product/Maemo5/kmplayer/ kmplayer] application from maemo5

Micke Prag '''ID sent''', '''Launchpad:Accepted''' | '''N950eMail:Yes''' | ''' Ordered:Yes ''' | '''Received:No''' 
[https://gitorious.org/telldus/tellduscenter-light TelldusCenter Light] - Using the mobile phone as the central hub in your home automation. Control your lights, electrical appliances and curtains wirelessly from the palm of your hands.

Aigars Mahinovs

Miika Johannes Ahdesmaki '''Nokia Developer Launchpad program approved 06Jul2011, Device available for order 07Jul2011 (ordered)''' 
[http://forum.meego.com/showthread.php?t=3633] Development of multi sensor utilising apps. First working example app in gaming.

Andreas Schildbach (Goonie) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting of [http://code.google.com/p/public-transport-enabler/ Public-Transport-Enabler] and [https://market.android.com/details?id=de.schildbach.oeffi Öffi] to Meego.

Ilya Paramonov '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Development of collaborative mind mapping application [http://yar.fruct.org/projects/hivemind HiveMind] for mobile and desktop platforms and sophisticated GTD-style personal time management application [http://yar.fruct.org/projects/octotask Octotask].

Thomas B. Ruecker '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
MeeGo Community edition for N9(|50|00) 
APRS application in QML to teach myself something about QML and Qt Mobility.

Damion Yates

Antti Raina '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''

Glen Gray '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''

Johan Paul '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
* Google Contacts importing (if you are an Android user, then setting up your contacts with be really easy)
* N9 Podcast client
* Instapaper client.

Simon La Rose (hawaii/SimonLR) '''ID sent. Applied for Launchpad. Ordered device. OID-052842'''
* Networking tools
* FOSS tool ports
* Port existing Fremantle/Maemo 5 packages missing active maintainers.
* Platform evangelism

Daniele Maio '''Device Ordered, Waiting for Arrival''' 
Porting maemo5 apps to meego.

Nathan Willis

Peter Hunt (tigerite) '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Integrating the BFS CPU scheduler https://garage.maemo.org/projects/kernel-bfs/ into the N9/50 kernel, along with the Budget Fair Queueing I/O scheduler http://algo.ing.unimo.it/people/paolo/disk_sched/
* Porting projects such as the Phoronix Test Suite http://www.phoronix-test-suite.com/ to Harmattan
* Converting a Flash cards based learning system which I developed, loosely based on the one found at http://www.educationlabs.com/projects/flashcards/Pages/default.aspx, from C#/XAML to Qt/QML and making it standalone

Philford Barrett (sevla) '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Swipe Style/Swypr/SwipeMe - Allows the user to assign swiping from the outside of the screen to specific actions i.e. swiping from the top jumps to the multi-tasking view while swiping from the bottom jumps to the Feeds View. Each side of the screen (Top/Left/Bottom/Right) can have a max of 4 zones. Each zone can be assigned to an action thereby giving the user the ability to configure 16 "invisible" shortcuts. Each of which will be available at all times, regardless of what the user is doing in the current app/view.
* Drop Box Integration - Integrate downloading/uploading data to and from an existing Drop Box account. Wherever possible, existing apps will be modified to show this data. i.e. photos in the users drop box account can be (meaning this will be configurable) displayed from the n9 picture viewer.
* Audio Galaxy Integration - Enable streaming of your audio galaxy library to your device through the n9 media player.
* Feeds++ - Feeds++, an enhanced feeds view, extends the functionality of the feeds view by allowing multiple views and enabling the ability to assign specific data to each view. i.e. Show Facebook only data in View A and Twitter only data in View B. Feeds++ will also allow the user to reply directly to events without having to opening the corresponding app.
[[user:jukey|Uwe Kaminski]] ('''Nokia Developer ID sent''')

Kyösti Ranto

Alex Tyler - '''Developer ID sent. Applied for Launchpad. Have ordered device. OID-052742''' - I plan to port my Subsonic client [http://maemo.org/packages/view/aerofy/ Aerofy] to the platform. I also plan to develop a range of media related applications.

Stuart Howarth (marxian) - '''ID sent. Accepted for Nokia Launchpad program 06/07/11. Device ordered 07/07/11 - OID-052785'''
* Porting my [https://garage.maemo.org/projects/qmltube cuteTube] application (QML version).
* MythTV controller/recording scheduler (similar to the Android XBMC application)

[[User:hardaker|Wes Hardaker]] '''ID sent, Launchpad application submitted'''
I'm continually developing applications for multitudes of devices, including many Qt applications at [http://www.dnssec-tools.org/ dnssec-tools] as well as personal projects, my favorite being my [http://www.hamtools.org/cutecw/ Morse Code Training Software], which is what I want to port immediately. See my [[User:hardaker|User Page]] for a more complete list.

Christoph Keller (gri) - '''ID sent, Order placed'''
Porting [http://web2sms.garage.maemo.org Web2SMS], splitting it up into a telepathy plugin, service daemon, contacts integration and hopefully sms application integration plus new provider plugins.

Luke Bratch

David Sansome - '''ID sent, Launchpad application submitted'''
Porting [http://www.clementine-player.org Clementine music player] to MeeGo. Clementine already uses Qt and GStreamer.

Jason Byrne (slvr32) - '''ID sent, Launchpad application submitted''' - [https://garage.maemo.org/projects/nfqm nfqm] (Netflix Queue Manager) Qt/C++, targeting Symbian^3, Maemo 5, and Meego/Harmattan - discussion thread [http://forum.meego.com/showthread.php?t=3715 here]

Hillel Lubman (shmerl) - '''ID sent, Launchpad application submitted''' 
Testing Firefox/Fennec on Meego, porting [http://code.google.com/p/kosherjava/ Zmanim API] to C++ and preparing it for Meego as a library. Planned - calendar application in Qt based on the Zmanim API.

[[User:kkv|Kirill Krinkin]] '''ID sent, already a Nokia Launchpad member'''. 
I'm working on clients for open [https://github.com/OSLL/geo2tag Location Base Platform ]. Project tracker and progress can be found [[http://osll.spb.ru/projects/geo2tag/issues here]].

Si Howard

Klaus Rotter (klausr) -'''ID sent, Applied for Nokia Launchpad program''' 
Projects are porting/rewriting EasyPlayer (audiobook player) and some kind of a HAM (amateur radio) app (PSK31) for MeeGo. I'm also interested in low latency audio apps (drum-studio, recording), if this is possible with the N950/N9.

Piotr Pokora (piotras)
I am core developer of Midgard Content Repository which (as library) is used by different Maemo apps: Conboy, MaeCalories, Tablet of Adventure, Qaikuclient. Also I am maintainer of libgda and midgard packages (debs and rpms).
From date of birth, I am interested in unified and simplified data access. And such, I am also going to develop for N950.

[[User:ivan4th|Ivan Shvedunov]] '''ID sent''', '''accepted into Launchpad (06-Jul-2011–06-Jul-2012), ordered the device, not delivered yet''' 
I'm working on [http://github.com/ivan4th/i4checklist Shopping list/checklist] application inspired by
HandyShopper for PalmOS (already working: All/Need separation; plan to implement other features soon, too).
Also [http://talk.maemo.org/showthread.php?t=42339 ported CLISP] to Maemo Fremantle and helped to debug
several ARM-related bugs in Clozure Common Lisp, managed to make [http://common-lisp.net/project/commonqt/ CommonQt]
(Common Lisp Qt bindings) work on Maemo Fremantle + CCL + Qt 4.7. I plan to continue my Common Lisp work on Meego, too.

[[User:Agomez|Andres Gomez]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
I plan to develop drondas, a personal application for the management of the payments shared with other people so you can get track of who paid which in name of whom.

William Stephenson (wstephenson) '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''
I'm working on a high level toolkit for the creation of branded RSS based apps, in order to facilitate the creation of these simple apps.

Jason Flatt (jflatt) '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''

[[User:Lizardo|Anderson Lizardo Gomes]] '''ID sent, Applied for the Nokia Developer Launchpad program (done). Launchpad for individuals (06-Jul-2011–06-Jul-2012), waiting for device order availability on DDP'''. 
I currently work on [http://www.bluez.org/ BlueZ] (Bluetooth stack for Linux) helping implement support for the new Bluetooth Low Energy (LE) technology. We currently lack user applications that take advantage of the [https://www.bluetooth.org/Technical/Specifications/adopted.htm recently adopted] GATT profiles, such as Proximity & FindMe. With these profiles, we will be able, for example, to alert if the phone has been left behind (assuming you own a LE keyfob with you) or locate your keys (if they have a LE keyfob/tag). 
I intend to work on QML applications that will enable to use this technology. NOTE: N950 Bluetooth chipset lacks LE support, but N9 will be Bluetooth 4.0 based (according to specs). For testing and development purposes, the applications will use the traditional Bluetooth 2.1 technology.

pancake

[[User:pancake|pancake]] '''
I'm the author of radare2, a reverse engineering framework for disassembling, debugging, hexediting binaries and doing some forensics-related tasks. I already wrote a GTK frontend for Maemo (n770,n810,n900) and my plan is to write a QT/QML ui for it.
I will also port other programs of mine like tokipona language learning tools, simple games (but addictive!) to QT (from commandline).
In the future I would like to work on Vala and Gtk3/gtkaml (multitouch) support for MeeGo based devices.

Rodrigo Vivi

[[User:niqt|Nicola De Filippo]] '''Sent my Account ID to Quim, i'm already Nokia launchpad member.'''. 
I'm porting my maemo5 applications [http://badge.garage.maemo.org Badge] and [http://qlshop.garage.maemo.org QLshop]. I'll develop a new qml game and other mail client.

[[User:lamikr|Mika Laitio]]
* kernel
* MeeGo CE edition
* VDR linux tv client

* kernel
* Meego CE edition

[[User:Blackwicked|Edvin Rab]], '''Developer ID sent''', '''Applied for Launchpad''', '''Device Ordered''', '''Waiting for Arrival'''. 
Porting [http://t.co/4Os8iIh EvidenceHunt Game] to MeeGo. Also have plans to work on augmented reality projects.

==== Batch Four ====

[[User:mikelima|Luciano Montanaro]] - '''Device Ordered, Waiting for Arrival.''' 
Porting [http://quandoparte.garage.maemo.org Quando Parte], implementing a QML patience/puzzle game, porting and adapting KGoldrunner, and writing an OpenStreetMap survey tool, all for use with MeeGo Harmattan (and future MeeGo versions).

Sebastian Pawluś - '''ID sent, Applied for the Nokia Developer Launchpad program''' 
LocIt is a location aware system, able to put on screen information about objects near device. Right now works with: Youtube, Wikipedia, Panoramio layers. 
Plans are: port it from Maemo to MeeGo device, and move from client server architecture to single client architecture. 
More: [https://github.com/xando/thesis/tree/master/locit-client source], [https://github.com/xando/thesis/blob/master/thesis/Obrazki/UiFlowDiagram.pdf?raw=true screenshots]

Lucien XU (Sfiet Konstantin) - '''Ordered the device (07/07/2011) waiting for arrival''' 
Develop a centralized public transportation system : [[TransportApp|libpublictransportation]] 
And also a game [http://sfietkonstantin.free.fr/blog/?p=11 Blog post about the game] (No gitorious yet, will come)

Robert Marki - '''Device Ordered, Waiting for Arrival.''' 
Developing an application called [https://projects.developer.nokia.com/feed_reader FeedReader], it's a universal feed reader with support for podcasts. More info on the project's website. 
Would like to develop image processing related applications like: 
Image translation application 
Image gallery with face recognition 
Porting control software of a hexapod robot, or at least the module which helps the robot orient itself and navigate based on the images acquired from the camera 

Antoine Reversat - '''Device ordererd, waiting for arrival.''' 
A bixi (Montreal public bike system) app : [http://forum.meego.com/showthread.php?t=3650 App thread] (hopefully will extend it to other bike systems)
Some Meego CE hacking

Roman Deninberg([http://maemo.team16.ru/ Bonapart]) - '''ID sent, Waiting for response from the Nokia Developer Launchpad program''' 
Psx4m\PCSX-rearmed\Psx4m-gui projects basically

[[user:ossipena| Timo Pelkonen]] - '''ID sent, Applied for the Nokia Developer Launchpad program''' 
Application to measure distances and collect stats about the distances 

[http://twitter.com/#!/gregjroberts Greg Roberts] - '''Developer ID sent | Launchpad:Accepted(06-Jul-2011) | N950eMail:07 July, 12pmGMT| Ordered:07 July 12pmGMT | Received:No''' 
Developing/Porting [http://maemo.org/downloads/product/Maemo5/healthcheck/ Healthcheck] with many new fun things (Qt) 
Will Port and update [http://talk.maemo.org/showthread.php?t=65522&highlight=maecount MaeCount] (Qt) 
Would like to develop a new game (Some ideas, and basic code for a few - so will update shortly) 

Christos Zamantzas ([http://wiki.meego.com/User:Saturn Saturn]) - '''ID sent, Applied for the Nokia Developer Launchpad program'''

Quang Pham ([http://wiki.meego.com/User:Quang Pham]) - '''ID sent, Applied for the Nokia Developer Launchpad program'''

==== Batch Five ====

Sivan Greenberg--> Nokia Developer Champion ID: sivang , Applied for individual Nokia Developer Launchpad Membership. Working on [[http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/pdf/CrowdQuick CrowdQuick]] and some platform stuff, as evident by the talks I had given in 2010/2011 MeeGo conferences.

Tapio Pyrhönen '''ID sent''', '''applied for Nokia Launchpad''', '''waiting for reply''' 
Porting my old Nintendo DS apps/games and making new ones too.
[http://tapsa.bitmagick.com/nds My Site]

Arto Jalkanen ([http://wiki.meego.com/User:Ajalkane Dynamic Profile Switcher]) '''- ID sent, Applied for the Nokia Developer Launchpad program'''

Jukka Nousiainen '''- ID sent, Applied for the Nokia Developer Launchpad program''', Creating a tethering application for DSLR cameras, and porting needed libraries, e.g. libgphoto2

Michael Schloh von Bennewitz (MSvB) '''- ID sent, Applied for the Nokia Developer Launchpad program''', Using the device for a MeeGo lecture series in the fall, giving demos. Application development includes LDAP client, and a chess clock. I've ported a number of network and security packages as well, will begin to get them over to the MeeGo repos.

[http://wiki.meego.com/User:Kdrozd Krzysiek Drozd] ''' - Device Ordered - 6.7.2011 13:45: Last Status: Device Sent to Customer 6.7.2011 13:45'''

Svetozar Belic ([[User:trx|trx]]) '''- Got "A Nokia N950 is waiting for you", Device ordered (2011-07-07) ''', Port TxPad, TxMySQL Explorer, libQt4Pas library, etc.. Will create a list of apps to port/create.

Philipp Andreas '''- ID sent, Applied for the Nokia Developer Launchpad program''', Porting [https://garage.maemo.org/project fahrplan] for the N9

Quality/Bugtriage

2011-06-30T09:39:57Z

Andre: /* Bug Triage Definition */

== Bug Triage Definition ==
* Bug Triage is a process to:
** Ensure bug report completeness
** Analyze and assign bug to proper component
** Assign bug to proper bug owner
** Assign bug to packages listed in "MeeGo Distribution Packages" product whenever possible (apply for new incoming bug reports for version 1.3 ONLY at this moment)
** Set appropriate bug priority
** Adjust bug severity properly (initially set by bug reporter)
** Resolve obvious invalid, duplication, won’t fix bugs etc.
** Forward bugs in upstream components to [[Quality/UpstreamBugTrackers | upstream bugtrackers]] and adding the upstream URL to the URL field of the report, if applicable

* Bug Triage Team
** A small team works on bug triage, could be experienced developer, distro engineer or QA
** Triage team members are expected to contribute significant time to bug triage

Please share your triaging knowledge by adding/editing [[Quality/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]].

== Bug Triage Process ==
* Triage new incoming bug reports timely by each triage team (from twice a week to daily triage).
* Triage team members in each triage team could have different focus, such as IA arch bugs, ARM bugs or specific applications etc.
* Each triage team meet on IRC weekly to discuss controversial bug reports and any open reports
* Bug assignees accept bug reports by setting target milestones for triaged bug reports
* [http://meego.com/about/governance/program-office Program Managers] host bug report scrub meetings to discuss bug reports which do not have a target milestone set

Triage Process Flow as follows:
[[File:Bug-triage.PNG]]

== MeeGo Bug Triage Guide ==
Check the [[Quality/Bugtriage_Guide|Triage Guide]] that explains good practices when triaging bug reports.

== MeeGo Bug Triage Team ==
{|cellspacing="0" border="1"
!|MeeGo Bug Triage Team
!|Member
|-
| MeeGo Core OS Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ares2012 Jason Zhou], [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Handset UX Triage || Fan Zhao, Cathy Li, [http://meego.com/users/srikanthyarlagadda Srikanth Yarlagadda],[http://meego.com/users/jylha Petri Jylha], [http://meego.com/users/ceferron Chris Ferron], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Netbook UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo Tablet UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang]
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
|-
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster], [http://meego.com/users/pmccarty Patrick McCarty]
|-
| MeeGo SDK Triage || [http://meego.com/users/ionutgavaz Ionut Gavaz], Jackie Wu, [http://meego.com/users/edmondas Edmondas Girkantas], Azadeh Karimian, Max Yu, Juha Peisanen
|-
| MCTS (MeeGo Core System Testing) Triage || [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen], Jeff Zheng
|}

=== MeeGo Bug Triage Meetings ===

* MeeGo Core Bug Triage
** Time: Every Monday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Handset Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Netbook Bug Triage
** Time: Every Tuesday at 13:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo IVI Bug Triage
** Time: TBD
* MeeGo Translation Bug Triage
** Time: TBD
* MeeGo SDK Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MCTS Bug Triage
** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC]

Those meetings take place in the IRC channel'''#meego-meeting''' on [http://freenode.net irc.freenode.net].

* MeeGo Tablet Bug Triage
** Time: Every Thursday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
** IRC channel '''#meego-meeting2''' on [http://freenode.net irc.freenode.net]

To discuss MeeGo bug triaging at any time feel free to visit the IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net].

* [[CoreBugTriageMinutesArchive|MeeGo Core Bug Triage Meeting Minutes Archive]]
* [[HandsetBugTriageMinutesArchive|MeeGo Handset Bug Triage Meeting Minutes Archive]]
* [[NetbookBugTriageMinutesArchive|MeeGo Netbook Bug Triage Meeting Minutes Archive]]
* [[SDKBugTriageMinutesArchive|MeeGo SDK Bug Triage Meeting Minutes Archive]]

=== Getting involved ===

Anyone can sign up for the triage team and start helping (see the [[Quality/Bugtriage_Guide|Triage Guide]] for information and steps). Just send an email to the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list] to get involved in. Thanks for your contribution to MeeGo!

== Other references ==
[[Quality/How_To_Report_Bugs|How to report MeeGo bugs?]]

[[Category:QA]]

Quality/Error Management

2011-06-29T12:47:55Z

Andre: /* Other Documentation */

MeeGo Error Management (EM) defines the handling of errors in MeeGo and maintains [https://bugs.meego.com MeeGo Bugzilla]. Error Management is part of [[Quality|QA]].

== Team ==

* '''[http://meego.com/users/ericlr Eric Le Roux]''', Nokia Error Management Lead
* '''[http://meego.com/users/wanshuang Shuang Wan]''', Intel
* '''[http://meego.com/users/iekku Iekku Huttunen]''', Ixonos
* '''[http://meego.com/users/andre Andre Klapper]''', Openismus

== Communication ==

Same as for [[Quality#Contact|Quality]] in general:
* Mailing List: [http://lists.meego.com/listinfo/meego-qa MeeGo-QA]
* IRC: Channel #meego-qa on irc.freenode.net

== Getting Involved ==

To be defined, but basically: Participate in [[Quality/Bugtriage|bug triaging]], help contribute to the [[Quality#Procedures_and_best_practices|process descriptions]], help out in [https://bugs.meego.com bugs.meego.com], show your abilities, earn reputation.

== Tools ==

== Process ==

* [[Quality/Meetings|Meetings]]
* Issues can be filed via bug reports in MeeGo Bugzilla against [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com MeeGo Bugzilla] itself or against [https://bugs.meego.com/enter_bug.cgi?product=Community%20processes Community processes].
* The current EM process is documented here: [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Handling]]

== Other Documentation ==

* [[MeeGoBugzilla_Customization|MeeGo Bugzilla Customization]]
* See [[Quality]] section for further Bugzilla process related information
* [https://gitorious.org/meego-bugzilla Codebase repository] (move not finished yet)

[[Category:QA]]

User:Andre/Bug Summary Prefixes

2011-06-28T20:28:45Z

Andre: add "PnP"

= Bug summary prefixes in bugs.meego.com =

{|
| style="background: #ffcc00; color: black" | '''Note:''' First and rough list. Does not mean that the current practice necessarily makes sense, just trying to document it. -- [[User:Andre]] 2011-05-17
|}

== List ==

Feel free to edit, but please keep the alphabetical order.

{| border="1" + Items
! Prefix
! Description
|-
| [CONX]
|
|-
| [CD] and [DE]
| Bug is reproducible only with [http://wiki.meego.com/ARM/N900/DeveloperEdition N900 Development Edition] / Community Edition image
|-
| [FEA]
| Feature request
|-
| GLS -
| outdated, stands for "Global Language Solutions". Replaced by [L10N] and [I18N]
|-
| [Installer]
|
|-
| [I18N]
| For issues in the codebase (not in translations themselves) that are related to using other languages
|-
| [IVI]
|
|-
| [L10N]
| For issues in translations (not in the codebase itself)
|-
| [MCTS-]
| For bug related to MCTS
|-
| [Meta] / [META] / [METABUG]
| For collecting bug reports from same area together (e.g. power management issues) by using 'Depends on'.
|-
| [MTF]
|
|-
| [MWTS-]
| For bug related to MWTS
|-
| [PnP]
| Power and Performance (according to bug 18851 comment 5)
|-
| [REG]
| Regression
|-
| [Trunk:Daily] / [trunk: daily] / [Trunk : Daily]
|
|-
| [Trunk:Testing]
|
|}

[[Category:QA]]

Quality/Bugtriage Guide

2011-06-27T17:53:16Z

Andre: Specific areas: Add TODO

{|
| style="background: #ffcc00; color: black" | '''Note:''' This is a first and very rough draft. If you can add information please go ahead. -- [[User:Andre]]
|}

This article is for anyone who wants to help triaging the incoming and existing bug reports in MeeGo Bugzilla. This article is not for bug reporters, but those people taking a look at the reports after they have been submitted.

Following the techniques listed and explained here will help important bugs get fixed, as well as optimize precious developer time.

Also see [[Quality/How To Report Bugs|How To Report Bugs]].

== How can I help? ==

# Create an account. The [http://bugs.meego.com bugs.meego.com] authentication system is integrated with the [http://meego.com meego.com] authentication system, so the same account is used for both sites. To create a MeeGo account visit the [http://meego.com/user/register registration page]. Soon after you will receive an email with a link that must be visited to confirm your account creation. You will have to change your password on meego.com before attempting to log into Bugzilla.

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Introduce [http://wiki.maemo.org/Bugs:Stock_answers Stock answers] if wanted and agreed on -- [[User:Andre]]
|}

# Read the [Stock_answers Stock answers]. These stock responses are general examples of the kinds of comments that triagers should add to bug reports. There are even a surprising number of bug reports for which you can simply use these responses. Please always add a comment when changing the bug status to RESOLVED or NEEDINFO, so the user can comprehend your decision.
# Find what should be changed. Read the Steps of Triaging below to determine what should be changed (if anything) and how.
# Add yourself to the CC list of the reports you triage so you will receive updates and notifications on changes.
# Ask someone to verify your changes. In #meego-bugs on irc.freenode.net mention the bug number you are looking at and the changes that you think should be made. (If no one is around, it is perfectly okay to leave a comment in the relevant bug with information that could be useful to others, e.g. "I think this bug report is a duplicate of bug 1234").

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' editbugs permissions: Does this make any sense in the bugs.meego.com setup? -- [[User:Andre]]
|}
As time goes by and you become more familiar with Bugzilla, please ask the [[Quality/Bugtriage#MeeGo_Bug_Triage_Team|Bugsquad members]] to provide [http://www.bugzilla.org/docs/3.6/en/html/useradmin.html#modifyusers editbugs permissions] to you so you have gain much more power to change things and work efficiently in the bug database.

=== Potential tasks ===

Please take a look at [[Quality/Bugtriage_Tasks|some ideas here]].

== Steps of Triaging ==

This guide should make triaging a bug as easy and simple as possible. Remember, if in doubt, ask! Also, remember that you may not be able to find anything to change for some bugs since not all bugs are filed incorrectly or incompletely.

=== Is it part of MeeGo Bugzilla? ===

Some pieces of software that users think of as part of MeeGo might be 3rd party software and have their bug tracking systems elsewhere. If the bug relates to one of these components, please close the bug as INVALID and ask the reporter to report it to the corresponding tracking system.

==== Hardware problems and Hardware enhancement requests ====

MeeGo is a software platform, hence bug reports about hardware bugs are invalid in bugs.meego.com. Please ask the reporter to either contact the hardware manufactorer (in case of Nokia this would be www.nokia.com) or to contact the company who sold the product to them.
In case of enhancement ideas for Nokia hardware there is http://conversations.nokia.com/design-by-community/.

==== Is it a valid, but wide and non-specific feature request? ====

Some reporters have great ideas and visions. They want to improve the User Experience in general or change behaviour of several applications at once.
These ideas are very hard to handle in Bugzilla as they require extensive brainstorming, discussing and involvement of several people/teams. Such reports are better to be discussed on one of the [http://meego.com/community/mailing-lists MeeGo mailing list] first .

=== Does it make sense? ===

Does it have enough information? Common sense rules here - "this sucks" or "this crashed" should be moved to NEEDINFO state with a polite message, as should other things that are too ambiguous to be useful.
In many cases asking for a URL or attachment will help. If you need help making changes to bug fields, just comment describing what changes you want made, or ask for help from the #meego-bugs channel on Freenode IRC, or send an email to meego-qa@lists.meego.com.

=== Is the bug a duplicate? ===

Some bugs in Bugzilla have been reported before. Finding them is more of an art than a science :-) This is an important step, but don't spend too long over it; if a bug is filed twice, someone else will mark the duplicate later. Be creative, e.g. searching for "delet" will bring up all bugs that have "delete" or "deleting" in the report, and "remov" is another popular string with a similar meaning to "delet" that other people could have used to already report the same problem.
If the bug is a duplicate, mark it as a duplicate in the resolution box at the bottom of bugzilla and add a polite comment explaining that this bug/request has been filed before. You don't need to carry on triaging it if it's a duplicate; press the "Commit" button and go onto your next bug!

=== Can you reproduce it? ===

If you can, please try to reproduce the problem. If you think the problem is not reproducable, write a comment indicating the exact software version you tested, the hardware that you used, the steps you took, the results you got, and why you think the bug WORKSFORME.

=== Is the version set correctly? ===

In general we always ask people to run the latest available software release, because nobody works on fixing ancient and obsolete releases anymore.

Image build date is available at /etc/meego-release, and you could refer [[Release_Engineering/Release_Versioning]]

=== Is it in the right place? ===

If you think the bug was filed against the wrong product, look for a better alternative in the drop-down list box (general information about the MeeGo architecture can be found [http://meego.com/developers/meego-architecture here]).

If the bug is about code which is buggy in its upstream form, please use the [[Quality/UpstreamBugTrackers|list of upstream bug trackers]] to find the correct bug tracker and then find/report it there. Once you have an upstream bug url, please add it to the bug by filling in <See Also>. If you can't add it to see also, add a comment to the bug.

=== What severity/priority should be set? ===
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' [https://bugs.meego.com/show_bug.cgi?id=12254 Document restrictions and permissions] -- [[User:Andre]]
|}
==== Severity ====
Severity field describes the impact of a bug and is open to all bugzilla users. Bug triage team will adjust the severity if the original one set by bug reporter is not proper. Roughly, MeeGo bugzilla provides 5 levels of severities:
* ''critical'' --- Crashes, loss of data, negative impact to other components, etc
* ''major'' --- Major loss of functionality
* ''normal'' --- Regular issue, some loss of functionality under certain circumstance
* ''minor'' --- Minor loss of functionality, or issues with easy workaround available
* ''enhancement'' --- Request for enhancement

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' [https://bugs.meego.com/show_bug.cgi?id=12252 Please explain ''enhancement'' severity vs ''MeeGo Features'' classification] -- [[User:Andre]]
|}

==== Priority ====
Priority field describes the importance and order in which a bug should be fixed. The priority field is restricted to '''group_of_some_people''' so it cannot be set by reporters or changed by average users. Triage team has the privilege to assign a proper priority based on bug severity and user imapct described by bug reporter. Roughly, MeeGo Bugs are with 3 levels of priorities:
* ''High'' --- SHOW STOPPER, must fix shortly in upcoming milestone and definitely for final product
* ''Medium'' --- fix before product release, however for upcoming milestones, we can document the issue with possible work-around for visible defects
* ''Low'' --- Lowest priority, harder to reproduce or are component specific in a different non-MeeGo environment.

Field Priority may keep "Undecided" for the first triage if triage team does not get enough information to assign a proper value. For example, lack of reproduce steps, image date for issue verification, user impact, etc. In this scenario, triage team will set bug status to "NEEDINFO" and add comments about what kind of information is needed for triaging. The Priority of the very bug is kept "Undecided" until information is feed and bug re-triaged.

* '''Crasher bugs'''
Should have Severity=Critical.
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Introduce [http://wiki.maemo.org/Bugs:Stock_answers Stock answers] if wanted and agreed on -- [[User:Andre]]
|}
Set the status to NEEDINFO if they don't have a stack trace, and ask the reporter to get a decent stack trace (see Stock_answers for more information). If there is no information about how it is triggered you should ask the original reporter how to reproduce the bug.
* '''Something not working as expected'''
Severity=Low or Medium depending on how much it breaks the application.
* '''Incorrect strings, typos, etc.'''
Severity=Low, Priority=Normal or High depending on how user-visible it is.
* '''Feature requests'''
If it really is a new feature, and not an improvement to something already in the product, set Severity=Enhancement.
If you're unsure about your Severity triage, add a comment in the bug explaining why you triaged it as you did. You can also add yourself to the CC field, so if someone retriages it differently you can find out why.

=== Is the assignee and QA contact correctly? ===
MeeGo bugzilla provides a default assignee and QA contact for each new filed bug. However, due to the complexity of each component and different supported platforms, the default one may not always be the proper one. Triage team also checks whether these two field are filled with proper person, to ensure that bugs will be owned and followed smoothly in their life cycle. However, if the issue is a system level one, probably cross components, then it is difficult for triage team to assign a proper owner. In this scenario, simply add keyword "need-sysdebug" and then it will be performed in-depth triage during SysDebug. See more details about SysDebug at http://wiki.meego.com/Quality/SysDebug.

=== Does it have the correct keywords? ===

Get familiar with the [https://bugs.meego.com/describekeywords.cgi existing keywords] and add those that apply to the report.

==== Is the described problem obviously easy to fix? ====

For reported issues that are obviously easy to fix, please add the "EasyFix" [https://bugs.meego.com/describekeywords.cgi keyword] which marks bugs that can easily be fixed by MeeGo community members and contributors. This is especially meant for beginners as an entry point to start contributing to MeeGo.

=== Has it been in NEEDINFO state for more than four weeks? ===
As [https://bugs.meego.com/show_bug.cgi?id=12257 decided] by the QA team, [https://bugs.meego.com/buglist.cgi?bug_status=NEEDINFO&chfieldfrom=-29d&chfieldto=Now reports that are in NEEDINFO state and have not been changed for four weeks] can be closed. This means that more information had been requested from the reporter but has not been provided. These reports should be closed as WORKSFORME if you are not able to reproduce, or as INVALID if there is simply not enough information to be a useful report. Please always explain your decision by adding a friendly comment and in the latter case, ask the reporter to provide the information asked for, if s/he can, and reopen the bug.

Example comment: "Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as WORKSFORME/INVALID. Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this in a recent version."

== Specific areas ==

=== Is the bug a release/update blocker? ===
When approaching the upcoming MeeGo release or update release, MeeGo bug fixing will be controlled through Flags like "MeeGo_1.0_Update_Release_Blocker", "MeeGo_1.1_Release_Blocker", etc. During these period, triage team will also propose potential blocker issues for Management team to judge. This is to push show stopper issues be fixed timely before formal release.

{|
| style="background: #ffcc00; color: black" | '''TO DO: Unclear / intransparent process how and who ("Management team") decides. See these postings: [http://lists.meego.com/pipermail/meego-releases/2011-June/001431.html 1] [http://lists.meego.com/pipermail/meego-releases/2011-June/001543.html 2] --[[User:Andre|Andre]] 17:53, 27 June 2011 (UTC)'''
|}

== Acknowledgment ==

Kudos to [http://browser.garage.maemo.org/news/8/ timeless], the [http://wiki.mozilla.org/MozillaQualityAssurance:Triage Mozilla Triage Team] and the [http://live.gnome.org/Bugsquad/TriageGuide GNOME Bugsquad]. This guide is based on the [http://wiki.maemo.org/Bugs:Triage_guide maemo.org guide].

[[Category:QA]]

Quality/UpstreamBugTrackers

2011-06-23T09:06:13Z

Andre: add downstream bug tracker section for Harmattan MeeGo 1.2

== Practice ==

If a bug in code or in translations exists that comes from an "upstream" project and that was not changed in ("downstream") MeeGo it is common practice to forward this bug report to the corresponding upstream bugtracker.

This makes upstream developers / translators become aware of issues (that were found in MeeGo but affect any other downstream projects too) so they can get fixed upstream. Patches are of course also welcome to be attached in an upstream report.

Fixing issues upstream reduces the efforts of maintaining downstream patches. It is welcome to query first in the upstream bugtracker for a potentially already existing report covering the issue.

In case an upstream bug has been filed or has been found, add the URL to the field "See Also: Add Bug URLs:" in the report in bugs.meego.com, and vice versa if possible. CC yourself to the upstream bug report to keep track and update the report in bugs.meego.com once it is fixed upstream.

== Mapping ==
{| border="1" + Upstream Bug Trackers
!rowspan="2"|MeeGo Components
!colspan="3"|Upstream
|-
! Project
! Bugtracker URL
! Product for Translation Issues
|-
| Alsa
| Alsa
| https://bugtrack.alsa-project.org/alsa-bug/
|
|-
| Cairo, Exempi, Xorg
| FreeDesktop.org
| https://bugs.freedesktop.org/
|
|-
| Giflib
| Giflib
| http://sourceforge.net/tracker/?group_id=102202
|
|-
| Banshee, librest, libsocialweb
| Gnome
| https://bugzilla.gnome.org/
| L10N
|-
| Icu
| Icu
| http://bugs.icu-project.org
|
|-
| KDE
| KDE
| https://bugs.kde.org/
| i18n
|-
| Fennec
| Mozilla
| https://bugzilla.mozilla.org/
|
|-
| Iptables
| Netfilter/Iptables
| http://bugzilla.netfilter.org/
|
|-
| ntp
| ntp
| http://bugs.ntp.org/
|
|-
| PulseAudio
| PulseAudio
| http://pulseaudio.org/report
|
|-
| Qt
| Qt
| http://bugreports.qt.nokia.com
|
|-
| sudo
| sudo
| http://www.sudo.ws/bugs/
|
|-
| SWI-Prolog
| SWI-Prolog
| http://www.swi-prolog.org/bugzilla/
|
|-
| WebKit, WebCore, CoreJS
| WebKit
| https://bugs.webkit.org/
|
|}

If the component you're looking for isn't listed here, please add it, possible places to find further bug trackers include:
* Ubuntu: https://launchpad.net/bugs/bugtrackers/
* Gnome: http://live.gnome.org/Bugsquad/TriageGuide/NonGnome

== Other bug trackers ==

=== Components related to MeeGo ===

For components that related to MeeGo but not part of MeeGo.

{| border="1" + Other Bug Trackers
! Project
! Bugtracker URL
|-
| Peregrine
| http://bugs.peregrine-communicator.org/
|}

=== Downstream MeeGo products ===

For products that are based on MeeGo.

{| border="1" + Other Bug Trackers
! Project
! Bugtracker URL
|-
| Nokia MeeGo 1.2 Harmattan
| http://www.developer.nokia.com/bugs/
|}

[[Category:QA]]

Quality

2011-06-23T07:56:27Z

Andre: Reverted edits by Noel (talk) to last revision by Jaritah

= Quality =

This page is for MeeGo Quality Assurance related material.

== Projects ==

For all test reports see [http://qa-reports.meego.com http://qa-reports.meego.com]

{| border = 1 valign="top"
! Release
! Core OS
! Handset UX
! Tablet UX
! Netbook UX
! SDK
! In Vehicle Infotainment
|-
| Release 1.3
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.3/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [[Quality/Plans/Handset UX test plan|MeeGo HandSet UX Test Plan]]
* [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests Test Suite]
* [http://qa-reports.meego.com/1.3/Handset Handset Test Reports]
|
* Tablet UX Test Plan
* Tablet UX Test Suite
* [http://qa-reports.meego.com/1.3/Tablet Tablet Test Reports]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.3/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.3/SDK SDK Test Reports]
|
* [[/Plans/IVI Test Plan | MeeGo IVI Test Plan]]
* IVI Test Suite
* [http://qa-reports.meego.com/1.3/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|-
| Release 1.2
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.2/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/Plans/1_2_Handset_UX_test_plan MeeGo HandSet UX Test Plan]
* [[Quality/TestSuite/handset-test-suite|Test Suite]]
* [http://qa-reports.meego.com/1.2/Handset Handset Test Reports]
* [[Quality/HandsetQualityMetrics|Quality Metrics]]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/Tablet Tablet Test Reports]
* [[Quality/TabletQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/1.2NetbookTestPlan 1.2 SW Update Test Plan]
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.2/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.2/SDK SDK Test Reports]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|}

== QA tools ==

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
* [[Quality/QA-tools|Meet the team and find our tools]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet)
* [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution.
* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions how to automate test execution and image installations.

== Procedures and best practices ==

* [[Quality/Plans/Testability-checklist|Feature Testability Checklist]]
** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** This is a guide for QA contacts about how to comment on feature testability so as to provide as much information as possible to test developers.
*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

* [[/defects | Defects Management]]
* [[/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[/Bugzilla_Fields|Fields in a bug report]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [[/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]] -- WORK IN PROGRESS, please contribute
* [[/SysDebug | MeeGo Sys-Debug]] (finding the right component for a report)
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|Bugzilla customized features]]
* [[/MeeGoBugzillaRequestProcess|Requests for changes in Bugzilla code/UI itself]]

== Error Management ==
See the [[Quality/Error Management]] subpage.

== Compliance Program ==
[[Quality/Compliance | MeeGo Compliance Program]] - the compliance spec (initially)

== Contact ==

* Mailing List: [http://lists.meego.com/listinfo/meego-qa MeeGo-QA]
* IRC: Channel #meego-qa on irc.freenode.net

== Meetings ==

General QA Meetings are held weekly on Tuesdays 07:00 UTC in the channel #meego-meeting on irc.freenode.net. [[Quality/Meetings|Click here for more information.]]

QA Tools meetings are held weekly on Tuesdays 08:00 UTC in the channel #meego-meeting2 on irc.freenode.net. [[Quality/QA-tools/Meetings|Click here for more information.]]

For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]].

== See also ==

* [[/Glossary | QA Glossary ]]
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]]
* [[Quality/Plans/Quality-considerations|Quality Considerations / Testing Quality Characteristics]]
** Some ideas around testing quality characteristics hopefully helping you identify what kind of things could be checked from applications - can be used as a frame to define test considerations – as a set of logical test cases - for applications targeting to run on MeeGo.

== Questions and Answers ==

* What is the QA contact expected to do actually?
** QA contact work with/support/advice/help package maintainers (see Fedora example [[http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility ]] or MeeGo guidelines for maintaining package [[http://wiki.meego.com/Packaging/Guidelines#Maintaining_a_Package ]]) and other users on QA related issues/questions for component in case.
*** Features ("Once a requirement is integrated, MeeGo QA verifies it by running the corresponding test cases." from [[https://meego.com/developers/requirements ]])
**** make testability analysis for features (yes or no value to testability field) and
**** identify "feature acceptance tests" together with product management and package maintainers that could be used at the end as a criteria for feature status to be changed as "VERIFIED".
*** Bugs ("QA Contact or Bug Submitter verifies bug fixing with the "how to re-produce" instructions in the original bug report when the bug is marked as RELEASED - FIXED." from [[http://wiki.meego.com/Quality/Bug_Life_Cycle_and_Handling ]])
**** facilitate the whole bug life-cycle from QA perspective, including ensure bug report completeness, follow up bugs by providing helpful or required information in timely fashion to accelerate bug fixing and verify the issue after fix is integrated, especially when the original reporter is not responsive or has difficulty to follow the bug up.
**** actively follow-up the bugs. Making sure the bug is attended properly, ping the default assignee or assignee or reporter to get visibility and comments on the progress, triage bugs, verify and close them whenever possible.

[[Category:QA]]

Quality/IVIQualityMetrics

2011-06-22T08:27:08Z

Andre: fix typo

((***** Working in Progress *****))

=== Key Messages ===
< Anything to highlight here >

=== MeeGo 1.2 - IVI Release Blockers ===

* '''See [[Quality/IVI_1.2_Update | more detailed bug status about 1.2 update]].'''

''Table. Open Blockers in numbers'' 
{| border="1"
! 2011-06-16
! MeeGo Release Blocker
! MeeGo Update Release Blockers
|-
|Approved
|3
|7
|-
|Proposed
|3
|9
|}

''Figure. Open Blockers Trend'' 
[[File:IVI_1.2_Open_blockers.png]] 

=== MeeGo 1.2 - IVI Bugs Status ===

* '''Open Bugs / Priority'''
** This graph shows the current status of the 1.2 IVI Open bugs by priority.
** [2011-06-16] 51 Bugs are open, including 16 High bugs.

''Figure. Open Bugs / Priority'' 
[[File:IVI_1.2_open_bug_priority.png]] 

* '''Top 3 Components'''
''Table 1. Bugs / Components in numbers'' 
{| border="1"
! Component
! 2011-06-16
|-
|Sample applications
|5
|-
|meego-ux-ivi
|9
|-
|Graphics
|8
|-
|Generic
|6
|} 

* '''Top/Hot issues'''
{{#bugzilla:
|columns=id,priority,severity,version,status,resolution,summary
|product=MeeGo IVI,MeeGo User Experience,OS Base,OS Middleware, Handset User Experience
|version=1.2,1.2.0
|group=component
|cc=ivi-bugs@meego.com
|id=19087,16997,19377,19386
|sort=component,priority,id
}}
* '''Accumulated bugs'''
''Table. Accumulated Bug in numbers / Status'' 
{| border="1"
! Status
! MeeGo IVI
! OS Base/Middlware
! MeeGo/Handset User Experience
! Total
|-
|NEW
|34
|2
|0
|36
|-
|ASSIGNED
|6
|2
|1
|9
|-
|NEEDINFO
|2
|0
|0
|2
|-
|WAITING FOR UPSTREAM
|0
|0
|0
|0
|-
|REOPENED
|4
|1
|0
|5
|-
|RESOLVED
|22
|2
|0
|24
|-
|RELEASED
|13
|0
|0
|13
|-
|VERIFIED
|174
|10
|2
|186
|-
|CLOSED
|2
|0
|0
|2
|-
|Total
|257
|17
|3
|277
|} 

=== MeeGo 1.3 - IVI Bugs Status ===

* '''Open Bugs / Priority'''
** This graph shows the current status of the 1.3 IVI Open bugs by priority.
''Figure. Open Bugs / Priority'' 
[[File:IVI_1.3_open_bug_priority.png]] 

* '''Top 3 Components'''
''Table 1. Bugs / Components in numbers'' 
{| border="1"
! Component
! 2011-06-09
|-
|Kernel and drivers(Northville)
|8
|-
|Graphics
|4
|-
|Sample applications
|4
|} 

* '''Top/Hot issues'''
{{#bugzilla:
|columns=id,priority,severity,assignee,status,resolution,summary
|product=MeeGo IVI,MeeGo User Experience,OS Base,OS Middleware, Handset User Experience
|version=1.3
|group=component
|cc=ivi-bugs@meego.com
|id=15157
|sort=component,priority,id
}}
 
* '''Accumulated bugs'''
''Table. Accumulated Bug in numbers / Status'' 
{| border="1"
! Status
! MeeGo IVI
! OS Base/Middlware
! MeeGo/Handset User Experience
! Total
|-
|NEW
|21
|1
|0
|22
|-
|ASSIGNED
|6
|0
|0
|6
|-
|NEEDINFO
|0
|0
|0
|0
|-
|WAITING FOR UPSTREAM
|0
|0
|0
|0
|-
|REOPENED
|0
|0
|0
|0
|-
|RESOLVED
|0
|3
|0
|3
|-
|RELEASED
|0
|0
|0
|0
|-
|VERIFIED
|0
|0
|0
|0
|-
|CLOSED
|0
|0
|0
|0
|-
|Total
|27
|4
|0
|31
|} 

=== MeeGo 1.2&1.3 - IVI Bug Activities ===
* '''New bugs / week'''
** This graph shows how many IVI bugs are newly reported or verified per week

''Figure. New/Fixed bugs / week'' 
[[File:IVI_new_fixed_bugs_week.png]] 

=== MeeGo 1.2&1.3 - IVI Bug Inactivities ===

* '''High Bugs Status = NEW for >=2 weeks''':
{{#bugzilla:
|columns=id,priority,severity,version,status,resolution,summary
|product=MeeGo IVI,MeeGo User Experience,OS Base,OS Middleware, Handset User Experience
|version=1.2,1.3
|priority=high
|group=component
|cc=ivi-bugs@meego.com
|id=14641,14830,14831,15704,16760,16876,16929,17135,17137,17177,17265,17460,17467,17502,17851,18005
|sort=component,priority,id
}}
 

* '''Bugs Status = RESOLVED/FIXED status for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?emailcc1=1&resolution=FIXED&classification=MeeGo%20Platform&emailtype1=substring&chfieldto=-14D&chfield=bug_status&query_format=advanced&chfieldvalue=RESOLVED&bug_status=RESOLVED&version=1.2&version=1.3&email1=ivi-bugs%40meego.com here]
{{#bugzilla:
|columns=id,priority,severity,version,status,resolution,summary
|product=MeeGo IVI,MeeGo User Experience,OS Base,OS Middleware, Handset User Experience
|status=RESOLVED
|resolution=FIXED
|version=1.2,1.3
|group=component
|cc=ivi-bugs@meego.com
|sort=component,priority,id
}}
 

* '''HIGH open bugs without update >= 1 month''':
{{#bugzilla:
|columns=id,priority,severity,version,status,resolution,summary
|product=MeeGo IVI,MeeGo User Experience,OS Base,OS Middleware, Handset User Experience
|version=1.2,1.3
|status=new,assigned,needinfo,waiting for upstream,reopened
|priority=high
|group=component
|cc=ivi-bugs@meego.com
|id=11
|sort=component,priority,id
}}

=== MeeGo 1.2&1.3 - IVI WONTFIX Bugs ===
Click [https://bugs.meego.com/buglist.cgi?emailcc1=1&resolution=WONTFIX&classification=MeeGo%20Platform&emailtype1=substring&query_format=advanced&version=1.2&version=1.3&email1=ivi-bugs%40meego.com&product=MeeGo%20IVI here] to see all wontfix bugs of MeeGo IVI

Glossary

2011-06-21T16:20:04Z

Andre: add CE

MeeGo has many terms whose meaning is not immediately apparent. This page will attempt to help rectify that.

== A ==
;''Architecture: ''
:The Meego architecture describes the components for the whole system and is broken down into Layer, Domain and Api http://meego.com/developers/meego-architecture

;''ARM: ''
:The CPU powering the N900 and many other mobile devices. See [[ARM]]

;''ATM: ''
:At The Moment

== B ==

;''Beagle-board: ''
:Is an OMAP3 based development board suitable for embedded projects. See [[ARM/Meego on the Beagle]]

;''BME (Battery Management Entity): ''
:Is proxied to D-Bus via the bme-dbus-proxy daemon

;''BOSS: (Build Orchestration Supervision System) ''
:Is the workflow tool for releases. See [[Release Infrastructure/BOSS]]

== C ==

;''CE''
:Community edition

;''Compliance: ''
: is designed to make sure things stay compatible, such that the devices supporting a particular MeeGo version can run the same software. [[Quality/Compliance]]

== D ==

;''DE''
:Developer edition. Has been renamed in June 2011 to CE (Community Edition).

;''DirectUI (DUI)''
:see MeeGo Touch Framework

;''Dual Boot''
:is a way of allowing meego devices to run multiple operating systems. See [[ARM/N900/Install/Dual Boot]]

== E ==
;''EMGD (Embedded Media and Graphics Driver) ''
: are Intel graphics drivers required for a number of netbook class devices http://edc.intel.com/Software/Downloads/EMGD/
: Currently not part of the standard netbook release images.

== F ==

;''FOSS: ''
:Free/Open Source Software

;''Fremantle: ''
:current Maemo 5 release *

== G ==
;''GMA500 (Graphics Media Accelerator 500) ''
: is the 3d graphics chip built into many Intel Atom based chipsets, related to the EMGD driver

== H ==
;''Handset''
: is one of the key components and deliverables of the Meego project http://meego.com/devices/handset/
;''Harmattan: ''
:future Maemo 6 (now MeeGo handheld) release by Nokia, to include bundled officially-supported Qt libraries, see MeeGo-Harmattan
;''Harmattan UI framework: ''
:see MeeGo Touch Framework
;''Harmattan UX''
:the user interface and applications of MeeGo-Harmattan.
;''HXT''
: MeeGo Handset Execution Team

== I ==

;''IRC (Internet Relay Chat) ''
:one of the key collaborative areas for Meego working and discussion

;''IIRC: ''
:If I Recall Correctly

;''IMG''
:Image creator

;''Intel''
: principle founding company (along with Nokia) of the Meego project
== K ==

;''Kernel (linux)''
: is the open source core of the operating system and without which we would not have Meego! See [[MeeGo kernel documentation for contributors]]

;''Kickstart files (.ks)''
: provide a list of packages and settings to use for automated installs. See [[Image Creation]]

== L ==

;''LSB (Linux Standard Base): ''
:The goal of the LSB is to develop and promote a set of open standards that will increase compatibility among Linux distributions and enable software applications to run on any compliant system even in binary form.

== M ==
;''MADDE''
:Maemo Application Development and Debugging Environment and offers the following features:
:* Command-line cross-compiling
:* Multi-platform support (Linux (32-bit/64-bit), Windows, Mac OS X)
:* Configurable for different targets & toolchains
:* Client for the device to simplify the development process
:It will used as part of future releases of the MeeGo SDK, along with QEMU, to enable cross-OS development.
;''Maemo''
:a software platform developed by Nokia for smartphones and Internet Tablets. It was initially based on the Debian Linux distribution. One of the predecessors of MeeGo, along with Moblin.
;''Maemo 5''
:the default operating system on the Nokia N900, and current latest stable and independent version of Maemo. Based on the GTK toolkit. Aliases: Fremantle
;''Maemo 6''
:see MeeGo-Harmattan
;''Maemo 6 UI framework''
:see MeeGo Touch framework
;''MeeGo''
:an open source, Linux project which brings together the Moblin project, headed up by Intel, and Maemo, by Nokia, into a single open source activity. Managed by the Linux Foundation. The important thing to note that you end users will mostly be using an edition of MeeGo, MeeGo itself is not a single product (that’s why "will X run/get MeeGo" is a bad question), just like people are using a Linux distributions, not Linux (as in kernel) alone.
;''MeeGo Compatible''
:something that implements the [http://meego.com/developers/meego-api MeeGo APIs], but is not necessarily based on MeeGo Core (for example Meego-Harmattan).
;''MeeGo Core 1.0''
:the base of every MeeGo system ([http://meego.com/sites/all/files/users/u13/MeeGoArch1.png diagram]), and described in detail [http://meego.com/developers/meego-architecture here]. It contains:
:* Kernel based on Linux 2.6.33
:* DeviceKit and udev for interacting with hardware devices
:* Modern 2D/3D graphics stack including Kernel Mode Setting, non-root X
:* Voice and data connectivity with Connman connection manager, Ofono telephony stack and BlueZ Bluetooth
:* Qt 4.6
:* Universal Plug and Play (gUPnP)
:* Media frameworks
:* Next generation file system BTRFS, as the default file system
:* Does NOT contain a user interface or end-user applications
;''MeeGo Garage''
:A client app installer in the MeeGo 1.0 Netbook release containing miscellaneous applications not part of the official MeeGo release and open for contributions from community. The name "Garage" may be changed in future releases. Ongoing community work is happening to create the official community repositories.
;''MeeGo Handheld''
:MeeGo Core + MeeGo Touch Framework + Reference Handheld UX (not yet released).
;''MeeGo Hardware adaptation project for the N900''
:Nokia as founding member of MeeGo project is using N900 as the ARM reference platform of MeeGo at the moment. This means that we have an active project that focuses to make a MeeGo hardware adaptation for the N900. The goal of the project is thus to open as much N900 specific drivers as possible in MeeGo scope.
;''MeeGo Hardware adaptation project for the N8x0''
:a 'skunkworks' project by the maemo.org community and others to bring MeeGo to Nokia N8x0, hence not a vendor-pushed hardware adaptation. Initially focus will be on Nokia N810. Some additional work to add support for ARMv6+VFP is also included in this.
;''MeeGo-Harmattan''
:the default operating system of the Nokia N9. Successor of Maemo 5, but based of the Qt toolkit. Originally named Maemo 6, but later rebranded as MeeGo-Harmattan (provisional name). It is MeeGo compatible (that is, has a MeeGo API) but is not to be confused with MeeGo 1.0 Handheld as it is NOT based on MeeGo Core. MeeGo-Harmattan will not be released as a Nokia product for the N900. Aliases: Harmattan, Maemo 6, MeeGo 1.0 N.
;''MeeGo Netbook''
:MeeGo Core + Reference Netbook UX
;''MeeGo SDK''
:A [[Getting started with the MeeGo SDK for Linux|software development kit for MeeGo]]
;''MeeGo Touch Framework (MTF)''
:provides the features needed for developers creating applications for touch-enabled devices. Features include standardized window navigation, list and other widget behavior, and common theming for components.
;''MeeGo Web RunTime''
:Web Runtime (WRT) allows web developers to use standard web languages — HTML, CSS, and JavaScript — to create applications for mobile devices. WRT exposes the features of the underlying platform so that applications can interact with device data and combine location-based context with web information.
;''MeeGo 1.0 N''
:A name which has appeared on [http://www.slideshare.net/NokiaAppForumBulgaria/software-development-with-qt some] [http://www.slideshare.net/elenakotina/qt-quick-qml Nokia] slides as a synonym for Harmattan. See MeeGo-Harmattan.
;''Moblin''
:short for 'mobile Linux', is an open source operating system and application stack for Mobile Internet Devices (MIDs), netbooks, nettops, and embedded devices. One of the predecessors of MeeGo, along with Maemo.
;''Moblin 2.1''
:last stable independent release of Moblin
;''Moblin 2.2''
:see Meego 1.0 Netbook

== N ==

;''Nokia''
: principle founding company (along with Intel) of the Meego project

;''Nokia Qt SDK''
:A custom version of the Qt SDK, which includes additional functionality for developing for Symbian/Maemo devices (with announced MeeGo support later on). These include tools for cross compiling (see MADDE) and simulation. Not to be confused with the Qt SDK as the two are not interchangeable due to a custom mix of features (neither is a a superset of the other)

;''N900''
: Nokia ARM powered handheld phone for open Meego development. See [[ARM/N900]]

;''Netbook''
: is one of the key components and deliverables of the Meego project http://meego.com/devices/netbook/

== O ==
;''OBS (OpenSuse Build System) : ''
:The Opensuse Build Service. is an open and complete distribution development platform that provides a transparent infrastructure for development. The service provides software developers with a convenient and easy to use tool to create and release open source software for openSUSE and other Linux distributions on different hardware architectures and for a broad user audience. See [[Build System]]

;''OCS (Open Collaboration Services) : ''
: a web API for browsing application catalogues, doing event and contact discovery [http://www.freedesktop.org/wiki/Specifications/open-collaboration-services OCS API]. Also, OBS command line client

;''Orbit''
:see UI Extensions for Mobile

;''OSSO (Open Source Software Operations): ''
:It was a department inside Nokia responsible for producing Maemo. It has been replaced by Maemo Software.

;''OTS (Open Test System): ''
:Suite of testing tools and configuration files for managing reproducible QA testing. See [[Quality/QA-tools/OTS|OTS Wiki]]

== P ==
;''PA (PulseAudio)''
: is the low level sound system component used by Meego. See [[Quality/TestSuite/PulseAudio Test Plan]]

== Q ==
;''QML''
:a Declarative UI tool, in effect a markup language that defines UI elements and their behavior in a declarative manner, allowing, snappy, whizzy UIs. Present in Qt4.7+

;''Qt''
:a cross-platform application and UI framework. Using Qt, you can write web-enabled applications once and deploy them across desktop, mobile and embedded operating systems without rewriting the source code.

;''Qt Quick''
:the Qt User Interface Creation Kit, which consists of QML, a specialized editor in QtCreator and all-around support for the declarative approach. Present in Qt4.7+. Aliases: Qt Declarative, Declarative UI, Bauhaus.

;''Qt SDK''
:The software development kit for the Qt framework

;''QtMobility''
:extends Qt with libraries providing additional features for applications targeting mobile platforms. These include the Service Framework and Contact and Bearer Management APIs, Messaging, Sensors, Camera, etc.

== R ==
;''Reference Netbook UX''
:a reference (example) implementation of a user interface for netbooks, utilizing Moblin’s Clutter-based MX toolkit. It is expected to be replaced or augmented with manufacturer provided user interfaces/system applications on actual devices.

;''Reference Handheld UX''
:a reference (example) implementation of a user interface for handheld devices, based on the MeeGo Touch framework. It is expected to be replaced or augmented with manufacturer provided user interfaces/system applications on actual devices.

;''REVS''
:Release Engineering Visibility System

== S ==

;''SR: ''
:Submit Request
:A submit request holds together all the changes relating to a specific fix.
:Bug reports commonly refer to them by SR #
:The Meego Commits mailing list documents the progression of each SR
:A Front end for SRs may be in place once the BOSS system becomes operational
:http://lists.meego.com/pipermail/meego-commits/

;''SSO: ''
:Single Sign On

;''SVC (Social Vendor Contract): ''
:A social contract for vendors to commit to, in order to have community spending time on them and not waste their time and end up with locked devices with a open system.

== T ==
;''TMO (talk.maemo.org): ''
:Main forum for Maemo non-technical community.

;''UC (Use Case): ''
: Nokianism for Use case description in documentation.

== U ==
;''Uiemo''
:see UI Extensions for Mobile

;''UI Extensions for Mobile''
:UI Extensions for Mobile is an extension library for Qt, which contains more than 50 UI elements tailored for mobile user experience. There is a proposal to use UI Extensions for Mobile and Qt together with Direct UI as a replacement for the existing S60 'Avkon' set of UI elements in Symbian^4, but has been demonstrated to work on Maemo, too. UI Extensions for Mobile was previously known as Orbit and has been open sourced. Aliases: Uiemo, Orbit

== Useful links ==
* [http://www.acronymfinder.com Acronym Finder]
* [http://wiki.maemo.org/Codenames Maemo Codenames]

Main Page

2011-06-21T14:54:42Z

Andre: Reverted edits by Renatofilho (talk) to last revision by Dawnfoster

== MeeGo Project Functions ==
* [[Community Office]]
* [[Localization team|Localization]]
* [http://meego.com/about/governance/program-office Program Office]
* [[Core_OS_Program | Core OS Program]]
* [[Handset_Program | Handset UX Program]]
* [[In-vehicle | In Vehicle Infotainment - IVI]]
* [[Product Management]]
* [[Quality]]
* [[Release_Engineering|Release Engineering]]
* [http://meego.com/about/governance/ui-design User Interface Design]
* [[SDK]]
* [[Architecture]]
* [[Meego IT]]

= User =

* [[MeeGo Netbook FAQ]]
* [http://meego.com/devices/netbook/installing-meego-your-netbook Install MeeGo on your netbook]
* [[Devices|Supported devices]]
* [[Install MeeGo from Hard Disk]]

= Developer =
== Developer Guide ==

* [[SDK/Docs/1.1|Developer Guide for MeeGo 1.1]]
* [[SDK/Docs/1.0|Developer Guide for MeeGo 1.0]]
* [[Build_Infrastructure | Build Infrastructure]]
* [[MeeGo Porting Guide]]
* [[QML tutorials]] - Some tutorials to help get started with QML, the Qt Modelling Language.
* [http://mxr.meego.com/ MeeGo cross reference] - Index of MeeGo source code

Other documents:
{| border="1"
! Document
! Variety (Version)
! Architectures
|-
|Instructions for [[ARM|ARM based devices (N900, BeagleBoard, PandaBoard, Snowball)]]
|All
|ARM
|-
|Instructions for [[MeeGo_1.0_Netbook_VirtualBox|VirtualBox]]
|Netbook (1.0)
|Intel
|-
|Instructions for [[MeeGo SDK on Windows with VirtualBox]]
|All
|All
|-
|Tips for [[Developing With The Aava]]
|Handset/Aava
|Intel
|}

== Release Process ==
The MeeGo Release Process includes:
* [[Release_Engineering/Process|Release process and work flow]]
* [[Release_Engineering/Release_Timeline|MeeGo releases every 6 months]]
* [[Release_Engineering/Process|Nightly builds for developers and weekly releases will be available]]

== MeeGo Components ==
* [[MeeGo_UX_Components|MeeGo Components]] - Supported common QML components

= Community =

== Contributing to MeeGo ==
* Read our [[Community guidelines]]: [[Wiki contribution guidelines|Wiki]], [[Mailing list guidelines|mailing list]], [[Forum/Guidelines|forum]], and [[Community guidelines|more]].
* [[Community communication|Participate in our forums, mailing lists, and more]].
* [http://meego.com/about/contribution-guidelines Contribute to MeeGo].
* [[Build_Infrastructure/Community_Builder|Building applications]] for MeeGo

See also [[Who's who]].

== Meetings ==

[[MeeGo-Meeting IRC Schedule]]

The following groups have regular meetings, see their respective pages for details.

* [[Technical Steering Group meetings]]
* [[Community Office/Meetings|Community Office meetings]]
* [[Localization team]]

Regional Activities.
* [[Local MeeGo Networks]]

== Bi-Annual MeeGo Conference ==

'''Upcoming Conferences'''
* [[MeeGo Conference Spring 2011|Spring 2011: May 23 - 25 at the Hyatt Regency, San Francisco]]
* [[MeeGo Conference Fall 2011|Fall 2011: November Date TBD in Europe]]

'''Past Conference Wrap-Up Information'''
* [[MeeGo_Conference_2010|Fall 2010: November 15 - 17 in Dublin]]

== Structure and Governance ==

MeeGo is an open source project led by the MeeGo Technical Steering Group (TSG). The governance model is based on meritocracy and the best practices and values of the Open Source culture. The MeeGo project lives under the auspices of the Linux Foundation.

* [http://meego.com/about/governance MeeGo Project Structure and Governance Overview]
* Bi-weekly [[Technical Steering Group meetings]]
* [[Working Group Process]]

== Resources ==
* [[MeeGo FAQ]]
* [[Glossary|Glossary and Acronyms]]
* [[Community guidelines]]
* [[Special:PopularPages|Popular Wiki Pages]]
* [[Special:MostLinkedPages|Most Linked-to Pages]]

[[Category:Top level]]

Quality/MeeGoBugzillaRequestProcess

2011-06-17T09:57:54Z

Andre: fix my wiki markup, as usual

=Processes to handle MeeGo Bugzilla Requests=

DRAFT STATUS - see [http://lists.meego.com/pipermail/meego-qa/2011-June/001940.html mailing list thread]

This process is to ensure new features or changes to MeeGo Bugzilla itself are implemented & deployed under the planned way and also to ensure the MeeGo Bugzilla features & changes are generic enough for most users.

==How MeeGo Bugzilla requests are handled==
* Have a [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com bug report] or [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com%20Features feature request] for the complete requests both for code level and new custom fields & new flags;
* Error management team will provide feedback in one working day normally once receive the request notification;
* The follow up and feedbacks should happen in the bug/feature comments in the report;
* For minor change like component adjustment and component owner changes, MeeGo Bugzilla admins will go ahead directly but should be done by filing a bug report (for the sake of transparency);

==Process to accept & review & integrate code level changes==
* There will be a personal repository branch for each one has the source code submission privilege in [http://gitorious.net/meego-bugzilla MeeGo Bugzilla git repository];
* Submit the new feature & bug fix into personal repository branch;
* Merge the changes into staging branch after code cross review;
* Deploy the changes into staging Bugzilla;
* Feedbacks from testing on our staging instances ([https://01.bugs-dev.meego.com/ 1], [https://02.bugs-dev.meego.com/ 2]);
* Merge the changes from staging branch to production branch once code quality is good enough;
* Deploy the changes into production Bugzilla;

Quality/MeeGoBugzillaRequestProcess

2011-06-17T09:56:57Z

Andre: remix; see http://lists.meego.com/pipermail/meego-qa/2011-June/001953.html for more info

=Processes to handle MeeGo Bugzilla Requests=

DRAFT STATUS - see [http://lists.meego.com/pipermail/meego-qa/2011-June/001940.html|mailing list thread]

This process is to ensure new features or changes to MeeGo Bugzilla itself are implemented & deployed under the planned way and also to ensure the MeeGo Bugzilla features & changes are generic enough for most users.

==How MeeGo Bugzilla requests are handled==
* Have a [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com|bug report] or [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com%20Features|feature request] for the complete requests both for code level and new custom fields & new flags;
* Error management team will provide feedback in one working day normally once receive the request notification;
* The follow up and feedbacks should happen in the bug/feature comments in the report;
* For minor change like component adjustment and component owner changes, MeeGo Bugzilla admins will go ahead directly but should be done by filing a bug report (for the sake of transparency);

==Process to accept & review & integrate code level changes==
* There will be a personal repository branch for each one has the source code submission privilege in [http://gitorious.net/meego-bugzilla|MeeGo Bugzilla git repository];
* Submit the new feature & bug fix into personal repository branch;
* Merge the changes into staging branch after code cross review;
* Deploy the changes into staging Bugzilla;
* Feedbacks from testing on our staging instances ([https://01.bugs-dev.meego.com/|1], [https://02.bugs-dev.meego.com/|2]);
* Merge the changes from staging branch to production branch once code quality is good enough;
* Deploy the changes into production Bugzilla;

Quality

2011-06-16T09:45:28Z

Andre: /* Defect tracking */

= Quality =

This page is for MeeGo Quality Assurance related material.

== Projects ==

For all test reports see [http://qa-reports.meego.com http://qa-reports.meego.com]

{| border = 1 valign="top"
! Release
! Core OS
! Handset UX
! Tablet UX
! Netbook UX
! SDK
! In Vehicle Infotainment
|-
| Release 1.3
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.3/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [[Quality/Plans/Handset UX test plan|MeeGo HandSet UX Test Plan]]
* [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests Test Suite]
* [http://qa-reports.meego.com/1.3/Handset Handset Test Reports]
|
* Tablet UX Test Plan
* Tablet UX Test Suite
* [http://qa-reports.meego.com/1.3/Tablet Tablet Test Reports]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.3/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.3/SDK SDK Test Reports]
|
* [[/Plans/IVI Test Plan | MeeGo IVI Test Plan]]
* IVI Test Suite
* [http://qa-reports.meego.com/1.3/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|-
| Release 1.2
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.2/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/Plans/1_2_Handset_UX_test_plan MeeGo HandSet UX Test Plan]
* [[Quality/TestSuite/handset-test-suite|Test Suite]]
* [http://qa-reports.meego.com/1.2/Handset Handset Test Reports]
* [[Quality/HandsetQualityMetrics|Quality Metrics]]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/Tablet Tablet Test Reports]
* [[Quality/TabletQualityMetrics | Quality Metrics]]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.2/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.2/SDK SDK Test Reports]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|}

== QA tools ==

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
* [[Quality/QA-tools|Meet the team and find our tools]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet)
* [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution.
* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions how to automate test execution and image installations.

== Procedures and best practices ==

* [[Quality/Plans/Testability-checklist|Feature Testability Checklist]]
** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** This is a guide for QA contacts about how to comment on feature testability so as to provide as much information as possible to test developers.
*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

* [[/defects | Defects Management]]
* [[/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[/Bugzilla_Fields|Fields in a bug report]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [[/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]] -- WORK IN PROGRESS, please contribute
* [[/SysDebug | MeeGo Sys-Debug]] (finding the right component for a report)
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|Bugzilla customized features]]
* [[/BugzillaRequestProcess|Requests for changes in Bugzilla code/UI itself]]

== Error Management ==
See the [[Quality/Error Management]] subpage.

== Compliance Program ==
[[Quality/Compliance | MeeGo Compliance Program]] - the compliance spec (initially)

== Contact ==

* Mailing List: [http://lists.meego.com/listinfo/meego-qa MeeGo-QA]
* IRC: Channel #meego-qa on irc.freenode.net

=== Meetings ===

General QA Meetings are held weekly on Tuesdays 07:00 UTC in the channel #meego-meeting on irc.freenode.net. [[Quality/Meetings|Click here for more information.]]

QA Tools meetings are held weekly on Tuesdays 08:00 UTC in the channel #meego-meeting2 on irc.freenode.net. [[Quality/QA-tools/Meetings|Click here for more information.]]

For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]].

== See also ==

* [[/Glossary | QA Glossary ]]
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]]
* [[Quality/Plans/Quality-considerations|Quality Considerations / Testing Quality Characteristics]]
** Some ideas around testing quality characteristics hopefully helping you identify what kind of things could be checked from applications - can be used as a frame to define test considerations – as a set of logical test cases - for applications targeting to run on MeeGo.

[[Category:QA]]

User:Andre/Bug Summary Prefixes

2011-06-15T17:07:14Z

Andre:

= Bug summary prefixes in bugs.meego.com =

{|
| style="background: #ffcc00; color: black" | '''Note:''' First and rough list. Does not mean that the current practice necessarily makes sense, just trying to document it. -- [[User:Andre]] 2011-05-17
|}

== List ==

Feel free to edit, but please keep the alphabetical order.

{| border="1" + Items
! Prefix
! Description
|-
| [CONX]
|
|-
| [CD] and [DE]
| Bug is reproducible only with [http://wiki.meego.com/ARM/N900/DeveloperEdition N900 Development Edition] / Community Edition image
|-
| [FEA]
| Feature request
|-
| GLS -
| outdated, stands for "Global Language Solutions". Replaced by [L10N] and [I18N]
|-
| [Installer]
|
|-
| [I18N]
| For issues in the codebase (not in translations themselves) that are related to using other languages
|-
| [IVI]
|
|-
| [L10N]
| For issues in translations (not in the codebase itself)
|-
| [MCTS-]
| For bug related to MCTS
|-
| [Meta] / [META] / [METABUG]
| For collecting bug reports from same area together (e.g. power management issues) by using 'Depends on'.
|-
| [MTF]
|
|-
| [MWTS-]
| For bug related to MWTS
|-
| [REG]
| Regression
|-
| [Trunk:Daily] / [trunk: daily] / [Trunk : Daily]
|
|-
| [Trunk:Testing]
|
|}

[[Category:QA]]

Quality/Meetings

2011-06-13T19:43:06Z

Andre: add links to three emails on meego-qa covering SF conference meeting minutes

== Logistics ==

Until further notice, the MeeGo QA meets every Tuesday at 07:00 UTC for one hour.
All MeeGo QA meetings take place in the MeeGo IRC channels:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego-qa
Propose a topic in advance by editing this page (#Next Meeting). Please note the following before proposing a topic:
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic.
* The people behind the proposal need to take part in the MeeGo QA meeting.
Resolution - Agenda is frozen approximately 18 hours before the meeting. If there is too many items then chair will pick the topics to be discussed and the rest will be moved to next meeting.
* Topics proposed might be addressed through other channels as well, being answered through other channels or being forwarded to the right team.

== Next Meeting ==
'''Tuesday June 14th 2011 07:00 UTC''' - Agenda Proposal

This meeting is focusing different process and procedure related items. If time we will also have short period for questions to QA Leads. Please anyhow remember to update your verticals QA status.

* Opening and general news
* Actions from previous meetings (2011-06-07)
* Follow up and discussion: N900 DE development's commitment to handset UX bugs -- see we should handle existing handset UX bugs
* Follow up: 1.3 QA plan and 1.3 features testability review
* Proposal: adding Yanshuang Zheng and Jie Zhou in error manager team of meego.com
** Yanshuang Zheng is focusing on core bugs triage, followup, indicator etc.
** Jie Zhou will look at FNV, NEEDINFO bugs etc to facilitate bug lifecycle
*** What does FNV stand for? What are advantages in having them in EM? (The bigger a team, the harder to make decisions) --[[User:Andre|Andre]] 06:59, 30 May 2011 (UTC)
* Update to QA status (QA Leads and QA-tools)
** Leads create short summary to Wiki min 1h prior the meeting so that in the meeting we can concentrate on questions and discussion
** [[Quality/Meetings/QA leads update 1.2| Weekly Updates from QA Leads]]

== Logs ==
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-06-07-06.59.html 2011-06-07 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-31-06.59.html 2011-05-31 Meeting Minutes]
* [http://lists.meego.com/pipermail/meego-qa/2011-May/001678.html BoF MeeGo QA at MeeGo Conference San Francisco - Meeting minutes]
* [http://lists.meego.com/pipermail/meego-qa/2011-May/001695.html BoF MeeGo Bugzilla Structure Enhancement Prototype at MeeGo Conference San Francisco - Meeting minutes]
* [http://lists.meego.com/pipermail/meego-qa/2011-May/001673.html BoF MeeGo EM session at MeeGo Conference San Francisco - Meeting minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-17-07.00.html 2011-05-17 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-10-06.59.html 2011-05-10 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-03-07.00.html 2011-05-03 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-04-26-06.59.html 2011-04-26 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-19-07.00.html 2011-04-19 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-12-07.01.html 2011-04-12 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-29-07.06.html 2011-03-29 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-22-07.08.html 2011-03-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-15-06.59.html 2011-03-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-01-06.59.html 2011-03-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-22-07.00.html 2011-02-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-15-07.00.html 2011-02-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-08-07.00.html 2011-02-08 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-01-06.59.html 2011-02-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-25-07.01.html 2011-01-25 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-18-06.59.html 2011-01-18 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-11-06.59.html 2011-01-11 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-04-07.00.html 2011-01-04 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-28-07.00.html 2010-12-28 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-21-07.02.html 2010-12-21 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-14-07.01.html 2010-12-14 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-06.59.html 2010-12-07 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-30-06.59.html 2010-11-30 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-23-06.59.html 2010-11-23 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-14.31.html 2010-11-09 Meeting minutes]

== Materials used in meetings - if not anyplace else ==
* [[Quality/Meetings/QA nominations 101201| QA Nomination proposals for 1st of Dec 2010 TSG Meeting]]
* [[File:QAtoolproposal.pdf]] - proposal about new QA tool discussed on Dublin QA Workshop (un-conference day)

Quality/Bugzilla Fields

2011-06-13T10:19:49Z

Andre: and fix my markup

==MeeGo Release==

MeeGo Release field defines in which MeeGo version a bug has been found.
Version names are defined according to the [[Release_Engineering/Plans|MeeGo release plan]]. If a bug was reported already for an older MeeGo version make sure to [[Quality/defects#Bug Cleanup after Project Release|handle this bug as described here]].

==Target Build==

The main purpose of this field is for developers to predict on which build the bug can be fixed.

When developers get a bug and acknowledge the issue, they are expected to change the status from NEW to ASSIGNED, and set a Target Build to forecast when the issue can be fixed.

==Importance==
===Priority===

Priority field describes the importance and order in which a bug should be fixed. It helps developers to prioritize their work. By default the priority is set as "Undecided" when reporting a new bug. A bug triage team sets the initial priority for the bug, which might be changed. Priorities range from High (most important) to Low (least important).
* High: Bug fixing is on-going, or is planned within 2 weeks, no later than the up-coming milestone. Reproducible crash issues, major function loss, issues greatly impact user experience or issues which block other key features to work would fall in to this category.
* Medium: Bug fixing is planned before project release, but can't start before HIGH priority items are cleaned up.
* Low: Bug fixing is not planned for the up-coming project release. Will re-evaluate the importance in next release.

===Severity===

The "Severity" field describes the impact of an issue. The options include:

* Critical: crashes, other components are affected
* Major: major loss of own function
* Normal: regular issue, some loss of functionality under specific circumstances
* Trival:cosmetic problem like misspelled words or misaligned text
* Enhancement: request for enhancement

==Profile, Architecture and Platform==
===Profile===

The type of device (like Netbook, Nettop, Notebook, Handset, Automotive, TV) the issue has been identified in.
For bugs which apply to all UX (like bugs for Middleware/Core components), then "Common" should be selected.

===Architecture===

The architecture (like [[:wikipedia:Intel Atom|IA]], [[:wikipedia:ARM architecture|ARM]]) the issue has been identified in. For example N900 Base OS layer bugs are ARM, most Netbooks are IA.
For bugs which apply for multiple architectures, like bugs for middleware or applications, there is "All".

===Platform===

Platform field indicates the hardware platform against which the bug is detected, like ExoPC, Moorsetown, N900, Oaktrail, etc.

==Keywords==

[https://bugs.meego.com/describekeywords.cgi Keywords] can be added to reports to quickly find issues of the same keyword category across various products and components.

The adding and deleting of keywords will follow the common process of changes in Bugzilla. 

'''TODO:''' ''(The link will be added here once the wiki page of the common process is done)''.

==See Also==

This allows you to refer to bugs in other installations. You can enter a URL to a bug in the "Add Bug URLs" field to note that that bug is related to this one. You can enter multiple URLs at once by separating them with a comma.
 You should normally use this field to refer to bugs in other installations. For bugs in this installation, it is better to use the '''Depends On''' and '''Blocks''' fields.

==PM Comment==

This field is for MeeGo PM team to record the TODOs, AR (Action Required), etc for MeeGo release key issues. By using this field, PM comments can be easily found. And meanwhile, PM is able to export the data in custom field easily for further using.
* See [https://bugs.meego.com/show_bug.cgi?id=16304 this report] for the request for addition of a custom PM comment field.

==Triaged By==

"Triaged By" is used to track who in-depth triaged a bug report. This field is intended to be used by system debug engineers.
* Please refer to [http://wiki.meego.com/Quality/SysDebug SysDebug] for more information on usage of this field.

==Flag==
We use these customized flags to manage release blocker bugs.
* '''MeeGo_Update_Release_Blocker'''.
* '''MeeGo_Release_Blocker'''.
* '''MeeGo_N900DE_Release_Blocker'''.
Any users can propose blocker bugs for a specific release, and users in a priviliged groups, like Program Managers, approve/reject these blockers.

'''TODO:''' ''(This process needs documentation)'' --[[User:Andre|Andre]] 10:14, 13 June 2011 (UTC).

 MeeGo release version and these blocker flags are used together to identify blocker issues in each releases uniquely.
* See [https://bugs.meego.com/show_bug.cgi?id=9533 this report] for the request for addition of a MeeGo_Update_Release_Blocker field.

==Other reference pages==
* [[Quality/Bugtriage|MeeGo Bug Triage]]
* [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[Quality/How_To_Report_Bugs|How to report bugs]]

[[Category:QA]]

Quality/Bugzilla Fields

2011-06-13T10:14:58Z

Andre: fix some typos, add TODOs

==MeeGo Release==

MeeGo Release field defines in which MeeGo version a bug has been found.
Version names are defined according to the [[Release_Engineering/Plans|MeeGo release plan]]. If a bug was reported already for an older MeeGo version make sure to [[Quality/defects#Bug Cleanup after Project Release|handle this bug as described here]].

==Target Build==

The main purpose of this field is for developers to predict on which build the bug can be fixed.

When developers get a bug and acknowledge the issue, they are expected to change the status from NEW to ASSIGNED, and set a Target Build to forecast when the issue can be fixed.

==Importance==
===Priority===

Priority field describes the importance and order in which a bug should be fixed. It helps developers to prioritize their work. By default the priority is set as "Undecided" when reporting a new bug. A bug triage team sets the initial priority for the bug, which might be changed. Priorities range from High (most important) to Low (least important).
* High: Bug fixing is on-going, or is planned within 2 weeks, no later than the up-coming milestone. Reproducible crash issues, major function loss, issues greatly impact user experience or issues which block other key features to work would fall in to this category.
* Medium: Bug fixing is planned before project release, but can't start before HIGH priority items are cleaned up.
* Low: Bug fixing is not planned for the up-coming project release. Will re-evaluate the importance in next release.

===Severity===

The "Severity" field describes the impact of an issue. The options include:

* Critical: crashes, other components are affected
* Major: major loss of own function
* Normal: regular issue, some loss of functionality under specific circumstances
* Trival:cosmetic problem like misspelled words or misaligned text
* Enhancement: request for enhancement

==Profile, Architecture and Platform==
===Profile===

The type of device (like Netbook, Nettop, Notebook, Handset, Automotive, TV) the issue has been identified in.
For bugs which apply to all UX (like bugs for Middleware/Core components), then "Common" should be selected.

===Architecture===

The architecture (like [[:wikipedia:Intel Atom|IA]], [[:wikipedia:ARM architecture|ARM]]) the issue has been identified in. For example N900 Base OS layer bugs are ARM, most Netbooks are IA.
For bugs which apply for multiple architectures, like bugs for middleware or applications, there is "All".

===Platform===

Platform field indicates the hardware platform against which the bug is detected, like ExoPC, Moorsetown, N900, Oaktrail, etc.

==Keywords==

[https://bugs.meego.com/describekeywords.cgi Keywords] can be added to reports to quickly find issues of the same keyword category across various products and components.

The adding and deleting of keywords will follow the common process of changes in Bugzilla. 
| style="background: #ffcc00; color: black" | '''TODO:''' ''(The link will be added here once the wiki page of the common process is done)''.

==See Also==

This allows you to refer to bugs in other installations. You can enter a URL to a bug in the "Add Bug URLs" field to note that that bug is related to this one. You can enter multiple URLs at once by separating them with a comma.
 You should normally use this field to refer to bugs in other installations. For bugs in this installation, it is better to use the '''Depends On''' and '''Blocks''' fields.

==PM Comment==

This field is for MeeGo PM team to record the TODOs, AR (Action Required), etc for MeeGo release key issues. By using this field, PM comments can be easily found. And meanwhile, PM is able to export the data in custom field easily for further using.
* See [https://bugs.meego.com/show_bug.cgi?id=16304 this report] for the request for addition of a custom PM comment field.

==Triaged By==

"Triaged By" is used to track who in-depth triaged a bug report. This field is intended to be used by system debug engineers.
* Please refer to [http://wiki.meego.com/Quality/SysDebug SysDebug] for more information on usage of this field.

==Flag==
We use these customized flags to manage release blocker bugs.
* '''MeeGo_Update_Release_Blocker'''.
* '''MeeGo_Release_Blocker'''.
* '''MeeGo_N900DE_Release_Blocker'''.
Any users can propose blocker bugs for a specific release, and users in a priviliged groups, like Program Managers, approve/reject these blockers.
| style="background: #ffcc00; color: black" | '''TODO:''' ''(This process needs documentation)'' --[[User:Andre|Andre]] 10:14, 13 June 2011 (UTC).
 MeeGo release version and these blocker flags are used together to identify blocker issues in each releases uniquely.
* See [https://bugs.meego.com/show_bug.cgi?id=9533 this report] for the request for addition of a MeeGo_Update_Release_Blocker field.

==Other reference pages==
* [[Quality/Bugtriage|MeeGo Bug Triage]]
* [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[Quality/How_To_Report_Bugs|How to report bugs]]

[[Category:QA]]

User:Andre

2011-06-08T12:49:46Z

Andre:

=== About me ===

* Member of MeeGo Error Management for [http://www.openismus.com/ Openismus]
* [http://bugs.maemo.org maemo.org] Bugmaster for [http://www.openismus.com/ Openismus]
* a [http://live.gnome.org/ReleasePlanning/ GNOME Release Team] member (mostly QA and Schedule)
* a [http://bugzilla.gnome.org GNOME Bugzilla] Maintainer
* member of the [http://live.gnome.org/Bugsquad GNOME Bugsquad]
* member of the [https://live.gnome.org/TranslationProject/CoordinationTeam GNOME Translation Project Coordination team]
* member of the [http://l10n.gnome.org/languages/cs/ Czech GNOME translation team]
* [http://gnome.org/projects/evolution/ GNOME Evolution] Bugmaster Emeritus
* yet another student

=== Contact ===
* IRC nickname on Freenode: andre__
* [http://blogs.gnome.org/aklapper My blog]

=== Stuff ===

Random unfinished stuff I work(ed) on (once ready for review it is moved to proper URLs):
* [[/Surrounds_Bugtracking]]
* [[/Bug_Summary_Prefixes]]

Quality/Bugtriage Stock Answers

2011-06-03T11:47:25Z

Andre: add power management

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

===Skype===
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

====Missing Service Center field in SMS settings====

Could you attach here the output of /usr/lib/ofono/test/list-modems script?
Is the output of the above script showing anything in ServiceCenterAddress?

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall dialer
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer -prestart --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

== Power Management ==
Please always provide the output file of "powertop --html" on any power management issues. Thanks!

==SDK / Images==

=== Problems creating images ===

Please attach your config file /boot/extlinux/extlinux.conf in your image to this bug report.
[[Category:QA]]

Quality/Bugtriage Stock Answers

2011-05-31T21:08:59Z

Andre: Add Missing Service Center field in SMS settings as per https://bugs.meego.com/show_bug.cgi?id=14290#c1

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

===Skype===
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

====Missing Service Center field in SMS settings====

Could you attach here the output of /usr/lib/ofono/test/list-modems script?
Is the output of the above script showing anything in ServiceCenterAddress?

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall dialer
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer -prestart --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

==SDK / Images==

=== Problems creating images ===

Please attach your config file /boot/extlinux/extlinux.conf in your image to this bug report.
[[Category:QA]]

Quality/Bugtriage Stock Answers

2011-05-31T21:06:29Z

Andre: Enhance Dialer app instructions as per https://bugs.meego.com/show_bug.cgi?id=17675#c1

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

===Skype===
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall dialer
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer -prestart --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

==SDK / Images==

=== Problems creating images ===

Please attach your config file /boot/extlinux/extlinux.conf in your image to this bug report.
[[Category:QA]]

Quality/Bugtriage Stock Answers

2011-05-31T20:04:01Z

Andre: add SDK / Images section, from https://bugs.meego.com/show_bug.cgi?id=10660#c1

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

===Skype===
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

==SDK / Images==

=== Problems creating images ===

Please attach your config file /boot/extlinux/extlinux.conf in your image to this bug report.
[[Category:QA]]

Quality/Bugtriage Stock Answers

2011-05-31T20:03:02Z

Andre: fix markup

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

===Skype===
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

[[Category:QA]]

Quality/Bugtriage Stock Answers

2011-05-31T20:02:35Z

Andre: fix alphabetic sorting

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

==Skype==
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

[[Category:QA]]

Quality/Bugtriage Stock Answers

2011-05-31T20:02:01Z

Andre: add skype bugtracker URL

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

==Skype==
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.
See http://developer.skype.com/SkypeGarage/ReportIssue for reporting Skype issues.

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

[[Category:QA]]

Quality/Bugtriage Stock Answers

2011-05-31T20:00:57Z

Andre: Add SIP debug instructions from https://bugs.meego.com/show_bug.cgi?id=13945#c5

A quick and dirty collection for anybody triaging bug reports in [https://bugs.meego.com meego.com Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that either need more information, or for other common cases.

Feel encouraged to edit/enhance to share knowledge here! -[[User:Andre]]

==Generic==

===Report too vague===
Thanks for reporting this, but unfortunately this report is not very useful because it doesn't describe the issue well. If you have time and can still reproduce the problem, please read https://bugs.meego.com/page.cgi?id=bug-writing.html and http://wiki.meego.com/Quality/How_To_Report_Bugs and add a more useful description to this bug.

===Not a bug / ask in forum===
Please note that bugs.meego.com is not a support forum — it is a bug tracking system for software errors. Hence closing this report as INVALID.
For future reference, please ask support questions in the forum at http://forum.meego.com/ or on the community mailing list at http://meego.com/community/mailing-lists . Thanks!

===Duplicate===
Thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

===Obsolete version===
Thanks for reporting this!
Can you please test this again running the latest available release? The latest release should be available through the Software Update function.

===Please verify===
A future public update [...more version info here...] will include the fix.
Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Thanks in advance!

==Crashes==
===Coredump needed===
Please provide a coredump of the crash by using http://wiki.meego.com/Quality/bkm/corewatcher

===gdb===
If this is reproducible, can you please install gdb and debuginfo packages for the affected packages (e.g. for handset video issues the command would be "zypper install meego-handset-video-debuginfo" and make sure that enabled=1 is enabled for the relevant debuginfo repository in the file /etc/zypp/repo.d/), then open the terminal, enter "gdb command" (command is the package name), enter "run", make it crash, enter "thread apply all bt", enter "list", and provide the output of both here? Thanks in advance!

==dmesg==
Can you please post the output of the command "dmesg" as an attachment here (in case you are not a developer running some non-public prototype)?

==Application Freezes==
If this is reproducible, can you provide the output of "powertop -d" in the terminal when the application freezes?

==Connectivity==

===General connection problems===
Does the same result happen with the connman-test scripts?

=== Bluetooth not seen ===

What is the output of running "hciconfig" in the terminal?
If output is shown this should be a User Interface bug; If not, please also attach the output of "dmesg" here (in case you are not a developer running some non-public prototype).

===WiFi===

==== WiFi not seen ====

Can you please provide the output of "test-connman list" in the terminal?

===Mixed mode===

Maybe your router not implementing mixed mode properly.
Can you please on your MeeGo machine:

1) Open a terminal

2) kill connmand, kill wpa_supplicant

3) Edit a wpa_s.conf file with the following content:

network={
ssid="YOURSSID"
scan_ssid=1
key_mgmt=WPA-PSK
psk="YOURPASSPHRASE"
}

Where YOURSSID would be the SSID of the AP you're having trouble to join with
ConnMan.

4) Then run: sudo wpa_supplicant -Dwext -iwlan0 -dd -c wpa_s.conf > wpa_s.log

5) Wait for a minute or so, Ctrl-C and attach wpa_s.log to this bug report.

==Data==

===Tracker===
If music or video files are not displayed in the application, try running "tracker-search -v" in a terminal.

==Desktop==
===MyZone===
Please run "grep meego-panel-myzone /var/log/messages" (as root user) on a failed boot and provide the output here.

==Graphics==

===X===
If X fails to load please provide the content of /var/log/uxlaunch.log and ~/.xsession-errors

==Multimedia==

===PulseAudio log===
Please provide a Pulseaudio log by killing pulseaudio (TODO: how?) and then restarting it by running "pulseaudio -vvvv".

==Skype==
Skype is not a MeeGo.com component and is closed-source and non-redistributable, hence closing this report as INVALID.

== Communication ==

=== SIP ===

Please create a log as described at http://telepathy.freedesktop.org/wiki/Debugging . To include SIP messages in the log, please first export TPORT_LOG=1 in the environment where telepathy-sofiasip is launched (the console, otherwise this should be in the user session, or the environment of dbus-daemon for same).

=== Telephony ===

====D-Bus log====
Please try to collect session D-Bus logs by launching dbus-monitor in the user
shell:

dbus-monitor --session > dbus-session.log

===Problems with modem detection===
Can you please attach:

1) ofono logs for this issue:
In /etc/rc.sysinit, replace
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod
fi
with
if [ -x "/usr/sbin/ofonod" ] ; then
/usr/sbin/ofonod -d '*' -n > /tmp/ofono.log 2>&1
fi
After testing, please attach /tmp/ofono.log here.
2) Result of the command /usr/lib/ofono/test/list-modems entered in the terminal

3) lsof | grep libsm (you will have to install lsof using the command "zypper install lsof")

Also, setting OFONO_ISI_DEBUG=1 and OFONO_ISI_TRACE=1 in environment variable before might provide more info.
See the HACKING file of oFono for more info.

==== Dialer application call data issues ====
Please attach logs from ofonod and dialer:

In one terminal:
# sudo killall ofonod
# sudo ofonod -n -d "*"

In second terminal:
# dialer --output-level debug

Also please send the output of the "date" command around the time of the calls.

What locale are the device set to? Please attach the output of the following commands:
# locale
# gconftool-2 -R /meegotouch/i18n

==== Slow display of UI ====

If this is reproducible:
- How many contacts were in the system?
- How many seconds it took for sms to display?
- Did the time to display differ on subsequent invocations?
- If you erase all contacts (please have a backup), does SMS come up faster?

[[Category:QA]]

Quality/Error Management

2011-05-31T19:27:14Z

Andre: Fix the "Communication" section, add "Getting involved" section

Quality

2011-05-31T19:12:18Z

Andre: add link for Error Management (did not exist before though it is part of Quality)

Web infrastructure

2011-05-31T19:10:57Z

Andre: Fix redirect for EM link

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|OSU
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/qgil Quim Gil]
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|OSU
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.16.2
|OSU
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|OSU
|active
|[http://meego.com/users/ericlr Eric Le Roux] [http://meego.com/users/may May Xie]
|[[Quality/Error_Management|details]]
|-
|http://apidocs.meego.com
|Static HTML/files
|OSU
|active
|[http://meego.com/users/bspencer Bob Spencer]
|[[SDK|details]]
|-
|http://lists.meego.com
|Mailman
|OSU
|active
|[http://meego.com/users/agretzinger Adam Gretzinger]
|[[Mailing list guidelines|details]]
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|[http://meego.com/users/reggie Reggie Suplido]
|[[Web_infrastructure/Forum|details]]
|-
|http://planet.meego.com
|Midgard
|OSU
|active
|[http://meego.com/users/bergie Henri Bergius]
|[[Web_infrastructure/Planet.meego.com|details]]
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|[http://download.meego.com download.meego.com]
|Generic Web Server, Serves Intermediate Builds
|OSU
|active
|[http://meego.com/users/agretzinger Adam Gretzinger]
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.pub.meego.com api.pub.meego.com
|Community OBS
|OSU servers
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|OSU
|active
|[http://meego.com/users/jennycao Jenny Cao]
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|-
|ots.meego.com
|http://gitorious.org/qa-tools/ots
|OSU
|Decomissioned
|
|[http://wiki.meego.com/Quality/QA-tools/OTS details]
|}

Main Page

2011-05-31T19:10:08Z

Andre: Remove explicit link to Error Management as it is a subtask of Quality/QA as per MeeGo's organizational structure

Error Management

2011-05-31T19:09:30Z

Andre: moved Error Management to Quality/Error Management: By MeeGo's organizational structure, EM is part of QA. Reflect this by moving it to a subpage of Quality/.

#REDIRECT [[Quality/Error Management]]

Quality/Error Management

2011-05-31T19:09:30Z

Andre: moved Error Management to Quality/Error Management: By MeeGo's organizational structure, EM is part of QA. Reflect this by moving it to a subpage of Quality/.

MeeGo Error Management (EM) defines the handling of errors in MeeGo and maintains [https://bugs.meego.com MeeGo Bugzilla]. Error Management is part of [[Quality|QA]].

== Team ==

* '''[http://meego.com/users/ericlr Eric Le Roux]''', Nokia Error Management Lead
* '''[http://meego.com/users/wanshuang Shuang Wan]''', Intel
* '''[http://meego.com/users/iekku Iekku Huttunen]''', Ixonos
* '''[http://meego.com/users/andre Andre Klapper]''', Openismus

== Communication ==

* TODO: Add mailing list or contact information here.

== Tools ==

== Process ==

* [[Quality/Meetings|Meetings]]
* Issues can be filed via bug reports in MeeGo Bugzilla against [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com MeeGo Bugzilla] itself or against [https://bugs.meego.com/enter_bug.cgi?product=Community%20processes Community processes].
* The current EM process is documented here: [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Handling]]

== Other Documentation ==

* [[MeeGoBugzilla_Customization|MeeGo Bugzilla Customization]]
* See [[Quality]] section for further Bugzilla process related information

[[Category:QA]]

Quality

2011-05-31T19:08:36Z

Andre: Fix the three mentions of meetings on this wikipage

Quality/UpstreamBugTrackers

2011-05-31T18:15:18Z

Andre: add sudo

== Practice ==

If a bug in code or in translations exists that comes from an "upstream" project and that was not changed in ("downstream") MeeGo it is common practice to forward this bug report to the corresponding upstream bugtracker.

This makes upstream developers / translators become aware of issues (that were found in MeeGo but affect any other downstream projects too) so they can get fixed upstream. Patches are of course also welcome to be attached in an upstream report.

Fixing issues upstream reduces the efforts of maintaining downstream patches. It is welcome to query first in the upstream bugtracker for a potentially already existing report covering the issue.

In case an upstream bug has been filed or has been found, add the URL to the field "See Also: Add Bug URLs:" in the report in bugs.meego.com, and vice versa if possible. CC yourself to the upstream bug report to keep track and update the report in bugs.meego.com once it is fixed upstream.

== Mapping ==
{| border="1" + Upstream Bug Trackers
!rowspan="2"|MeeGo Components
!colspan="3"|Upstream
|-
! Project
! Bugtracker URL
! Product for Translation Issues
|-
| Alsa
| Alsa
| https://bugtrack.alsa-project.org/alsa-bug/
|
|-
| Cairo, Exempi, Xorg
| FreeDesktop.org
| https://bugs.freedesktop.org/
|
|-
| Giflib
| Giflib
| http://sourceforge.net/tracker/?group_id=102202
|
|-
| Banshee, librest, libsocialweb
| Gnome
| https://bugzilla.gnome.org/
| L10N
|-
| Icu
| Icu
| http://bugs.icu-project.org
|
|-
| KDE
| KDE
| https://bugs.kde.org/
| i18n
|-
| Fennec
| Mozilla
| https://bugzilla.mozilla.org/
|
|-
| Iptables
| Netfilter/Iptables
| http://bugzilla.netfilter.org/
|
|-
| ntp
| ntp
| http://bugs.ntp.org/
|
|-
| PulseAudio
| PulseAudio
| http://pulseaudio.org/report
|
|-
| Qt
| Qt
| http://bugreports.qt.nokia.com
|
|-
| sudo
| sudo
| http://www.sudo.ws/bugs/
|
|-
| SWI-Prolog
| SWI-Prolog
| http://www.swi-prolog.org/bugzilla/
|
|-
| WebKit, WebCore, CoreJS
| WebKit
| https://bugs.webkit.org/
|
|}

If the component you're looking for isn't listed here, please add it, possible places to find further bug trackers include:
* Ubuntu: https://launchpad.net/bugs/bugtrackers/
* Gnome: http://live.gnome.org/Bugsquad/TriageGuide/NonGnome

== Other bug trackers ==

Bugtrackers for components related to MeeGo but not part of MeeGo.

{| border="1" + Other Bug Trackers
! Project
! Bugtracker URL
|-
| Peregrine
| http://bugs.peregrine-communicator.org/
|}

[[Category:QA]]