Editing performance

Concrete deliverable:

• Instrumentation of VisualEditor
• Much of this is done.  Timing data is being emitted from ... 
  • http://gdash.wikimedia.org/dashboards/ve/
  • https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/master/modules/ve-mw/init/ve.init.mw.TargetEvents.js
  • https://github.com/wikimedia/mediawiki-extensions-WikimediaEvents/blob/master/modules/ext.wikimediaEvents.ve.js
• Needs
  •   Rigorous definition of what needs to be tracked
  •   Correlation of changes in code to changes in performance
  • Milestone:
    •   Weekly report sent out automatically from the system that is interesting, clear and actionable
• How does it align with the goals of the organization?
  • 2014-2015 Engineering goal: "Understand, measure, and monitor readership across projects."
• How does it align with other team's commitments?
  • TechOps wants to make metrics a priority for the coming quarter, so there's opportunity for collaboration there.

Editing performance Improving the user-perceived performance associated with all aspects of the editing experience Group: Editing Start: 2014-03-31 End: 2014-01-01 Team members: Ori Livneh, Tim Starling, Aaron Schulz, James Forrester, Roan Kattouw Lead: Ori Livneh

Documents

• User requirements:
• Specifications:
• Software design document:
• Test plan:
• Documentation plan:
• User interface design docs:
• Schedule:
• Task management:
• Release management plan:
• Communications plan: