MeeGo wiki - User contributions [en]

SDK/QA

2011-03-21T17:17:26Z

Arcadie: /* Team */

= MeeGo SDK QA Team =

The MeeGo SDK QA Team is responsible of MeeGo platform SDK Quality. QA members focus on different components, host and target platforms, but we maintain all the test cases in the same testlink website, file bugs to MeeGo bugzilla SDK project, post testing report to MeeGo quality WiKi page. The synchronization among QA members is ensured by weekly SDK QA meeting, IRC and mail.

== Team ==

* Jaya Uppalapati -- QA leader, focus on Nokia legacy components, ARM based platform and features
* Juha Peisanen -- QA owner, focus on Nokia legacy components, ARM based platform and features
* Arcadie Prepelita -- QA owner, focus on X86 based platform and features
* Ionut Gavaz -- QA leader focus on X86 based platform and features

== Process ==

===Bug Triage===

For bug triage process of MeeGo, please refer to [[Quality/Bugtriage]]. SDK team members should register bug triage mailing list: meego-bug-triage@linux.intel.com. Register @ http://linux.intel.com/mailman/listinfo/meego-bug-triage.

Teams for bug triage:
* Bug triage team: Juha Peisanen (Nokia) Daniel Mihai (Intel), Fathi Boudra(Nokia), Jackie Wu(Intel), Max Yu (Intel)
* Bug management team: Veli Kaksonen (Nokia), Bob Spencer(Intel), Kerry Jiang (Intel), Arcadie Prepelita(Intel)

Bug triage process:
* Bug triage team review all the new bugs for the priority, severity, assignee and description every week.
* After review, bug triage team send out the review request to "bug triage mailing list" every Monday and request management team provide feedback on bugs
* Management team review the bugs in '''1 business day''' and decide if accept these new bugs. Bug owners should accept the bugs for her/him in '''1 business day'''. Anyone in triage mailing list can speak out with your opinion for any bug. If a bug is accepted, the bug status should be changed to "ASSIGNED" and right "target build" is set by bug owner.
* If there are controversial bugs, Management Team should drive to go through them in next sync meeting and make decision in the meeting.

===Bugzilla workflow===

The default assignee of a newly introduced bug must set the bug to ASSIGNED in '''1 business day''' if she/he is not on leave. In case he is not the one to solve the bug, he must pass the bug to another person leaving the status unchanged in '''1 business day''' if she/he is not on leave.

Developer needs to set bug to ASSIGNED even if he won't start working at the bug right away. The ASSIGNED state is just an indication that the bug has reached the person/persons that should take care and fix it; bugs should have a short life in the NEW state.
In case a bug remains in NEW state for longer than '''1 week''', QA must take action to search and notice the right persons; maybe the bug was misplaced?
The recommended way of asking for describing anything that is related with the bug is by commenting in bugzilla rather than email or chat; this way other people can see all information related to the problem in one place

One unwanted situation is when bugs are in NEW and nobody has ever commented on it for a long time. Feedback is important to the QA, even for INVALID or DUPLICATE bugs in order to improve the QA process for the future and to help any other viewer that might run into the same bug later.
Another situation to be avoided is when developer works on fixing bugs based on his own preferences, for instance avoid writing for bugs for documentation. This will contribute to an overall reduced quality process.

Once the release is about to take place the QA should release an acceptance document enlisting the last versions of the builds tested, overall status of the product (GREEN/YELLOW/RED) and some of the major bugs. RED should mean that the build is not ready for release from QA POV.

== Test Plan ==
You can find uniform MeeGo SDK test plan @ [[SDKTestPlan|SDK Test Plan]]

== Test Report ==
*[http://qa-reports.meego.com/ MeeGo SDK Test Reports]

== Meeting ==
* When: Every Tuesday at 11:00~12:00 (UTC+2).
* Sharing point during the meeting: http://piratepad.net/MXIM107LUe

=== Meeting Minutes ===
*[[SDK/QA/MeetingMinutes/20110315|20110315 Meeting Minutes]]
* 20110308 Meeting Cancelled due to vacations
*[[SDK/QA/MeetingMinutes/20110301|20110301 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101109|20101109 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101102|20101102 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101026|20101026 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101019|20101019 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101012|20101012 Meeting Minutes]]
* 20101005 Meeting Cancelled due to vacations
*[[SDK/QA/MeetingMinutes/20100928|20100928 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20100921|20100921 Meeting Minutes]]

SDK

2011-03-21T17:15:25Z

Arcadie: /* Domains */

= MeeGo SDK =

This is the entry page of MeeGo SDK. From here you can find info about using MeeGo SDK and about SDK development.

== Using the SDK ==

* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux]] - Main page pointed from http://meego.com/developers
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Windows]]
* [[SDK/Docs/1.1]] - For more information about MeeGo SDK 1.1 (beta)
* [[SDK/Testing]] - Instruction on how to install and test the weekly release. NOTE: weekly releases can be totally broken. Use stable unless you know what you are doing.

== Contribute ==

MeeGo SDK work and the team can be found here:
* '''IRC''': #meego-sdk on Freenode. [http://trac.tspre.org/merbot/freenode/%23meego-sdk/ Logs.]
* '''Mailing list''': [http://lists.meego.com/listinfo/meego-sdk MeeGo-SDK].
* '''Submit Features''': [https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20SDK%20features SDK Feature Request]

Visit the [http://wiki.meego.com/Mailing_list_guidelines mailing guidelines page] for more details about participating on MeeGo mailing lists and IRC channels.

== SDK Development ==

SDK development is done by the MeeGo.com SDK Program under MeeGo Program Office. MeeGo SDK team consists of team members from various companies involved in MeeGo. The goal is to create one SDK suitable for all the official MeeGo verticals. SDK also needs to be extend-able with plugins for more specific needs.

* [[SDK/Road_to_1.1]]
* [[SDK/Road_to_1.2]]

=== SDK Program Organization ===

==== Management ====

* [http://meego.com/users/veli Veli Kaksonen] - Program Manager
* Ville Lavonius - Product Manager
* [http://meego.com/users/bspencer Bob Spencer] - Architect
* Kerry Jiang - Engineering Manager / China

==== Domains ====

* [[SDK/Architecture]] - [http://meego.com/users/bspencer Bob Spencer] - Architecture Team Lead
** [http://meego.com/users/fabo Fathi Boudra]
** [http://meego.com/users/wwhbuaa Jackie Wu]
** [http://meego.com/users/mauricek Maurice Kalinowski]

* [[SDK/API]] - N/A - API Team Lead

* [[SDK/Release]] - [http://meego.com/users/fabo Fathi Boudra] - Release Team Lead
** [http://meego.com/users/wwhbuaa Jackie Wu]

* [[SDK/Windows]] - [http://wiki.meego.com/User:Maxayu Max A Yu] - Windows Port Lead

* [[SDK/MacOSX]] - N/A - Mac OS X Port Lead

* [[SDK/QA]] - Jaya Uppalapati - QA Team Lead
** Juha Peisanen
** Arcadie Prepelita
** Ionut Gavaz
** Laura Piekkola

* [[SDK/Documentation]] - Taru Laine - Documentation Team Lead
** Elliot Smith
** Ronan MacLaverty
** Murali Punaganti
** Bob Spencer

==== Subsystems ====

* [[SDK/Installer]] - N/A - Installer Team Lead
** N/A

* [[SDK/QtCreator]] - [http://meego.com/users/mauricek Maurice Kalinowski] - Qt SDK responsible
** [http://meego.com/users/johnchen Zhang Chen]

* [[SDK/Toolchains]] - [http://meego.com/users/kaltsi Juha Kallioinen] - Toolchain Team Lead
** Al Nikolov - ARM
** Xu U Zhang - Intel

* [[SDK/MADDE]] - Jari Ihatsu - MADDE Subsystem Maintainer / Team Lead
** [http://meego.com/users/too Tomi Ollila]
** Wang Wenchao

* [[SDK/Qemu]] - [http://meego.com/users/suihkulokki Riku Voipio] - Qemu Subsystem Maintainer / Team Lead
** [http://meego.com/users/zhiyuan Zhiyuan Lv]
** Juha Riihimäki
** [http://meego.com/users/haitao Haitao Feng]
** [http://meego.com/users/juntian Jun Tian]

=== Meetings ===

* [[SDK/Meetings]] - Meetings - agenda, minutes

=== Proposals & Studies ===

Proposals & Studies about MeeGo SDK. Feel free to write one.. :)

==== Active ====

* [[SDK/Bugzilla_Components]] - List of products and components in Bugzilla
* [[SDK/Two_weeks_delay_proposal]] - Proposal about two weeks delay in releasing SDK after MeeGo release
* [[SDK/Installers_study]] - Pros and cons about different installing possibilities
* [[SDK/Installation_Proposal]] -- Proposal for discussion on MeeGo SDK installation (Bob)
* [[SDK/Team_Proposal]] - SDK team, members, roles, responsibilities
* [[SDK/Managing_MADDE_Components_proposal]] - Proposal on how to add/remove/update madde components.
* [[SDK/Packaging_proposal]] - Proposal on how to package MeeGo application for deployment and uploading to App stores.
* [[SDK/Packages_group]] - Proposal for packages group
* [[SDK/Sysroot_extension]] - Proposal on how to extend sysroot by adding additional libraries

==== Closed ====

* -

== Misc material not yet in right place ==

Let's gather here links to all the documents we have. Then later we can review those and move those under /SDK/.

* [[SDK/MeeGo_1.1_Application_SDK_Project_Plan]] - (work in progress)
* [[SDK/Release_Tasks]]
* [[SDK/MADDE_distfiles]]
* [[SDK/Comparison]]
* [[SDK/Road_to_1.1.2]]
* [[SDK/Tutorials]]

SDK/QA/MeetingMinutes/20110315

2011-03-21T17:12:16Z

Arcadie: Created page with "* Attendees: Arcadie, Juha, AlexG,Andreea *Agenda: **Review of last week activities and APs **Continue with feature verification - use google spreadsheet as refference and focus …"

* Attendees: Arcadie, Juha, AlexG,Andreea
*Agenda:
**Review of last week activities and APs
**Continue with feature verification - use google spreadsheet as refference and focus on features that have the same state in both spreadsheet and featurezilla.

SDK/QA

2011-03-21T17:10:22Z

Arcadie: /* Meeting Minutes */

= MeeGo SDK QA Team =

The MeeGo SDK QA Team is responsible of MeeGo platform SDK Quality. QA members focus on different components, host and target platforms, but we maintain all the test cases in the same testlink website, file bugs to MeeGo bugzilla SDK project, post testing report to MeeGo quality WiKi page. The synchronization among QA members is ensured by weekly SDK QA meeting, IRC and mail.

== Team ==

* Jaya Uppalapati -- QA leader, focus on Nokia legacy components, ARM based platform and features
* Juha Peisanen -- QA owner, focus on Nokia legacy components, ARM based platform and features
* Arcadie Prepelita -- QA owner, focus on X86 based platform and features
* Daniel Mihai -- QA leader focus on X86 based platform and features

== Process ==

===Bug Triage===

For bug triage process of MeeGo, please refer to [[Quality/Bugtriage]]. SDK team members should register bug triage mailing list: meego-bug-triage@linux.intel.com. Register @ http://linux.intel.com/mailman/listinfo/meego-bug-triage.

Teams for bug triage:
* Bug triage team: Juha Peisanen (Nokia) Daniel Mihai (Intel), Fathi Boudra(Nokia), Jackie Wu(Intel), Max Yu (Intel)
* Bug management team: Veli Kaksonen (Nokia), Bob Spencer(Intel), Kerry Jiang (Intel), Arcadie Prepelita(Intel)

Bug triage process:
* Bug triage team review all the new bugs for the priority, severity, assignee and description every week.
* After review, bug triage team send out the review request to "bug triage mailing list" every Monday and request management team provide feedback on bugs
* Management team review the bugs in '''1 business day''' and decide if accept these new bugs. Bug owners should accept the bugs for her/him in '''1 business day'''. Anyone in triage mailing list can speak out with your opinion for any bug. If a bug is accepted, the bug status should be changed to "ASSIGNED" and right "target build" is set by bug owner.
* If there are controversial bugs, Management Team should drive to go through them in next sync meeting and make decision in the meeting.

===Bugzilla workflow===

The default assignee of a newly introduced bug must set the bug to ASSIGNED in '''1 business day''' if she/he is not on leave. In case he is not the one to solve the bug, he must pass the bug to another person leaving the status unchanged in '''1 business day''' if she/he is not on leave.

Developer needs to set bug to ASSIGNED even if he won't start working at the bug right away. The ASSIGNED state is just an indication that the bug has reached the person/persons that should take care and fix it; bugs should have a short life in the NEW state.
In case a bug remains in NEW state for longer than '''1 week''', QA must take action to search and notice the right persons; maybe the bug was misplaced?
The recommended way of asking for describing anything that is related with the bug is by commenting in bugzilla rather than email or chat; this way other people can see all information related to the problem in one place

One unwanted situation is when bugs are in NEW and nobody has ever commented on it for a long time. Feedback is important to the QA, even for INVALID or DUPLICATE bugs in order to improve the QA process for the future and to help any other viewer that might run into the same bug later.
Another situation to be avoided is when developer works on fixing bugs based on his own preferences, for instance avoid writing for bugs for documentation. This will contribute to an overall reduced quality process.

Once the release is about to take place the QA should release an acceptance document enlisting the last versions of the builds tested, overall status of the product (GREEN/YELLOW/RED) and some of the major bugs. RED should mean that the build is not ready for release from QA POV.

== Test Plan ==
You can find uniform MeeGo SDK test plan @ [[SDKTestPlan|SDK Test Plan]]

== Test Report ==
*[http://qa-reports.meego.com/ MeeGo SDK Test Reports]

== Meeting ==
* When: Every Tuesday at 11:00~12:00 (UTC+2).
* Sharing point during the meeting: http://piratepad.net/MXIM107LUe

=== Meeting Minutes ===
*[[SDK/QA/MeetingMinutes/20110315|20110315 Meeting Minutes]]
* 20110308 Meeting Cancelled due to vacations
*[[SDK/QA/MeetingMinutes/20110301|20110301 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101109|20101109 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101102|20101102 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101026|20101026 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101019|20101019 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20101012|20101012 Meeting Minutes]]
* 20101005 Meeting Cancelled due to vacations
*[[SDK/QA/MeetingMinutes/20100928|20100928 Meeting Minutes]]
*[[SDK/QA/MeetingMinutes/20100921|20100921 Meeting Minutes]]

SDK/QA

2011-03-01T17:37:52Z

Arcadie: /* Team */

SDK/Meetings

2011-03-01T17:37:03Z

Arcadie: /* QA */

= MeeGo SDK Meetings =

This page lists the MeeGo SDK Team meetings, agendas and minutes of different team / groups.

* [http://www.timeanddate.com/worldclock/meetingtime.html?pa=438&pa=33&pa=37&pa=101&pa=136&pa=202 World clock] for meeting planning and local times.

== MeeGo SDK Team ==

Common meetings for wider audience. Weekly status of all the subteams and common workshops.

=== Weekly meeting ===

[[SDK/Meetings/SDK_Weekly]] - MeeGo SDK Team weekly meeting - every Wednesday at 5:30 GMT. Duration 1 hour.

* [[SDK/Meetings/20110223_Weekly]]
* [[SDK/Meetings/20110216_Weekly]]
* [[SDK/Meetings/20110209_Weekly]]
* [[SDK/Meetings/20110126_Weekly]]
* [[SDK/Meetings/20110119_Weekly]]
* [[SDK/Meetings/20110112_Weekly]]
* [[SDK/Meetings/20110105_Weekly]]
* [[SDK/Meetings/20101222_Weekly]]
* [[SDK/Meetings/20101215_Weekly]]
* [[SDK/Meetings/20101208_Weekly]]
* [[SDK/Meetings/20101201_Weekly]]
* [[SDK/Meetings/20101103_Weekly]]
* [[SDK/Meetings/20101027_Weekly]]
* [[SDK/Meetings/20101020_Weekly]]
* [[SDK/Meetings/20101006_Weekly]]
* [[SDK/Meetings/20100929_Weekly]]
* [[SDK/Meetings/20100922_Weekly]]
* [[SDK/Meetings/20100915_Weekly]]
* [[SDK/Meetings/20100908_Weekly]]
* [[SDK/Meetings/20100901_Weekly]]
* [[SDK/Meetings/20100825_Weekly]]
* [[SDK/Meetings/20100820_Extra]]
* [[SDK/Meetings/20100818_Weekly]]
* [[SDK/Meetings/1st_Kickoff_Meeting_Agenda]] - 20100812

=== Workshops ===

* [[SDK/Meetings/20100216-18_F2F_Helsinki]] - Face-to-face in Helsinki
* [[SDK/Meetings/20100128_Feature_workshop]] - Telco about Features
* [[SDK/Meetings/Jan_2011_F2F_Helsinki]] - From 20110126 to 20110128 in Helsinki - CANCELLED
* [[SDK/Meetings/1st_SDK_Team_F2F_Workshop]] - On 20101117 in Dublin -- [[SDK/Meetings/1st_SDK_Team_F2F_Workshop_minutes|Minutes]]
* [[SDK/Meetings/Road_to_1.1_Workshop]] - On 20101013 - 20101014

== Sub-team meetings ==

=== MeeGo Chat ===

[[SDK/Meetings/Chat]] - MeeGo SDK Management Chat (weekly) meeting information

* [[SDK/Meetings/20101005_Chat]]
* [[SDK/Meetings/20100928_Chat]]
* [[SDK/Meetings/1st_chat]]

=== Architecture ===

[[SDK/Architecture]] - MeeGo SDK Architecture Team meeting information. Includes past meeting summaries and future topics.

=== Documentation ===

[[SDK/Meetings/DocumentationTeam]] - MeeGo SDK Documentation Team meeting information

==== Weekly meetings ====
* [[SDK/Documentation/MeetingMinutes/20110127]]
* [[SDK/Documentation/MeetingMinutes/20110120]]
* [[SDK/Documentation/MeetingMinutes/20110112]]
* [[SDK/Documentation/MeetingMinutes/20101012]]
* [[SDK/Documentation/MeetingMinutes/20101005]]
* [[SDK/Meetings/1st_Documentation]]

=== Toolchains ===

[[SDK/Toolchains/Meetings]] - MeeGo Toolchains Team meeting info

* [[SDK/Toolchains/Meetings/Notes20110221]]
* [[SDK/Toolchains/Meetings/Notes20110131]]
* [[SDK/Toolchains/Meetings/Notes20110114]]
* [[SDK/Toolchains/Meetings/Notes20110105]]
* [[SDK/Toolchains/Meetings/Notes20101217]]
* [[SDK/Toolchains/Meetings/Notes20101119]]
* [[SDK/Toolchains/Meetings/Notes20101108]]
* [[SDK/Toolchains/Meetings/Notes20101022]]

=== Release ===

[[SDK/Meetings/Release]] - MeeGo SDK Release Team meeting info

* [[SDK/Meetings/Release/Agenda/20101130]]
* [[SDK/Meetings/Release/MeetingMinutes/20101130]]
* [[SDK/Meetings/Release/Agenda/20101207]]
* [[SDK/Meetings/Release/MeetingMinutes/20101207]]
* [[SDK/Meetings/Release/Agenda/20101214]]
* [[SDK/Meetings/Release/MeetingMinutes/20101214]]
* [[SDK/Meetings/Release/Agenda/20101221]]
* [[SDK/Meetings/Release/MeetingMinutes/20101221]]
* [[SDK/Meetings/Release/Agenda/20101228]]
* [[SDK/Meetings/Release/MeetingMinutes/20101228]]
* [[SDK/Meetings/Release/Agenda/20110104]]
* [[SDK/Meetings/Release/MeetingMinutes/20110104]]
* [[SDK/Meetings/Release/Agenda/20110111]]
* [[SDK/Meetings/Release/MeetingMinutes/20110111]]
* [[SDK/Meetings/Release/Agenda/20110118]]
* [[SDK/Meetings/Release/MeetingMinutes/20110118]]
* [[SDK/Meetings/Release/Agenda/20110125]]
* [[SDK/Meetings/Release/MeetingMinutes/20110125]]
* [[SDK/Meetings/Release/Agenda/20110222]]
* [[SDK/Meetings/Release/MeetingMinutes/20110222]]

=== API ===

[[SDK/Meetings/API]] - MeeGo API Team meeting info

* lorem ipsum

=== QA ===

[[http://wiki.meego.com/SDK/QA#Meeting QA Meetings]] : Every Tuesday at 11:00~12:00 (UTC+2).

SDK/QA

2011-03-01T17:31:29Z

Arcadie: /* Meeting */

SDK/QA/MeetingMinutes/20110301

2011-03-01T17:27:57Z

Arcadie: Created page with "*Attendees: Juha, Jaya, Daniel, Arcadie. *Agenda: ** Review proposal from Daniel on bug workflow http://wiki.meego.com/SDK/Bugzilla_Work_Flow *** AP1: Juha to provide bug/feature…"

*Attendees: Juha, Jaya, Daniel, Arcadie.
*Agenda:
** Review proposal from Daniel on bug workflow http://wiki.meego.com/SDK/Bugzilla_Work_Flow
*** AP1: Juha to provide bug/feature workflow flow pictures in wiki pages. We should see what we can reuse/update.
** Bugs/Features verified last week
*** AP2: Arcadie to send the updated xls file with the reviewed features and comments regarding test cases
** Test automation
*** No activity on test automation - top priority is creating cases for features.
** Next meeting attendees
*** Daniel Mihai will handover the QA Lead role to the new team member, Ionut Gavaz, that will join on March 15.
*** Arcadie will participate in these meetings at least until end of March.
*** Daniel and Arcadie will be OOO next week and not participate in this meeting. Viorel Mirea and Alexandru Georgescu will participate.

SDK/QA

2011-03-01T17:08:37Z

Arcadie: /* Meeting Minutes */