Confirmed users
753
edits
Auto-tools/Automation Development/Meetings/WorkWeek July2011: Difference between revisions
Auto-tools/Automation Development/Meetings/WorkWeek July2011 (view source)
Revision as of 10:53, 3 August 2011
, 3 August 2011→Action Items
(→Friday) |
|||
| Line 98: | Line 98: | ||
=Action Items= | =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 | |||