Hi Clytie ^_______^ Thanks very much for your reply.Now,I've know what I should do with the Wiki and issues.
------------------ Vince Ji 2008-06-19 ------------------------------------------------------------- 发件人：Clytie Siddall 发送日期：2008-06-18 17:42:16 [EMAIL PROTECTED] 抄送： 主题：[qa-dev] Beginning_QA_(was:_Re:_[qa-dev]_Re￡oClytie_Siddall) Hi Ji Ming :) On 18/06/2008, at 2:36 PM, Vince wrote: > > I'm sorry to reply so late. The past few days, there has been a lot > of work to do. > I have read the wiki pages and then I found there are so many links. > I nearly don't know which I could read first. > And what can I do for the issues in the Tracker ? You don't have to read everything. Just start with the introductory pages, then, when you have more time, read one page at a time. It just helps to have some background knowledge of the project. What you can do for the Issue Tracker is to test issues. There is a very large number of unconfirmed issues. This means that someone has reported a problem, but nobody else has had time to check that it really happens. We don't even know how important it is. There is a long list of UNCONFIRMED issues for Calc. So you choose an issue, then try to repeat it in your latest copy of OpenOffice.org. Does it happen to you? Does anything else happen? Then you add this information to the issue. The person reporting the problem should describe the steps needed to reproduce it. You follow those steps, to test it. Then you report on what happened in your latest copy of OpenOffice.org, e.g. "Confimed in OpenOffice.org 3.0b Chinese." or "This doesn't happen in OpenOffice.org 3.0b Chinese. Function X works as expected." or "Slightly different in OpenOffice.org 3.0b Chinese. Function X works, but the results appear in the wrong cell." You add any information you get from testing the bug. Just confirming, or not confirming these issues is helpful the developers. Once you have processed some issues, you can request CANCONFIRM status: this gives you the right to mark an issue as CONFIRMED. But to start with, you would need someone from the QA project to review your first few issues. > > > A new-comer with poor English and not much confidence. Everybody has to start at the beginning, sometime. Just take one step at a time. Login to the Issue Tracker and read the information about how to report bugs. Then start looking at some Calc bugs. Find one that interests you, or one that looks simple to test, then test it. Write your results in the issue. Then look at another bug. Every bug confirmed is a help to us. Please feel free to questions here. We are all here to help each other. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
