On 30/06/2008, at 1:52 AM, Per Eriksson wrote:
Hello Clytie, > So, if any member of this QA team wants to be able to confirm issues > [1], s/he only needs to request that right here. Normally, we will> only grant that right once you have gained some experience in testing> bugs and have a reasonable understanding of the OpenOffice.org QA > process. So, start testing issues! :)Is the text that you attached at the bottom easily available for normal users? I haven't been able to find it, and think it would be very usable for a lot of new users. Maybe on the left panel that are available for all projects, maybe on the qa.openoffice.org "website".Thanks for the well written instructions.
My pleasure. The QA project is welcome to reuse that text on the webpage or in the wiki. I'm sure we already have detailed info on the Issue Tracker, but maybe we also need an introduction that summarizes what a new QA member needs to know. I'd be happy to write such a wiki page, if that suits the QA project, and someone with access to the website CVS could add a link to that wiki page. (New to Issue Tracker?)
Ah: I have found a page with similar information: http://www.openoffice.org/scdocs/issue_lifecycle.htmlIt's in the Issue Tracker Help. I would suggest changing its title to "Issue Status", because that is easier for speakers of other languages to understand. Perhaps also add a Help button (quesion mark) to the New Issue form?
There seem to be quite a few pages on the Issue Tracker or the QA project. I don't know if we need another page (an introductory page, written specifically for newer members), or whether we need to collect all these links somewhere.
What do you think? from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
PGP.sig
Description: This is a digitally signed message part
