Confirmed users
2,492
edits
No edit summary |
|||
| Line 1: | Line 1: | ||
=Projects & Programs= | =Projects & Programs= | ||
==Crashkill== | ==Desktop== | ||
===Electrolysis=== | |||
* Provide management assistance running meetings | |||
* Identify 4Q goals for project and track short term goals to completion | |||
===Silent Update=== | |||
* Manage effort running weekly meetings | |||
* Engage with Engagement, Product Management, releng, Security, and QA and keep them involved in the project | |||
* Kill major update pain points in 4Q | |||
==Cross Product== | |||
===Crashkill=== | |||
* Socorro Q4 goals - features/bugs we would like to see implemented in Q4 to support the mandate of crashkill | * Socorro Q4 goals - features/bugs we would like to see implemented in Q4 to support the mandate of crashkill | ||
** https://wiki.mozilla.org/CrashKill/Plan/Priorities#Q4.2F2011 | ** https://wiki.mozilla.org/CrashKill/Plan/Priorities#Q4.2F2011 | ||
== | ===Telemetry=== | ||
* | * Work with engineering teams to identify and implement probes for top three Blizzard questions. | ||
==Mobile== | ==Mobile== | ||
===Performance=== | ===Performance=== | ||
* Create standards of legitimacy for responsiveness tests - clear methodology and configuration for running tests. | * Create standards of legitimacy for responsiveness tests - clear methodology and configuration for running tests. | ||
| Line 24: | Line 33: | ||
===Java UI=== | ===Java UI=== | ||
* Project plan and schedule for development. | * Project plan and schedule for development. | ||
=Process= | =Process= | ||