QA/Meetings/2012/November 03
TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate
Meeting of the QA Team | |
Date | 2012-11-03 |
Time (UTC) | 1300 |
Chair | Bjoern Michaelsen |
Secretary | Bjoern Michaelsen |
Started | 1300 |
Adjourned | ?? |
Participants | Bjoern, Florian R., Petr |
Agenda
No formal agenda prepared due to conference, open call to discuss anything
Minutes
Warning: Notes may not be formatted quite right']
- structured manual testing (Yifan?):
- MozTrap was quickly and ad-hoc demoed at the LibreOffice conference, found quite some interest (QA and RelEng Roundtable)
- bug wrangling:
- bugzilla with OpenID would still require registering
- that kinda defeats the purpose, any other ideas?
- skip HardHack selection, devs were almosty all at the conference last week (or swamped with preparations)
- bugzilla with OpenID would still require registering
- community building/communication (Cor?):
- Florian did some awesome work to make server installations (and thus master testing) on Windows more accessable:
- AI:take this to the ESC/Andras (Bjoern)
- the newly donated virtual machines should be used allow users to remotely login and test master
- intended to be combined with bibisect
- a lot of setup work though, still off a few months
- Florian came up with this work, to improve the quality of filed bugs:
- originally intended to be implemented inside LibreOffice (Florian)
- brainstormed at the german QA weekend
- would allow easy testdocument inclusion in upload
- safe detection of version and OS
- would be localized
- stats show already 50 unconfirmed bugs/month since the last cleanup
- multiple issues with implementing this inside LibreOffice itself (Bjoern):
- privacy
- proxy/connectivity settings (e.g. corp. firewalls)
- resources/assumed hard to find a volunteer for
- we cant adjust old and released versions
- the newly donated virtual machines should be used allow users to remotely login and test master
- AI: take to the ESC still, to prove the assumption (Bjoern)
- maybe better to extend a webbased solution for that (Bjoern/Petr)
- OS and version can be encoded in the initial "file a bug" url
- updateable and localizable
- no 'automatic' inclusion of docs, but that is tricky anyway from a privacy POV
- while our current infra team is stuffed with work, its in general easier to find talent for this kind of work (and maybe grow the infra team)
- in theory, it is possible to make the BSA file bugs without the reporter registering (Petr/Bjoern)
- file them from a [hidden email] account
- add a bsa-reporter:[hidden email] field in the whiteboard status
- add some procmail magic to the [hidden email] account that forwards to the bsa-reporter
- without keeping the original reporter in the loop, bug report quality will only get worse
- very hackish approach
- the idea to create to send the bug to a mailing list for review instead of blindly creating a bug is interesting (Bjoern)
- might help getting more people involved in QA
- works with local teams in non-english too
- we could do a testdrive of this with those l10n communities that have enough manpower to handle the incoming native language reports:
- portuguese/brazil
- french
- german
- english
- requires those prescreening the report to be responsive and reliable (thus their teams need a certain size)
- maybe better to extend a webbased solution for that (Bjoern/Petr)