Hi :) When you first start triaging you might find that there is only 1 or 2 admin/secretarial type tasks that you can do. So you might be able race through tons of bug-reports doing just that 1 thing.
As you gain confidence or experience (hopefully both) then you might find you have to slow down to do things like searching for duplicate bug-reports and linking them together. These slightly more complex tasks might mean you sometimes find ones that might be relevant but you are not entirely certain about so you either have to ask the QA mailing list for help and give them the numbers (or use whatever other mechanism they have set-up for that sort of question) or abandon work you might have spent a little time on and move on to do the same thing for another bug-report. It's part of a learning process and you probably don't even notice yourself gaining experience and increasing your success-rate. Even if you can only do certain limited specific things right now that "frees-up" someone to do other stuff and gives them confidence in knowing they don't have to worry about that area too much. If you can share your knowledge with other people who each have their own area then that creates quite a broad base quite quickly. Just think how much faster torrenting is than normal downloads Regards from Tom :) On 14 November 2013 04:49, Joel Madero <[email protected]> wrote: > On 11/13/2013 03:59 PM, Tim Lloyd wrote: >> >> Hi All, >> >> temperatures have been getting a bit frayed of late. There has been a lot >> of heartfelt discussion on devs/bugs/volunteers. What is our role in this >> product! How to volunteer. >> >> I had a look at the code - too difficult. Going forward I am going to try >> and make the effort to contribute to bug triaging. . >> >> Triaging is frustrating as I find I can only really look at specific bugs >> due to platform/knowledge limitations. Anyone else care to join? I think >> Joel has info for any newbies. >> >> Cheers >> > Indeed I'm more than willing to help just ping me. Triaging in general > shouldn't be frustrating. If directions aren't clear on the bug then mark it > as NEEDINFO and ask the user for explicit steps. I've found triaging to have > benefits and drawbacks, can be quite tiresome but you learn a ton about the > product and see all the interesting and unique things that people use > LibreOffice for. Furthermore, it's really the first (and critical) step in > getting bugs identified and into developers hands to get fixed. > > That being said, I applaud your being proactive - we truly do need more > users to take a step from being a user to being a contributor as the > workload is just to much for our small team. There are a ton of other non > tech ways to get involved - for instance marketing (they always need help) > and localization stuff (again, always need help). I can point you in the > direction if you're interesting in helping out in some other area. > > Best, > Joel > > -- To unsubscribe 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/users/ All messages sent to this list will be publicly archived and cannot be deleted
