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


Hi all,

taking into account that some of us are present at Brno Libreoffice Conference this week, we're going to have a face-to-face QA meeting from 19.00 to 20.00 UTC+2 at the Red Hat Offices while the hackfest session is taking place.

Therefore, I invite everybody present at the Libreoffice Conference to join the meeting as we would like to hear anything you have to say with regards to QA.

On the other hand, we would also like to try something Gabriel proposed yesterday. Basically, we would like to offer the possibility for non-QA/non-developer people to report bugs in person, mainly thinking of FOSDEM and the incoming Libreoffice Conferences, so we can also show them how doing QA looks like at the same time. We plan to do a public announcement in the social networks during the course of the day and it's going to take place today from 20.00 to 22.00 to see whether someone is showing up or not.

I'll keep you updated.

Regards
Xisco
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: https://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

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.