Re: [native-lang] Very Easy QA How To (WAS: writing an easy QA howto)

Hirano San,

what a beautiful Haiku! ;-)
I'll include it in the howto!


Kazunari Hirano a écrit :
> Hi Alexandoro and all,
> 
>> Here is a good parameter to write good documentation. If your kids
>> read it
>> and they don't understand, then  that means that your documentation still
>> need works to make it simpler.
> I agree :)
> But my daughter is 5 and she is not interested in OOo and QA ;)
> So I try to write "Very Easy QA How To" for my partner who occasinally
> uses OOo but knows nothing about QA.
> 
>> Another good parameter is having a '5 step program'
>> to get the process understood.
> Right!
> 
> 0. What is QA? QA is Quality Assurance.
>    What is Quality?  Quality product doesn't crash.
>    What is Assurance?  To make sure it doesn't crash.
>    How to QA?  Follow the following 5 steps:
> 
> 1. Subscribe releases/AT/openoffice.org and watch out its announcements.
> 2. When announced, find your localized snapshot build or release candidate.
> 3. Download and Install it onto your machine and start it.
>    Then you have done the first and the most important part of QA.
> 4. Tell your community QA lead what you have done and results.
> 5. If you can not find your QA lead, be QA lead yourself.
> 
> How to be QA lead?
>  Declare at your local mailing list and be accepted.
> What QA lead does?
>  Tell dev/AT/qa.openoffice.org that you are QA lead,
>  and ask many questions on the list,
>  and ask your community members for help.
> You want to do more?
>  Sure, there are TCM, TestTool, IssueTracker and various mailing
> lists you can contribute.
> What are these things?
>  Time-consuming things.  You need skill to do them.
>  You need to read a lot.  You need to ask a lot of questions.
> Are you still here? :)
> Good!
> Then let's get started.
> Quick!  Start asking Questions!
> 
> What is important, Communication :)
> 
> Thanks,
> khirano
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
>