Hi :) This message got through to me personally rather than to a mailing list so i have forwarded it to the Documentation Team as they are most likely to be able to help make the page more consistent with documentation. I'm sure there is a proper place for these things to go but i don't know where that would be. Definitely not to individuals jic they are not around or unable to help for however long.
My only comment about the changes below is that i prefer "non-developers" with a hyphen in the middle rather than just a gap/space. Apart from that it looked fine to me. Regards from Tom :) >________________________________ > From: "[email protected]" <[email protected]> >To: [email protected] >Sent: Friday, 8 March 2013, 12:47 >Subject: CMS Workflow: LibreOffice - Page: QA Testers - Status: Čeká na >schválení > > > >Ahoj Davies, Tom, > >Mladek, Petr has made changes to QA Testers and has requested approval. >Comment >The last version adds link to the QA mailing list which is what we want :-) >Last Edited >2012-08-16 12:52:24 2013-03-01 15:35:52 >Obsah >If you're interested in Quality Assurance work for LibreOffice, we're keen to >welcome new testers. >Primary points of contact and resources: the #libreoffice and #libreoffice-qa > channels at irc.freenode.net , the QA wiki page , the bug triage wiki page >, the qa mailing list at FreeDesktop.org developers mailing list at >FreeDesktop.org , and the pre-release download page . >You can easily help out: download and install LibreOffice Beta versions and Release Candidates for testing and trial use. >We aim to bring our users high-quality software. A great deal of work goes into coding and development. But when that work is finished, it needs to be tested and validated. That's the job of Quality Assurance [QA]. To do quality assurance, you don't necessarily need previous experience. You can easily contribute to it as an end user. >Quality assurance involves the following: > * Bug triage : you can take part in the triage and confirmation of > bugs having been reported on the LibreOffice bug tracker . To start doing so, create an account on the bug tracker and then follow the instructions on our wiki page . > * Manual Testing : You can help with regular regression tests . Just > choose a test cases in Litmus and follow instructions. If you miss an useful check, go and add it . Finally, you could help stabilizing new features . Just take one, play with it, and report problems. > * Automatic Testing : It might be an interesting introduction into the LibreOffice development if you write your own automatic check . Even non developers could provide test documents for some special tests . > * Localization QA : The internationalization of LibreOffice requires additional quality assurance (to check date and time handling, complex scripts, etc.), to ensure that we provide LibreOffice users with top-grade software in their language. To get involved in this QA, join the corresponding language group's mailing list (see our local mailing list index ). >Quality assurance requires patience and attention to detail, but it's >essential work. Even if you don't have time to contribute on a regular basis, it's a valuable boost to the project and community if you take time to report bugs and failures you encounter in your everyday use of LibreOffice. >To report bugs please do the following: > * Account Log-in: If this is the first time you report a bug to us, create an account for yourself OR log in to your account on our bug submission page . > * Bug Description: Use the "bug submission assistant" to describe the > bug in detail. ( Please note: at the " Choose a Subcomponent " step, you > will be presented with a list of existing bug reports; please browse through the list to make sure that your bug report is unique. If your bug report is unique, complete and submit the report and log-out OR if you find that your bug has already been submitted by someone else, click on that link and add your comment to that bug.) > * Account Log-out OR Abandon Submission: To abandon the bug submission, browse to any other page on the LibreOffice website. >Please rest assured that every bug report is examined and followed up. Your >contributions to our community project are most appreciated. >Status >Saved (update) Published >Save Count >21 20 >Last Edited By ID >293 87 >Actions > * View this page in the CMS to action the request > * Náhled této stránky na webu >Děkuji. > > -- Unsubscribe instructions: E-mail to [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
