QA/Meetings/2014/February 10

From The Document Foundation Wiki
< QA‎ | Meetings‎ | 2014
Jump to navigation Jump to search
Meeting of the QA Team

previous - next

Date and Time (UTC) 2014-02-10 19:30 UTC
G+ Hangout [ This Meeting]
Chair Robinson Tryon
Secretary Robinson Tryon





Robinson, Dali, Sophie, Joel

Talkyoo Room Number 537138


Agenda + Minutes


Content from the meeting itself ("the minutes") will be displayed in blue boxes like this.

Before we Start

A few minutes before we officially start the call, we'll try to have a few people on hand to help assist newbies set up their teleconferencing gear, get things muted, and log on to all of our communication channels:


Put start time and attendees list in the table

The State of QA

Including any Opening Discussion

  • T-shirts update:
    • Kiva Cards?
    • More T-shirts delivered to:
    • Still en-route to:
      • Hackert, Mandal
  • Any update on possible Hackfest in the US (School in Pennsylvania) ?
  • Consider rethinking QA Meeting time (Joel)
    • It's too late for Florian R.
    • ACTION: Joel will set up a doodle for a new QA Meeting time
  • Kiva cards sent
    • Will send out blurb once I check with Italo/Marketing (Robinson)
  • Possible Bug Hunting event for 4.2.2 ? (Sophie)
    • 4.2.2 will be in RC in about a month
  • Pennsylvania Hackfest: Update?
    • Tentatively in April
    • Question about how many students we could get pre-registered (Joel)
    • What about partnering with OpenHatch?
  • Hackfests can give us multiple things:
    • Possible new contributors
    • GSoC interest
    • New contributors (in QA, Documentation, etc...)
    • Awareness of FOSS in high schools and university campuses
    • Awareness of LibreOffice in particular (good place for expanded use of LO)
    • ACTION: Joel will respond to planning email and help shape what we can/want to do
    • ACTION: Robinson will check-in with OpenHatch/Deb Nichols to investigate partnership
  • California has a lot of schools in close proximity, so might be a good place for us to plan a multi-school trip (Joel)


UNCONFIRMED bug count:

  • January 27th: 774
  • Today (10th): 874
  • Difference: +100
  • Numbers climbing up -- what can we do to keep these numbers down? (Robinson)
  • Some positive interest from NA users (Joel)
    • Make sure to have at least one of the experienced users in the chat room as much as possible
  • There are a number of duplicates that need to be consolidated (Sophie)

Topics for ESC?

Does anyone have any topics/concerns that I should bring to the Engineering Steering Committee (ESC)? (Robinson)

Need_Advice Bugs

Need_Advice bugs

I'm going to bring up the following bugs:

  • (Perhaps more a11y bugs?)
  • NeedAdvice list doing well (a bit shorter)

Pending Items

PENDING ITEM: MozTrap Localization

  • ACTION: MozTrap translation (GUI and tests) continues to be high-priority for QA (Needs someone to shepherd)

To review:

    • Other project who might want to work on translating GUI w/us?
  • Had interest from Mozilla coordinator at FOSDEM to join us (Robinson)

PENDING ITEM: Bugzilla Migration etc.

  • ACTION: Robinson will work on a new lobster mascot for our Bugzilla
  • ACTION: Robinson/Cloph will talk to Tollef about next steps in Bugzilla migration
    • Waiting to hear back from Tollef
  • ACTION: Joel/Alex working to give Robinson a VM in which to test Bugzilla ourselves
    • This will speed-up the 2nd half of migration and after-migration tasks


  • ACTION: Get Tollef to activate voting on FDO (merged item)
  • ACTION: Get Tollef to add BOLD statement to each FDO mail sent out to not reply via mail (merged item)
  • ACTION: Get Tollef to clarify 'version' label in Bugzilla (merged item)
  • ACTION: Will track the filed bug and wait to hear updates (re: Bold statement on FDO mail)
  • Owen made up a great lobster mascot -- will unveil it once we have our instance up and running (Robinson)
  • Will feel better if we can slowly work on our side in a VM (Joel)
    • Should have a VM up by end of February for testing
  • PSA: Now that we have Redmine up and running, the official position is to send infrastructure bugs there
    • (but FDO WWW subcomponent is still available for now)

PENDING ITEM: Bibisect Repositories

  • ACTION: Make combined bibisect repo available for testing (Robinson) + Provide better docs
  • ACTION: Provide documentation for mac bibisect on wiki (Robinson)

To review:

  • Robinson working on bibisect docs
  • IDEA: Add bibisect into regular Developer workflow
  • IDEA: Create graph/tool to show which builds contain a given commit
  • punt

PENDING ITEM: GUI for Bibisect

  • ACTION: Punt on implementation until after we have bibisect repos up and running (All)
    • Florian is working on a Windows-only version
  • Florian pushed-out a beta release ... (Joel)
  • ACTION: Joel will ask people to test the Windows Bibisect GUI

PENDING ITEM: Feedback pages

  • ACTION: Sophie will shepherd native-lang versions of Feedback page
  • [DONE] ACTION: Robinson will ping chs/website list to make sure the feedback page is styled per the site redesign
    • Feb 01 - Pinged chs/website list that the newdesign Feeback page still doesn't pass url params
    • Feb xx - Filed a bug in Redmine

To review:

  • Feedback page in new mockup
  • NL versions (bug #?)
  • We'll work on translations once the website redesign is put into production (Sophie)

PENDING ITEM: EOL, Release series, and Stable versions

  • ACTION: We'll wait and see if the Fresh vs. Stable (esque) language ends up in the updater (Robinson)
  • Wait and see how the website redesign presents the Fresh vs. Stable version, too

PENDING ITEM: QA Input into website redesign

  • ACTION: Sophie/Robinson - Keep QA in the loop re: updates to QA pages

Website Redesign:

  • New website will be out very soon (Robinson)
  • Sophie will get us an update in the next few days

PENDING ITEM: Start Center and Sidebar Concerns

  • ACTION: Robinson will get an update on the latest progress here from Stuart/a11y Team
    • Feb 1 - Emailed
  • ACTION: If you try to use LibreOffice without a mouse (and using a screen reader), how is the experience? (Everyone)

Relevant tracker bugs:

  • Will ping again
  • There's been a lot of discussion re: the sidebar (is it redundant?) (Joel)

PENDING ITEM: Introduction video to LibreOffice QA

  • ACTION: Mock something up/have something to show at a future QA Meeting (Robinson, Joren)
  • Delayed (FOSDEM :-)

PENDING ITEM: Planning Regular QA Events

  • ACTION: Joel will come up with a timeframe for future Bug Hunting Sessions/Triage Contests, with rationale.
    • Let's try to have an event every 6 months
  • Possibly something with 4.2.2
    • Sophie will organize it for Week 11

PENDING ITEM: Daily builds for all platforms

  • ACTION: Robinson will take point on making sure we get daily builds for win/mac/linux
  • ACTION: Write a script to make sure builds are being produced daily! (Robinson)
  • Will touch base with Cloph again
  • Mac builds of master are down today (Sophie)

Long-term/Frozen Pending Items

These are long-term or frozen items (i.e. on ice until something else happens) that we don't want to forget about...

PENDING ITEM: Update the whiteboard/keywords page

  • ACTION: Joel will turn this into an EasyHack and work on it (slowly)

PENDING ITEM: Most Annoying Bug List

  • ACTION: Joel will propose stricter guidelines for what qualifies as a MAB

To review:

  • How is the test going? (using the 'Priority' field in Bugzilla)


  • Things are going well (Sophie)
    • List is still growing a bit
      • Perhaps clarify exactly what criteria to be a MAB? (Robinson)

PENDING ITEM: What to do with FDO bugs filed against Extensions, Templates

  • ACTION: Joel will continue to monitor the situation

PENDING ITEM: Talk to CS Department/others at University

  • ACTION: Put up a message on the message board at his University and see who is interested (Joel)


  • ACTION: USA involvement in hackfests -- (Keep on the agenda, discuss on QA list) (All)

New Action Items

All items proposed between meetings go here

NEW ITEM: Title (Author)

New Items (Proposed/Discussed at the Meeting)

NEW ITEM: Title (Author)



Put meeting-adjourned time in the table


(Add topics below and reference them as #Example Topic in the Agenda/Minutes above)

Example Topic