https://bugs.freedesktop.org/show_bug.cgi?id=57199
--- Comment #17 from Petr Mladek <[email protected]> --- I would use something like the following text at http://wiki.documentfoundation.org/Triage_For_Beginners: 1. Find[1] a bug that you want to try to reproduce 2. check if it is reproducible; leave a comment, set status NEW or NEEDINFO[2] 3. check if component, severity and priority looks reasonable[3] 4. escalate major, critical, and blocker bugs[4] 5. optional: add more useful information[5] If you are in doubts, please contact us on [email protected] The links [1][2][3][4][5] should point to a more detailed information: [1] how to find non-triagged bugs [2] hints what to do if it is reproducible, what to do does not work, what to do it is works [3] hints what means reasonable component, ... well, this is not clear even for experienced triaggers but it should be important part [4] hints how to escalate bugs (developers in CC, Whiteboard flags, MABs) [5] hints how to add more useful information (more Whiteboard flags, check if it is a regression, add backtrace, do bibisect, add test document, screenshot, easier steps to reproduce) My approach is that we should teach people how to do it correctly from the beginning. Of course, we must not scare them by complex intro page but we should provide handy links to details. I prefer to link particular sections than just link the whole scary page on the end. The text on the intro page need to describe the basic idea, so people could do the job intuitively even without reading details. Finally, I still suggest to point people to the mailing list. IMHO, http://wiki.documentfoundation.org/QA/QA_Team is not a good idea because the page is not up-to-date, some people might not react well. I think that some shared place would work better. We need to create a living and friendly place from the QA mailing list anyway. We could add more shared channels if we have them later. If you do not mind, I could update the wiki. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
