Hi :) I like the changes. Actually i prefer "someone" to "bug-triager" and "person" to "developer"
While the more precise definitions are important to us and we might 'naturally' understand what the terms ,eam those things might not be so obvious to a noob. In photography a developer is a liquid and bug-triager could be a bot or anything. It could even mean that crazy loony from CSI: Vegas. I think the important thing for a noob to know is that when they post a bug-report the very next actions that happen to the report will be done by a person, a human being, not a machine ior automated process. Beyond that is just confusing detail that they don't really need to know at such an early stage. Perhaps some hierarchy tree or flow-chart might help the user understand the process that happens after filing the bug-report but again i think it's too much information and so it risks confusing the poor wide-eyed-end-user. Regards from Tom :) >________________________________ > From: Sophie Gautier <gautier.sop...@gmail.com> >To: documentation@global.libreoffice.org >Sent: Friday, 15 February 2013, 19:29 >Subject: Re: [libreoffice-documentation] De-geeking BugReport on Wiki > >Hi Kieran, >On 15/02/2013 19:56, Kieran Peckett wrote: >> I have just de-geeked the BugReport page on the wiki, as well as a few >> other updates. > >Thanks a lot for that, usually it's better to inform the QA team about >your work/modifications as this is their work that is detail here. >> >> Permalink: >> https://wiki.documentfoundation.org/index.php?title=BugReport&oldid=63321 >> >> Diff: >> https://wiki.documentfoundation.org/index.php?title=BugReport&diff=63321&oldid=62052 >> >> Full list of changes: >> >> - De-geeked parts of the page >> - Changed ALL CAPS (e.g. WRITER) to regular type (Writer) >> - Improved Ubuntu instructions on how to get to the terminal, as the >> Apps menu in Unity doesn't uses categories. >> - Changed some references to OO.o to OO.o and AOO >> - Added ADVANCED to the end of the "Extra info for developers" section >> header >> - Explained the Ctrl+Alt+T shortcut in some Linux distros for access to >> Terminal >> - Improved some English > >Something I do not agree with : >----------------------------------- ># If you are not sure what component your problem is about, choose the >'''Libreoffice''' component. Someone will come and change it later. For >more information about this, have a look at >"[[QA/BugTriage|BugTriage]]". If it is an urgent issue (broken parts, >regression, etc), experienced users can assign it to one of the >developers listed on the ''[[FindTheExpert]]'' page. >------------------------------------- > >You can't change a 'bug triager' by 'someone', a bug triager is a role >and a function in our QA project :) >'High priority' is something different than 'urgent'. Before filling a >bug you have to check about its priority. A bug can be urgent for you >but have a very low priority in term of QA. Here the terminology is >important for the quality of the bug report. > >Kind regards >Sophie > >-- >Sophie Gautier <sophie.gaut...@documentfoundation.org> >Tel:+33683901545 >Membership & Certification Committee Member - Co-founder >The Document Foundation > >-- >Unsubscribe instructions: E-mail to documentation+h...@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/documentation/ >All messages sent to this list will be publicly archived and cannot be deleted > > > -- Unsubscribe instructions: E-mail to documentation+h...@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/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
