TPEGFX/2014-12-11

Weekly Report

Boris Chiou

• PTO: A week

Chiajung Hung

• bug 918984 Direct video stream texturing support on WebGL
  • WIP
  • Refactoring the whole patch to make it compact and clean
  • Study related codes in HTMLImageElement/ImageLib, CanvasElement(2D streaming)

Ethan Lin

• bug 1108978 - Crash in debug build CompositorOGL::CreateRenderTarget MOZ_ASSERT
  • f?
• bug 1108924 - [B2G][IPC] Move fence / texture async messages from ImageBridge to SharedBufferManager
  • WIP

Jerry Shih

• bug 1101974 - Create a single VsyncDisptacher per nsBaseWidget
  • WIP
  • Get VsyncDispatcher from widget.

Morris Tseng

• Refactoring Touch/Selection carets
  • Implementing gtest.

• bug 1092888 - [Text selection] Enable selection carets for non-editable fields on B2G and fix the existing test case failures
  • Fix try fail.

Tingyu Lin

• bug 1067728 - [Text Selection] Hide utility bubble after scrolling if the selected text is out of visible area
  • r+, sr+

Peter Chang

• bug 1098161 - [Text Selection]Trigger text dialog by long press when input filed is empty
  • r?
  • Ask UX to clarify the difference between long tap and short-cut behavior

• bug 1068474 flicker to tilt mode when selection range is changed
  • WIP

Team

• V2 schedule
  • Based on Gecko 37
  • Move to auora on 1/12
  • FC on 2/23 and Branch to 2.2
  • Features related to GFX - CopyPaste and L porting

• Three directions for 2015
  • V2
  • Stability/Performance/Platform work/Unit Test
  • V3

• V3 is in ideation stage.
  • Mopad for Groups, https://etherpad.mozilla.org/v3-groups.
  • Procedure doc,
    1. Add Yourself to the Agenda: http://bit.ly/LightningTalkSignUp
    2. Review how we will enable, capture and communicate ideas: http://bit.ly/v3_Ideation_Overview
    3. Idea Submission (linked to from document above): http://bit.ly/Slack_HowTo
  • You can implement the prototype for V3. But don't land codes on master before having the firm scope of V3 features.
  • Schedule(not firm), we will finish this ideation stage before end of March.

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)