One idea that has worked for me is to personally ping users that are on FDO with a personal email thanking them for their hard work and encouraging them to become more active (weekly meeting + bibisect + IRC channel). This has been relatively successful (just this week I pinged a member who has been doing a ton of bibisects and he says he hopes to join QA call come September.
It's vital that we continue to grow our team as we get a few really active members busy and our bug count sky rockets - plus we have more tasks that we're not even close to completely doing (prioritizing for instance, or checking really old NEW bugs to see if they are now WFM) and the truth is - we need to at least triple the # of people actively involved in QA.
Dig through FDO to find the top 10 most active people that aren't really well known in QA but are all over the place on FDO and send them a personal "hi, welcome, thanks, do more" email ;)
migrated from https://redmine.documentfoundation.org/issues/605
Great idea - this obviously works because people feel recognised and appreciate personal contact with fellow enthusiasts :)
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.1 or preferably 18.104.22.168 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
I have actually pinged ~100 bug reporters with a personal email during 2015. About 1/5 said they are interested in doing QA. Not all of them started doing it, but perhaps there is a long term effect.
I have discussed this a few times in QA meetings and have proposed an automated recruiting message for the first couple of bug submissions:
It could be in the BZ interface, an email (in that case only once) or both.
Migrating Whiteboard tags to Keywords: (topicQA)
I think it would be better to deal with this issue in redmine. However, I don't have authorization to see it...
Automated in https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/commit/?id=606053655530f03b14810008dc5330ad68f366e1.
From now on, this task will be monitored in https://redmine.documentfoundation.org/issues/2351.
Closing as RESOLVED FIXED