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


Time Begin: 1405
Present: Florian, Joel, Joren, Petr, Robinson

Pending Action Items
*NEEDINFO
+AGREED: Current text is good for 1st comment to be added to all NEEDINFO bugs which have not had activity for 6+ months.
    +AGREED: This week we will start process
+ACTION: Joel will be responsible for mass bug changes this round, he will do test with ~20 bugs to make sure system works, then move forward with the rest of them -Will email developer list to let developers know the data/time that change will occur -AGREED: Temporary whiteboard status to monitor bugs that are mass commented on

*Bug Submission Assistant (Localized French)
+Update from Rob is that most technical work is done, some minor translation is ongoing from Sophie

*Realistic Goals
    +New wiki page discussed in “NEW ACTION ITEMS”
    +https://wiki.documentfoundation.org/QA_Projects

*Funding Wishlist
    +Need update from Bjoern about status of netbooks
-If netbooks are approved: ACTION: Joel will write up proposal for how we go about determining if someone is eligible to get one

*Triage Contest
    +AGREED: Timeline looks good, plan to do contest June 20th – July 5th
    +Any notes about rules can be sent to Joel via email
+ACTION: Joel will work on rough draft of rules over the next few weeks
    +Ideas for prizes
       -Hoodies, T-Shirts, Mug, laptop case

*Wiki Pages
    +Joren has merged and cleaned QA-Team page
        - https://wiki.documentfoundation.org/QA/QA_Team

New Action Items
*FDO
    +Prioritized Bugs
-AGREE: Somehow being able to determine what bugs have been prioritized by QA is a good thing -A lot of discussion about using QA field or new whiteboard status – pros and cons discussed -Lead to discussion about what QA contact means, some disagreement and acknowledging pros/cons of different ideas -AGREED: Move conversation back to mailing list to try to find best solution, aim to have final vote next meeting. -ACTION: Joel will start thread back up from Rainer's previous thread.

    +Verified – WORKSFORME
-AGREED: Makes a lot of sense to have this, original reporter can confirm that a bug indeed WFM by setting status to VERIFIED – WORKSFORME -AGREED: If QA member sets bug to WFM they should leave a comment explaining that if reporter can verify to change status, if they cannot, to reopen as UNCONFIRMED

    +Signature
-Using signature could be good if it invites users to contribute to LibreOffice through multiple avenues such as QA, marketing, developing, and explains that run by a team of volunteers. Also a pointer to good bug reporting (reproducible steps, good prioritizing)


*Wiki
    +New wiki page to track QA projects
        - https://wiki.documentfoundation.org/QA_Projects
-Everyone welcometo add projects, idea is that if someone leaves QA, their projects will continue for others to work on

    +Team Page
        - https://wiki.documentfoundation.org/QA/QA_Team
-Everyone who wishes to be included in “QA Team” should add name to this list

End Time: 1510

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.