Changes

Jump to: navigation, search

Platform/2014-Q4-Goals-ByTheme

8,765 bytes added, 22:38, 13 October 2014
Created page with "== Platform == === 2014 General Goals (by Product/Theme) === For Q4, the team decided to reformat the goals to demonstrate if they served a particular..."
== Platform ==
=== [[Platform/2014-Goals|2014 General Goals (by Product/Theme)]] ===

For Q4, the team decided to reformat the goals to demonstrate if they served a particular Product or more generally the Web Platform. We also wanted to call out high level themes around areas of focus. A list of the same goals broken down in the more familiar team format can be found [https://wiki.mozilla.org/Platform/2014-Q4-Goals-ByTeam here].

====Firefox Desktop====

<b>Theme</b>: Put Desktop on a growth trajectory by reducing crashes, enabling media and increasing performance

*e10s
** gfx support
** {{ok|{{bug|874016}} ensure all plugin work related to e10s is complete}}
** accessibility - e10s goal - TBD
** OMTC Windows

* Performance/responsiveness
** OMTA on non-B2G Platforms (980770)
*** {{ok|fix correctness bugs (cascading, etc.)}} - partly done in {{bug|996796}}
*** {{ok|turning on on other OMTC platforms (Mac/Win/Android)}}

* Text Performance
** {{ok|{{bug|934770}}}} - slow at rendering large blocks of plain text
** {{ok|{{bug|860492}}}} - Divide large text runs into smaller runs to avoid chrome hangs

* Media Source Extensions
** {{ok|Enable YouTube MSE/VP9{{bug|1000686}}}}
** {{ok|Enable YouTube MSE/MP4 on Windows}}

====FirefoxOS====

<b>Theme</b>: Support mobile web platform capabilities - feature parity with other platforms.

* DOM
** {{ok|WebComponents: one of :host ({{bug|992245}}) or :content (TBD which is more important) selector landed (preffed off) on m-c}}
** {{ok|respond to Service Worker feedback, adapt to spec changes, and improve performance}}
** {{ok|{{bug|701634}} land IndexedDB in workers on m-c}}
** {{ok|{{bug|997779}} Implement more w3c manifest (marcosc)}}
** Enable Vertical Text for major use cases for Chinese & Japanese
*** {{ok|{{bug|145503}}}} - Meta Bug.

* CSS Scrolling
** {{risk|CSS scroll snapping}} - spec issues prevent deployment

* JS
** {{ok|{{bug|972710}} ARM64 Baseline}}
** {{ok|{{bug|650161}} Compacting GC}}

* Accessibility
** {{ok|{{bug|1069598}} Gesture quicknav (ffos a11y)}}
** {{ok|{{bug|1069600}} Gesture text nav (ffos a11y)}}
** {{ok|{{bug|1069574}} Screen reader hints (ffos a11y)}}
** {{ok|}} GAIA: Fix [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Productivity%20b2ga11y%20p%3D1&sharer_id=458165&list_id=11280813 Productivity P1 a11y bugs] (~47 at this time)

====Firefox for Android====
* No clear goals called out for Q4

====Web Platform====

<b>Theme</b>: Framework for measurements

* Have a solution defined for fixing the ADI problem
** Understand the issue
** Investigate the solutions
* Some benchmarking goal (?)
** Figure out a plan for measurements and benchmarking for Platform

<b>Theme</b>: Drive web standards
* DOM
** {{ok|Produce a draft for [https://wiki.whatwg.org/wiki/Sharing Sharing] (annevk)}}
** {{ok|Define persistent notifications in the [https://notifications.spec.whatwg.org/ Notifications API Standard] (notifications associated with a service worker; annevk)}}

* CSS Grid
** Goal TBD

* CSS Ruby
** Our intern got through a bunch of this, but we'll continue it next quarter; remaining work tracked in {{bug|css-ruby}} and {{bug|enable-css-ruby}}
** {{ok|line breaking}}
** {{ok|vertical positioning}}
** {{ok|other dependencies on enabling the feature}}

* WOFF2 Fonts
** {{done|implementation {{bug|1064737}}}}

* CSS Animations, Transforms, & Transitions
** {{ok|transitions/animations spec editing}}
** {{ok|work to match new spec}}

* Web Animations:
** TBD

* JS
** {{ok|{{bug|837314}} ES6 classes}}
** {{ok|{{bug|894105}} SIMD.js IonMonkey x86}}

<b>Theme</b>: Progress towards more robust security hooks for better correctness in content security features like CSP, mixed content, etc.
* Add LoadInfo to all channels (dri=ckerschb,tanvi)
* Fix MCB redirect bug (dri=tanvi)
* Implement CSP Level 2.0 features (dri=sstamm,ckerschb)
* Initial Implementation of sub-resource integrity (992096) (dri=francois)

<b>Theme:</b> Progress towards defeating certificate misissuance, progress against Man-In-The-Mid, fresher/more accurate revocation informationdle attacks
* Add more BR checking (some combination of giving errors during path building, wall of shame, console warnings -- tbd) [dri=dkeeler]
* Identify what of Certificate Transparency we must/should deploy [dri=rbarnes]
* Complete phase 1 of migration to CA database [dri=kwilson]
* [stretch] Import mozilla::pkix to a branch of NSS [dri=jcjones]
* [stretch] Add ability to name constrain more root CAs [dri=dkeeler]
* [stretch] Add security warnings about SHA-1 to Web Console (dri=mgoodwin)


=== Engineering Operations ===

<b>Theme:</b> Product Related

<b>Theme:</b> Tool Development and Automation

<b>Theme:</b> Operational Efficiency


==== A*Team ====

(draft only)

Highlights:
* Develop a multi-binary harness for devtools - desktop
* Add e10s support to Talos, and either Marionette or Mozmill - desktop
* Make end-to-end testing in Autoland possible - platform
* Deploy ReviewBoard for developers to start using (carry over from Q3) - platform
* Add B2G support to mochitest-chrome - fxos
* Add support to Bugzilla for the Gmail transition - platform
* Prototype alternate bug views in Bugzilla to improve performance and usability - platform
* Continue improving sheriff and developer workflows in Treeherder - platform

See full list: [[Auto-tools/Goals/2014Q4]]

==== QA ====
(Draft)
* Shift focus to exploratory testing and finding bugs rather than verification for non-security bugs to see if that helps us find more high value bugs earlier in the nightly/aurora cycle (Will continue to attempt verification for all security bugs). - desktop
* Consolidate QMO and our dashboards so that it is easier to keep up with the state of quality among all projects - platform
* Experiment with unifying web testing technology stack for MDN with what developers are using to drive better adoption and lower maintenance costs of end to end web automation testing - platform
* Ensure marketplace payments automation running on Firefox 2.0 and above at least once per day fxos/mktplace
* Complete webRTC connection establishment and connection quality automated tests - platform
* Develop code churn correlation metrics and community health metrics (drop off rates of contributors performing QA tasks). -platform

[https://wiki.mozilla.org/QA/Goals/2014q4 Full list here]

==== Web Engineering ====
'''crash-stats'''
* {{ok|}} begin migrating subsystems to AWS
** e.g. migrate hbase to S3, architect cloud infra, build production-quality AMIs
* {{ok|}} enhance processor flexibility
** e.g. deploy processor2015, enhance tooling for developing post-crash classifiers, prototype alternate processing pipelines
* {{ok|}} enhance search functionality
** e.g. pull users from postgres search so we can shut it off, upgrade ES to 1.x, data dumps of search results
'''elmo'''
* {{ok|}} continue progress towards buildbot retirement
** e.g. migrating diff/compare tools to a10n, migrate remaining buildbot steps to a10n
'''airmo'''
* {{ok|}} prototype self-service publishing
** e.g. getUserMedia-based new hire video recording, user uploads of pictures and videos

==== DXR ====
* {{ok|}} Continue improving infrastructure.
** For example: [https://bugzilla.mozilla.org/show_bug.cgi?id=1045183 move file rendering to request time], implement [https://wiki.mozilla.org/DXR_Parallel_Tree_Indexing independent tree rendering], or finally [https://bugzilla.mozilla.org/show_bug.cgi?id=959728 replace the config subsystem]
* {{ok|}} Pick newly low-hanging fruit.
** With the new plugin architecture and Elasticsearch backend, a lot of previously difficult possiblities are opened to us. Examples: index a new language, show result counts, show indexed revision identifiers, do some [https://wiki.mozilla.org/DXR_Result_Mixing result mixing], or default the query parser to interpret text runs as phrase matches.

==== SUMO and Input ====
(draft only)
* Implement v1.0 of BuddyUp, the live support app for FirefoxOS, and integrate it with existing SUMO web app.
* Update SUMO forums.
* (Input goals still under discussion)

==== Release Engineering / Release Operations / Developer Services ====
* Identify, measure, and publish core release engineering KPIs.
* Develop a plan for disaster recovery and business continuation in the event of a disaster for release infrastructure.
* Make try stable and fast.
* Support Windows 64 initiatives as needed.
* Automate merge day processes to free up engineer time and reduce opportunity for error.
* Develop automation and self-serve APIs for developers to remove the need to have one full time engineer on buildduty.
* Automate release processes, again to free engineer time and reduce opportunity for error.
Confirm
2,492
edits

Navigation menu