A great way to help the QA team (and actually become a member of the team) is confirming bugs.
For that, see:
and confirm the bug by setting the status of the bug to NEW if you can reproduce the bug and the other conditions from that wiki-page are met.
Oh, and if you have questions on how to go ahead with things, contact the QA-Team on the mailing-list or on IRC, rest assured we dont bite:
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
@Björn: Do we want to keep this bug report? I understand the rationale behind (thank you very much for your call), but I am not sure if new users will look for this bug report?
(In reply to A (Andy) from comment #3)
> @Björn: Do we want to keep this bug report? I understand the rationale
> behind (thank you very much for your call), but I am not sure if new users
> will look for this bug report?
This bug is marked as an EasyHack an thus listed on our wiki pages about that.
Migrating Whiteboard tags to Keywords: (easyHack, difficultyBeginner, topicQA)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
This is not something that can be solved, and therefore as such not a bug. We should not use the bug system for announcements, we have other means to onboard people.
QA EasyHack exist for https://wiki.documentfoundation.org/QA/Easy_Hacks => reopening as new.
Not my scope
This has been added to the getInvolved page: https://wiki.documentfoundation.org/QA/GetInvolved.
Thus, Closing it