User:KaiRo/Goals: Difference between revisions

← Older edit

User:KaiRo/Goals (view source)

Revision as of 16:58, 25 January 2016

4,920 bytes added , 25 January 2016

no edit summary

KaiRo

Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti

4,083

edits

@@ Line 1: / Line 1: @@
 Personal goals of KaiRo per quarter (in addition to ongoing routine work).
+== longer-term ideas ==
+* Get graphs for categories of crashes (GC, OOM, shutdownhang, GFX, JIT, ...) to monitor if the volume of some category improves of gets worse.
+* Get a crash rate graph done that is useful for putting up on office screens
+== 2016 Q1 ==
+* {{ok|}}Create a script or dashboard using Telemetry data.
+* {{ok|}}Start migrating the custom scripts that now are hg-hosted php using PostgreSQL over to git-hosted Python using Socorro API: Get at least one script into a github repository, using python and possibly the API instead of direct DB access.
+* {{done|}}Improve Top Crash Score report to deal better with the Socorro API rate limit as well as to accept more parameters via URL and add drop-downs for selecting those. [implemented except the dorpdowns]
+* {{ok|}}Reduce the amount of manual work done for routine tasks in Release Quality/Stability.
+* {{ok|}}Continue learning more about people management at Mozilla (praxis insights on hiring, tools and structure used at Mozilla for people management). [being involved in interviews was a good step, more next quarters on this ongoing goal]
+== 2015 Q4 ==
+* {{done|}}Move arewestableyet.com to use the same numbers as the graphs and link graphs from there.
+* {{done|}}Investigate Unified FHR/Telemetry as a source for better stability information. [partially done, Mozlando: sessions on Telemetry in general, bsmedberg's dashboard work]
+* {{done|}}Train Release Management team to help in stability tasks. [partially done, potentially another round in Mozlando]
+* {{miss|}}Start migrating the custom scripts that now are hg-hosted php using PostgreSQL over to git-hosted Python using Socorro API: Get at least one script into a github repository, using python and possibly the API instead of direct DB access.
+* {{miss|}}Improve Top Crash Score report to deal better with the Socorro API rate limit as well as to accept more parameters via URL and add drop-downs for selecting those.
+* {{done|}}Continue learning more about people management at Mozilla (praxis insights on hiring, tools and structure used at Mozilla for people management). [being involved in interviews was a good step, more next quarters on this ongoing goal]
+== 2015 Q3 ==
+* {{done|}}Tweak Top Crash Score to make it easier to use (e.g. color-code reasons for increasing/decreasing score). Note: additional pieces carried over to Q4.
+* {{done|}}Get [https://arewestableyet.com/graph/?fxbeta-bcat graphs] up for per-channel volume of startup crashes, OOMs, shutdown hangs and un-symbolized signatures,
+** {{miss|}}and work on getting this data into metrics systems that can be used for executive dashboards.
+* {{done|}}Get a [https://arewestableyet.com/office prototype] up for crash rate display on office screens.
+* {{miss|}}Start migrating the custom scripts that now are hg-hosted php using PostgreSQL over to git-hosted Python using Socorro API: Get at least one script into a github repository, using python and possibly the API instead of direct DB access.
+* {{miss|}}Investigate which areas of quality are unowned in Firefox/Platform at this point.
+* {{risk|}}Continue learning more about people management at Mozilla (praxis insights on hiring, tools and structure used at Mozilla for people management).
+== 2015 Q2 ==
+* {{done|}}Improve the "[https://crash-analysis.mozilla.com/rkaiser/crash-report-tools/score/ crash score]" (relevance-weighted topcrash) prototype into a state that can experimentally be used for prioritizing crashes in release decisions, figure out how well it works for that and adjust factors if/as necessary.
+* {{done|}}Highlight aspects of crashes that influence importance on the "crash score" prototype: startup, OOM, shutdown, number of installations, GC.
+* {{miss|}}(Stretch goal:) Get graphs up for per-channel volume of startup crashes.
+* {{done|}}Teach the full release management/quality team to run mozmill-ci update tests to remove myself from being a SPF while those still need to be run.
+* {{done|}}Learn more about people management at Mozilla (at least hiring process, additional areas as possible).
+== 2015 Q1 ==
+* {{done|}}Create a concept and prototype for a better topcrash metric that (de)prioritizes for more/less serious issues.
+* {{done|}}Familiarize with the current QE release process (more in depth) and build up some more routine about dealing with it.
+* {{done|}}Find how we can make the QE release process more effective and refine the release test plan wiki pages.
+== 2014 Q4 ==
+* {{done|}}Learn more about how QA train driving works and what can be improved in that process.
+* {{ok|}}Help rest of the Firefox QA team figure out how to focus work better, figure out how we could get metrics on that.
+* {{done|}}Attend TRIBE: AoS.
 == 2014 Q3 ==
-* {{ok|}}Get up metrics for OOM and GC crashes in addition to the overall rates, figure out possible additional groups to measure (GFX? JS? JIT?).
+* {{miss|}}Get up metrics for OOM and GC crashes in addition to the overall rates, figure out possible additional groups to measure (GFX? JS? JIT?).
-* {{ok|}}Automate more ongoing Firefox QA metrics, get a first version of a dashboard up.
+* {{done|}}Automate more ongoing Firefox QA metrics, get a first version of a dashboard up.
-* {{ok|}}Get verification process into a more uniform and transparent state (esp. in terms of bug queries).
+* {{done|}}Get verification process into a more uniform and transparent state (esp. in terms of bug queries). [Queries on dashboard are more visible now, new flag exists and is used, but we are de-emphasizing verification overall.]
+* {{done|}}Connect more with people on the QA team.
 == 2014 Q2 ==