Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi All,

I wanted to first say thanks to everyone who has contributed to the
triaging project. I'm still hopeful that we can get this done but we're
going to have to start actively trying to grow our QA membership. I've had
relative success in #libreoffice just casually asking if there are any
users who want to help out - I think I've gotten 2 or 3 people who have.
This being said, if you have any recommendations for someone I can try to
convince to help out, please let me know (or ask them). Our #'s aren't
growing which is good, but at this point they aren't shrinking much either
(steady at 850ish bugs that are > 30 days unconfirmed). Goal is still to
have this down to 0 by the end of the year.

I was hoping that each of the people who have added their name to the
triaging spreadsheet could join a triaging "party" in the next 2-3 weeks.
My time zone becomes an issue but I'm willing to do the weekend or even
really late evening my time zone.

Also hoping that devs and other QA people subscribed to the mailing list
will volunteer to help out.

I won't be doing it unless we can at least get 10 people committed, without
this number it's likely to not be very functional. I'm hoping for a 1 - 2
hour commitment.

Please respond proposing if you'd be willing to help, if I get at least 10
responses I'll set up a doodle to arrange a time.

Best Regards,
Joel

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.