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

Hi :)
I thought this worth flagging up again.  If you want to join in (or if you might have a little free 
time) between midnight (UTC) Thursday 20th June and 1 minute before midnight (UTC again) on Friday 
5th July then it might be good to sign-up now and get in a little practice at triaging.  

You don't need to be a dev or have any coding skills.  Even if you do have such skills it's 
probably fastest to pick a type of task and then race through tons of bug-reports doing just that 
and then maybe pick another task on the list that you might be able to do and race through again.  
Other times it might be good to have a small checklist of things you can do and kinda race through 
doing those few things.  I tend to find the 1st method faster because the 2nd one tends to lead me 
into getting distracted or bogged-down in 1 tricky case.  

Useful tasks you can do without any coding skills whatsoever

2.  Search for Duplicates of Bug(s)

3.  Check Information Provided in Bug Report

4.  Attempt to Reproduce Bug

5.  Set Bug Status
Obviously 4&5 go together and are likely to take quite a long time (but it's where you learn most). 
 2 & 3 can be done independently of each other.  It's probably best to make sure 2 has been done 
before attempting 3 though.  I'd probably do 10 just doing step 2 and then go back over any left of 
that 10 to do step 3 and then find another 10 bug reports

Step 2 looks like it's just a case of checking they have given the info asked for on the bug-report 
wiki and then copy&paste the specific instruction from the bug-report page to try to help them (or 
remind them) to get the extra info

Of course another way of handling this is to pick issues you have been fretting about for years and 
see if you can process them further to make sure 'your' bug-reports  are complete and linked to 
duplicates, definitely reproducible in different versions and report back on which versions seem to 
have the problem and which don't.  ie a much more thorough job, aiming at "quality not quantity"

Regards from 

Tom :)  

From: Joel Madero <>
To: "" <>; Libreoffice-qa 
<>; libreoffice-dev <>; LibO 
Mailing List Website <>; 
Sent: Tuesday, 4 June 2013, 17:25
Subject: [libreoffice-users] [ANNOUNCEMENT] LibreOffice Triage Contest - Win a LibreOffice 
T-Shirt! :)

Hi All,

This has been in the works for quite awhile, and now we are happy to say the time is here.

_LibreOffice Triage Contest_
Dates: June 20th, 2013 (0000 UTC) - July 5th, 2013 (2359 UTC)
(note that the wiki is being updated still but most info is there)
Prizes: Top 5 triagers will win a TDF/LibreOffice t-shirt

*Sign Up: In order to sign up you must do one of two things:*
a) add your name to wiki linked above (in the table with names listed)
b) e-mail me directly and say "I'd like to join", giving me your FDO account email address so that 
judges are able to monitor your work
*you must sign up prior to June 20th as judges will be following your work and we need to know who 
is participating

*Recommended Next Step
*1. Get familiar with bugzilla:
     *Get an account if you don't already have one
     *Learn how to use the query "search" function
     *Look through the list of UNCONFIRMED bugs (approximately 1,200 currently on the list)

2. Read the "how to triage" page

3. Join us on LibreOffice-QA channel if you want some guidance before the competition

Please take the time to get comfortable with these things BEFORE the competition as 
judges/moderators and QA staff will be quite busy during the period of the contest - the room has 
people in it usually 20 of the 24 hours of the day so chances are, you'll find someone in there to 
help out :)

Warm Regards,

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.