TPEGFX/2015-04-23: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 4: Line 4:


===Chiajung Hung===
===Chiajung Hung===
* {{Bug|1156140}} - Choose different code path for boot animation based on device capability
** f+/r?
* {{Bug|1156141}} - Make switch from boot animation to first system app screen seamlessly
** filed
** Help debug
* Hack dirty region
** debug


===Ethan Lin===
===Ethan Lin===

Revision as of 01:59, 23 April 2015

Weekly Report

Boris Chiou

Chiajung Hung

  • bug 1156140 - Choose different code path for boot animation based on device capability
    • f+/r?
  • bug 1156141 - Make switch from boot animation to first system app screen seamlessly
    • filed
    • Help debug
  • Hack dirty region
    • debug

Ethan Lin

Jeremy Chen

  • bug 1152263 - [Messages][Text Selection] Hard to drag the caret when there is an attachment in the beginning of a message
    • land
  • Clipboard Web API
    • bug 1012662 - implement click-to-copy and click-to-cut permissions (semi-trusted events)
    • bug 1151429 - Allow JS to copy text to the clipboard by triggering document.execCommand('copy') or document.execCommand('cut') in user-initiated thread
    • study
    • prepare for presentation
    • spec. update: W3C Working Draft 21 April 2015

Jerry Shih

Morris Tseng

Tingyu Lin

  • bug 1110039 - Refactor Touch/SelectionCarets
    • r-
    • Add more documentation and comments to the code.
  • bug 1155493 - Refactor event dispatching in Touch/SelectionCarets
    • file
  • bug 1156037 - SelectWord triggered by NS_MOUSE_MOZLONGTAP widget event doesn't move focus
    • r
  • bug 1156636 - Dragging a selection-caret starts panning at a large zoom-in scale
    • file
  • bug 1156160 - Blur event closes SelectionCarets but leaves visible selection on page
    • debug

Peter Chang

Team

Rule of Thumb

Status code:

  • OOAD: In analysis or design phase.
  • WIP: working on WIP patch.
  • feedback(f): feedback a patch
  • feedback?(f?): WIP is ready for feedback grant.
  • feedback+(f+): Get positive feedback.
  • feedback-(f-): Get negative feedback.
  • review(r): review a patch.
  • review?(r?): patch is under review
  • review+(r+): get review+ and ready to check-in
  • review-(r-): get negative review feedback. Fix problems and switch back to r? again.
  • land: patch check in.
  • debug: Figure out the root cause of a bug/ try to repro that bug, etc...
  • file: file a bug
  • PTO: take personal leave
  • interview(I)
  • study: Spend time on domain knowledge study, such as multimedia transport technology, compress format, real-time rendering.
  • presentation
    • Write a personal blog, which is relative to work, such as articles on MozTech, or what you experience in a work week.
    • WIKI/ MDN article writing.
    • If you write a technical blog or anything relative to work, it's welcome to share it on weekly report.
    • Do a presentation of technical topics

Status code combination rule
Combine status code with "|". For example

** OOAD|WIP

Which means you work on both OOAD and WIP in the last week.

land status code
If your patch is target for specific branch, instead of central, postfix branch version. For exp

** land(1.4)