Hi Joel, at this point I have some spare time so I can help out where
possible. I only really have knowledge on writer and calc which limits
my capabilities.
I had a look at 2 writer bugs which were not difficult to reproduce. I
created a bugzilla account so would it be a good idea to jump in and
comment?
Cheers
Tim
On 03/02/2013 04:18 AM, Joel Madero wrote:
Hi All,
This is an invite for anyone who has just a little time to join the QA team
in triaging bugs. Our team is quickly growing but the ratio of users to QA
contributors is still not functional as we are having a hard time keeping
up with organizing bugs. The tasks are quite easy and someone from our team
is almost always available to help new contributors "master the skills"
needed to successfully triage bugs.
If you are interested and have just a few minutes (honestly some bugs take
<5 minutes to triage) please consider joining.
https://wiki.documentfoundation.org/QA/BugTriage
and our friendly team is available on freenode at:
http://webchat.freenode.net/?channels=libreoffice-qa
Hope to see some of you around.
Best,
Joel
--
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.