m (moved Quality/meetings/QANominations101201 to Quality/Meetings/QA nominations 101201: Fixed the name according to the wiki guidelines) |
m (→Error Management / Eric Le-Roux) |
||
| Line 13: | Line 13: | ||
== Error Management / Eric Le-Roux == | == Error Management / Eric Le-Roux == | ||
| - | We have not had public nomination for Error Management in MeeGo. MeeGo Error Manager is responsible for MeeGo Bugzilla tool, processes and error metrix for all MeeGo releases and verticals. ''Eric Le-Roux'' has been acting in this role from the very beginning of MeeGo. | + | ''We have not had public nomination for Error Management in MeeGo.'' |
| + | The public announcement of Eric Le Roux as MeeGo EM Lead occurred on September 15th 2010, see below: | ||
| + | http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-15-19.01.html | ||
| + | MeeGo Error Manager is responsible for MeeGo Bugzilla tool, processes and error metrix for all MeeGo releases and verticals. ''Eric Le-Roux'' has been acting in this role from the very beginning of MeeGo. | ||
== QA Tools / Ville Ilvonen == | == QA Tools / Ville Ilvonen == | ||
QA Tools lead is responsible for leading MeeGo QA Tools team. In practice QA Tools leader is responsible for running QA Tools development projects form Feature definitions to delivery of the tools. Ville is the most active contributor in this area in MeeGo. Investment that we put to tools is enormous and this in main enabler for quality code done already by developers. In practice he is running this activity as we speak in public already. | QA Tools lead is responsible for leading MeeGo QA Tools team. In practice QA Tools leader is responsible for running QA Tools development projects form Feature definitions to delivery of the tools. Ville is the most active contributor in this area in MeeGo. Investment that we put to tools is enormous and this in main enabler for quality code done already by developers. In practice he is running this activity as we speak in public already. | ||
Contents |
These proposals are on the agenda on 1st of Dec 2010.
Tommi Toropainen has been nominated earlier in TSG for Core QA Lead. Tommi has been doing that as a part of his Nokia Job Profile. We would like to strengthen this by proposing to TSG that they would nominate Niko Rantalainen to this Core QA Lead position. Niko is the main contributor in this Core QA project from Nokia side. He has been working with Tommi from the beginning of MeeGo Core 1.1. He is active contributor in this area.
We have not had any public nomination for Netbook UX QA Lead position. Ling Yu is the person who has been running this in practice from the 1.0 onwards already. I would like to make his position nominated. Netbook QA Lead is operationally responsible (Planning, guiding and reporting maturity to Netbook Program) for ensuring that all the needed QA activities are done for Netbook UX in all MeeGo versions.
We have not had any public nomination for IVI UX QA Lead position. Jerry Yu is the person who has been running this in practice. I would like to make his position nominated. IVI UX QA Lead is operationally responsible (Planning, guiding and reporting maturity to IVI UX Program) for ensuring that all the needed QA activities are done for IVI UX in all MeeGo versions.
We have not had public nomination for Error Management in MeeGo. The public announcement of Eric Le Roux as MeeGo EM Lead occurred on September 15th 2010, see below: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-15-19.01.html
MeeGo Error Manager is responsible for MeeGo Bugzilla tool, processes and error metrix for all MeeGo releases and verticals. Eric Le-Roux has been acting in this role from the very beginning of MeeGo.
QA Tools lead is responsible for leading MeeGo QA Tools team. In practice QA Tools leader is responsible for running QA Tools development projects form Feature definitions to delivery of the tools. Ville is the most active contributor in this area in MeeGo. Investment that we put to tools is enormous and this in main enabler for quality code done already by developers. In practice he is running this activity as we speak in public already.