Auto-tools/Automation Development/Meetings/WorkWeek July2011
Overview
Date: | July 25th - 29th |
Attendees: | David B., Henrik S., David C., Dave H., Owen C., Geo M., Anthony H., Matt B. |
What: | Automation Services Workweek UnCon |
Meeting Space
Where:
# Cambridge, UK
Twitter Hash
http://twitter.com/#!/search?q=%23mozautoqa
Agenda
Schedule | Meeting | Topic |
Monday, 10am - 12pm & 1pm - 3pm | Planning |
Create agenda - compiled list of sticknote topics http://mozqa.sync.in/54 |
Tuesday, 10am - 12pm & 1pm - 3pm |
Sessions | http://mozqa.sync.in/56 |
Wednsday, 10am - 10:50am, 11am - 12pm & 1pm - 1:50pm, 2pm - 3pm |
Sessions | http://mozqa.sync.in/58 |
Thursday, 10am - 10:50am, 11am -12pm & 1pm - 1:50pm, 2pm - 3pm |
Sessions | |
Friday, 10am - 10:50am, 11am - 12pm & 1pm - 1:50pm, 2pm - 3pm |
Sessions |
Monday
Reserved for planning out the work week. Prior to the work week we used a scrumpad to capture a few ideas.
- 10am - 3pm - Planning, break for lunch at ~12pm
- 6pm Springboard Pitches
- Topic generatation: link to sticknote topics http://mozqa.sync.in/54
Tuesday
- 10am - 12pm and 1pm - 3pm,
- New Members
- Internal Team Communication
- Team Dynamics
Notes from the day - http://mozqa.sync.in/57
Wednesday
- Team responsibilities
- Code Reviews
- Community
Notes from the day - http://mozqa.sync.in/58
Thursday
- 10am - 10:50am - Workflow
- 11am - 12pm - Goals
- 12pm - 1pm - Lunch
- 1pm - 1:50pm - Internal team communication (loop back conversation)
- 2pm - 3pm - - External team communication
Notes from the day - http://mozqa.sync.in/64
Friday
- 10am - 10:50am - Infrastructure
- 11am - 12pm - Group Documentation
- 12pm - 1pm - Lunch
- 1pm - 1:50pm - Meetups/Events
- 2pm - 3pm - From topic backlog/retrospective
Notes from the Day http://mozqa.sync.in/65
Action Items
New Members
Actions: David to create initial documents and share that with the team to get feedback Actions: Team to get a few questions together and share with QA as a whole.
Internal Communications
Action: Google Calendar to Visualize Timezones - Henrik to do action
Community
Action: We need to get Mozilla Contributor Engagement involvedAction: Find out what people what to learn so we can teach them
Responsibilities
Action: We need to prioritise tasks we should be doingAction: What is our minimum for tasks that we should be doing in our responsibilities? What is the things we can do more?
Code Reviews
Action: Check that README in WebQA projects have links to styleguide - It Does Action: have a look at the Google JavaScript styleguide Action: How do we spread the load on reviews?
Workflow
Action : add pivotal tracker project links to readme and project wiki so it painfully obvious
Goals
Action: Compare Responsibilities vs Current GoalsAction: Check point the backlog Priorities in each meeting
Internal Communcations
Action: Do we see value in a 1:1. Revisit in a few months
External Communications
Action: speak to AL to see if we can use as everyday too, need to get newsgroups plugin maybe
Infrastructure
Action: We need a staging server for Selenium