Activity Map: Difference between revisions

← Older edit

Activity Map (view source)

Revision as of 01:46, 26 February 2013

351 bytes added , 26 February 2013

→‎Automation

Ctalbert

Confirmed users

3,816

edits

@@ Line 9: / Line 9: @@
 ==Automation==
-* Testing
+* Automated Test Framework Development
-** Desktop
+** Builder tests: leaktest, profile test, make check
-** Android
+** Desktop: mochitest, browser-chrome, reftest, xpcshell, gtest, c++ tests, javascript tests, mozmill
-** B2G
+** Android: all desktop, plus robo-cop
+** B2G: all desktop, plus emulator web API, Gaia UI tests, Gaia integration tests, Gaia unit tests
+** Underlying automation components: mozbase, marionette, mach (shared), breakpad, crash integration in tests, building symbols, mozharness (shared), mozpool, automatic power cycling for mobile devices
+* Automated Performance test Framework, mozmill-ci, mozmill-environments, jenkins build systems for b2g, selenium, webdriver W3C spec
+** Desktop: talos, multi-browser speed tests, eideticker
+** Android: talos, robo-check (a form of talos), eideticker
+** B2G: b2g-perf framework, eideticker
+* Internal Developer Web tools
+** TBPL
+** Datazilla
+** Orangefactor
+** Moztrap
+** Bughunter
+** Bugzilla.mozilla.org
+* Internal Developer tools
+** Mach
+** Bisect in the cloud (mozregression's next version)
+** Debugger interfaces (something I'd like us to do more of)
+** Pulse
+** Profiler integration
+** Code coverage analysis
+** Performance regression analysis
+** Test synchronization with W3C test repos
+* Automation/Code Quality
+** Sheriffing of the Trees
+** Developing and educating others on developing automated tests
+** General bugzilla.m.o bug triage policies and community building around the early bug life cycle
 * Release Engineering
@@ Line 245: / Line 271: @@
 * MDN
 * www.mozilla.org
+* webplatform.org
 ==Education and Learning==
@@ Line 252: / Line 279: @@
 ==Engagement==
-https://wiki.mozilla.org/Engagement
-*Brand Engagement: responsible for ensuring that the Mozilla and Firefox brands are communicated clearly and consistently by us, our contributors, and our partners.
+* Community Engagement
+** Direct user channels (Snippet, social, e-mail)
+** Reps
+** Gear
+** Students
+** Community Tools
+** Word of Mouth Marketing
+* Brand Engagement
 ** Creative
 *** Video
@@ Line 266: / Line 300: @@
 *** Paid media
-*Developer Engagement/WebProductions: serves the Mozilla mission by promoting open Web-related technologies to developers and through web development
+* Developer Engagement
-** Mozilla.org web development
 ** Engagement web application development
-** [http://developer.mozilla.org Mozilla Developer Network]
 ** Demo Studio/DevDerby contest
 ** Hacks.mozilla.org blog
-** Promoting Web standards and Mozilla initiatives at Mozilla and external events
-** Mozilla Hack Days (such as Firefox OS Apps Days)
 ** Firefox OS phone distribution
 ** Liaison to related efforts at other organizations (such as WebPlatform.org)
-*Events
+* Events
 ** MozCamps
 ** Mozilla Festival
@@ Line 283: / Line 313: @@
 ** Industry Events (MWC, SxSW, etc)
 ** Local events (via Mozilla Reps)
+** Mozilla Hack Days (such as Firefox OS Apps Days)
-* Product Marketing: Responsible for the promotion and adoption of Mozilla products and the Mozilla vision. Focuses on user, market, and competitive research; devising and driving product development and business strategy, and devising and driving the outbound marketing strategy for our products.
+* Product Marketing
 ** Firefox
 ** Firefox OS
@@ Line 290: / Line 321: @@
 ** Market Insights
-* Communications: cultivates trust with different communities by communicating Mozilla's story to the press and other media. The team acts a mediator between the company and the wider public, helping users get to know Mozilla by maintaining transparent communication, while maintaining the positive and active voice unique to Mozilla.
+* Communications
 ** Earned Media
 ** Crisis Communications
-** Internal Communications (shared with People team)
+** Internal Communications
-* Community Engagement: Empower and grow our overall community, from users to core volunteers, to not only use Firefox and Mozilla products, but to advocate and promote, and actively participate in Mozilla.
-** Direct user channels (Snippet, social, e-mail)
-** Reps
-** Gear
-** Students
-** Community Tools
-** Word of Mouth Marketing
-*Other
+* Other
 ** Air Mozilla
@@ Line 641: / Line 664: @@
 **** tegra dashboard
 **** mobile dashboard
-** Database Operations
+** Database Engineering
+All databases for Core IT and Webhosting services.
+See also https://blog.mozilla.org/it/2012/06/13/what-does-a-self-assessment-look-like/ and https://blog.mozilla.org/it/2012/12/31/2012-mozilla-db-year-in-graphs/
 ** Storage/Virtualization
 * Labs