Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On Fri, Oct 19, 2012 at 7:54 AM, Tom Davies <tomdavies04@yahoo.co.uk> wrote:

Hi :)
Ahhh, now i understand what QA is.  I think other projects call it
different things such as the Triage Team and stuff like that.  I think a
few people on this list could almost definitely help and maybe we could
help push people in that direction.


+1. We do more than just confirming bugs in QA but it is a big part of what
we do.


A few people have asked about how to become a dev and i usually point them
to just the Easy Hacks but QA is a good way of getting hands-on quickly
without actually having to instantly learn coding.  You clearly build-up a
better understanding of the infrastructure used by LO devs and perhaps it
helps you as you are learning coding by giving you examples of where it's
most needed.  Right, next time i will point people towards QA.


+1 please do, you can have them even email me directly as I coordinate a
lot of that stuff.


Regards,
Joel

-- 
*Joel Madero*
LibO QA Volunteer
jmadero.dev@gmail.com

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
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/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.