<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> Time Start: 1405 UTC Present: Peter, Florian, Joel, Joren, Thorsten Completed Action Items *Wiki for Hard Hacks – on hold until after release of 4.0 (Joel) *Wiki page for triage contest (Joel) *Bibisect Torrent/Mirror – No longer needed with bibisect repository *Wiki for FDO policies/rules (Joel) *Get permissions for Joel (Bjoern & Tollef) Pending Action Items *Bugs which are not touched for long period of time (Florian) +UNCONFIRMED -Not users fault, we will not automate anything and will not ask the user for more work on their part. +NEEDINFO - Discussion lead to agreement that automating comment to remind users followed by automatic closer of bug after some period of time appropriate -Follow-up email lead to moving this conversation to QA mailing list to get broader consensus.. <meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"> <title></title> <meta name="GENERATOR" content="LibreOffice 3.6 (Linux)"> <style type="text/css">  </style> *Localized BSA (Rob) +Rob has been in contact with Florian trying to work out details *Goals +Punt until after Release of 4.0 *Hard Hacks (Alll) +Message on wiki stating that these are on hold until after release of 4.0 *Funding WishList (Everyone) *Shipping Costs +Marc's email thread on member mailing list possible - Details need ironed out but having TDF members sign up to be “carriers” in their region. They can be responsible for buying “locally” and then shipping to prize winners, etc... *Triage Contest (Everyone) +Wiki page up, need to start filling it out - <a href="https://wiki.documentfoundation.org/Bug_Triage_Contest">https://wiki.documentfoundation.org/Bug_Triage_Contest</a> +Date -AGREED: 2 Days after release of 4.1 RC1 -AGREED: Length will be 14 days +ACTION: Joel will link page to FDO rules (see below) *Bibisect +No longer need mirrors or torrents because of new bibisect repository *Wiki Updates (Joel & Joren) +<a href="https://wiki.documentfoundation.org/QA">QA</a> and <a href="https://wiki.documentfoundation.org/QA-Team">QA-Team</a>, not much progress yet +Action: Joren will add a welcome message to QA wiki +Action: Joel will email everyone on QA-Team list and see if they want to stay on that list *FDO +Mime Type (Bjoern & Joel) -Not changed yet to Auto, no word from Tollef - Action: Joel will talk to Bjoern about this +Version Message -Bjoern in contact with Tollef about this +Twitter (Bjoern) - No Update +Permissions (Joel) -Joel now has permissions to permanently or temporarily ban users -New wiki describes rules and procedures *<a href="https://wiki.documentfoundation.org/FreeDesktop_Rules_Procedures">https://wiki.documentfoundation.org/FreeDesktop_Rules_Procedures</a> -Hopefully this is never needed +Metrics -None +NEW vs. REOPENED -Reopened discussion as previously agreed upon structure wasn't working -ACTION: Joel will talk with Bjoern about if we can ask Tollef to make it so we can set a bug back to UNCONFIRMED even after it's set to WFM -AGREED: If above can be done, we'll ask users to reopen bugs as UNCONFIRMED if WFM status not correct so that other QA members can easily look into the bug as well. NEW will mean confirmed, REOPENED will only be done if the bug was marked as FIXED & is assigned a developer but the user says it's not fixed. -AGREED: If above is not possible, we will treat REOPENED the same as UNCONFIRMED unless it is assigned a developer. If the bug is not assigned and is REOPENED, QA will mark as NEW if we can confirm the behavior. New Items *FDO +Assigning Bugs -AGREED: At this time QA team “pushing” bugs to developers isn't working, we will now only do “pull” philosophy (developers choose their own bugs and assign themselves -AGREED: The >300 bugs that are assigned but haven't been touched in over 6 months is a problem as developers who could fix bugs will not touch bugs that are assigned to someone else. These bugs should be unassigned & developers should be placed in CC list. *<a href="https://bugs.freedesktop.org/buglist.cgi?list_id=209831&emailtype1=notequals&chfieldto=2012-07-17&query_format=advanced&emailassigned_to1=1&bug_status=NEW&bug_status=ASSIGNED&email1=libreoffice-bugs%40lists.freedesktop.org&product=LibreOffice">Assigned (status NEW or Assigned), No Movement </a><a href="https://bugs.freedesktop.org/buglist.cgi?list_id=209831&emailtype1=notequals&chfieldto=2012-07-17&query_format=advanced&emailassigned_to1=1&bug_status=NEW&bug_status=ASSIGNED&email1=libreoffice-bugs%40lists.freedesktop.org&product=LibreOffice">6+ Months</a> -ACTION: Joel will e-mail developer mailing list with decision, inform developers that we will be automating an action to unassign them from untouched bugs of over 6 months UNLESS they speak up and say that this is a bad plan. +FDO #59717 (Most Wanted Enhancement or some such list) -No discussion, will discuss at next meeting +Default Assignee -Joel doesn't like that there is a default assignee email, could be confusing for new developers – a friend who has started developing for LibreOffice recently pointed this -AGREED: No real solution for this unfortunately, e-mail is linked to IRC bots and other things so removing is not possible. Changing name to UNASSIGNED@... would make a mess of FDO -Solutions welcome here but no action to be taken +QA Field -Joel requested that QA field is used by triagers because it will help: *Knowing if something has been prioritized correctly *In the future with FDO maintenance +Default Priority/Importance -Can this be changed to NONE or some other such thing so that it's much easier to see when a bug is triaged/prioritized -Good to have a QA contact for developer & for reporter/commenters -Goal is to slowly move away from lists like MAB, Hard Hacks, etc... and instead be able to use priority/importance correctly (long term) -AGREED: Everyone agreed they will try to use QA fied when they triage a bug -ACTION: Joel will discuss default Importance/Priority with Bjoern and possibly Tollef *Name “Personas” Could Be Wrong (Florian) +Florian brought it to our attention that Firefox is going to be using the name “Personas” for something else and changing to “themes” -See comment in: <a href="http://flosmind.wordpress.com/2013/01/18/personas-in-libreoffice-color-your-office/#comment-608">http://flosmind.wordpress.com/2013/01/18/personas-in-libreoffice-color-your-office/#comment-608</a> - <a href="http://identity.mozilla.com/post/18038609895/introducing-mozilla-persona">http://identity.mozilla.com/post/18038609895/introducing-mozilla-persona</a> +ACTION: Joel will email Kendy about this ACTIONS *Bjoern +Twitter Feed +Mime type default (update?) *Joel +Metrics (bugs) +Update QA and QA-Team wiki +Email Kendy about Personas name +Bug Importance/Priority Default – discuss with Bjoern, report back +Link Triage Contest Wiki to FDO Rules +E-Mail Everyone on QA-Team page, find out if they want to stay on there +Allow WFM to become UNCONFIRMED again – Discuss with Bjoern, possibly with Tollef +E-Mail Dev list about untouched bugs *Joren +Update QA and QA-Team wiki +Add a welcome message to QA wiki *All +Continue looking into shipping options End Time: 15:05 UTC </body> </html>