On Mon, Aug 16, 2010 at 1:59 PM, Steven Shelton <[email protected]> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 8/16/2010 2:53 PM, Alexandro Colorado wrote:> Why don't you try to
> re-write it on a more comprehensive post, once we
>>> have a template, we could submit it for review, and eventually
>>> replaced. Then again, I am not the responsible for the qa
>>> project. I will suggest you address the [email protected] and
>>> Joost (the project lead). I think he will agree if he sees an
>>> improved document.
>
>
> I would absolutely do that . . . but as I said, I don't understand it
> most of it myself. Makes it hard for me to explain to someone else.
>
> :-)
Well, let's see, beside the internal lingo of the apps what exactly is
confusing to you?
Supporting the Quality Assurance of OpenOffice.org is graduated in 3
Participation Steps
1. The first participation step (""Report bugs") is meant for
newbies to acquire general knowledge about issues in common.
Participants on the first stage are able to find and write issues
themselves. The link holds all the information you need to know for
starting to contribute.
/me I guess the explanation is too narrow, but it does explain that is
the first step of the QA process and holds the information that
developer needs to work with it.
2. The second step ("Manual testing") is meant for participants
with more skills. You are able to do manual testing on your own. You
can execute and write Test-Case-Specifications (TCS) and submit issues
found when dealing with Test-Case-Specifications.
The page contains all information needed to contribute to the
second participation step.
/me Actually I would argue with this, because using OOo is easier than
understanding bugzilla system. It relies on different knowledge, a
more practical one under the use of the application and following
instructions. This is on an app called TCM located here
http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_index.cgi?tcm_config=newooo
3. In the third participation step ("Join QA") you can apply to
join the QA Team of OOo at one of the "OOoQA-Teamleads". You have now
collected enough knowledge about issue handling to confirm issues and
close them by yourself. Having reached this stage of participation
brings a lot of advantages: you have direct contact to the
StarOffice/Openoffice.org developers and Quality Assurance engineers,
you will get listed as a direct member of the OpenOffice.org Quality
Assurance Team, you will be able to send own issue right to the
responsible engineer, you get direct responsibility, more rights (like
"canconfirm") and more weight in decisions.
>
> - --
> Steven Shelton
> Twilight Media & Design, LLC
> 17195 Silver Parkway
> #134
> Fenton, MI 48430
> www.TwilightMD.com
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iD8DBQFMaYqNKP0FWmSVanERAvDlAKDMmPC9Jmq/hq1j82F6nsmkKhKDDACfaX8i
> v/NBM4rUGr5SsH/2PR2iRR8=
> =0xdx
> -----END PGP SIGNATURE-----
>
>
--
Alexandro Colorado
OpenOffice.org Español
http://es.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
