QA/Execution/Web Testing/Meetings/2016-07-14

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to: navigation, search

Meeting details

Please see our public calendar for all upcoming events and meetings.

Our regular team meeting occurs every Thursday @ 9am Pacific

Lead / Scribe

  • Lead: stephend
  • Scribe: justinpotts
    • Scribe is responsible for:
      • adding the action items and takeaways to the current meeting's minutes
      • creating the agenda for the next meeting and carrying the action items and takeaways over to it
      • sending out a notice of the availability of that agenda along with the meeting invite
      • completing all of the above by the end of the week during which the meeting occurred

Last week's action items

  • None

Status updates

Meeting owner starts by giving a brief status update on what they've been working on, highlighting any releases, blog posts, blockers, etc. Once the update is complete, owner picks someone else to give a similar update. Repeat until everyone has had an opportunity to speak. This is entirely optional, and you are free to simply bounce to the next person. Notes are not taken.

Discussion items

Goals Check-in - 1st and 3rd meetings, monthly

Read only

Add any notes for the week here that do not need to be discussed during the meeting.

Time off / Out-of-office

PTO and other time out of office for Firefox Test Engineering

  • [davehunt] - October 26 - PTO
  • [davehunt] - December 12-14 - Honolulu marathon

Buildmaster (2-week duration)

  • Hands off to the next person at the end of the current Buildmaster's 2-week role, in the Web QA Thursday meeting

Rotation

The Web QA Buildmaster Rotation page contains the past and upcoming schedule.

These entries are in reverse chronological order.

  • 2016-05-05 - 2016-05-19 - stephend
  • 2016-04-21 - 2016-05-05 - mbrandt
  • 2016-04-07 - 2016-04-21 - davehunt
  • 2016-03-24 - 2016-04-07 - rbillings
  • 2016-03-10 - 2016-03-24 - krupa

Action items

Next Meeting

  • Next owner / scribe:
  • Next week's meeting notes: