TPEGFX/2015-04-09

From MozillaWiki
Jump to: navigation, search

Weekly Report

Boris Chiou

  • bug 1144012 - Wrap HAL code from HwcComposer2D
    • WIP | f?
    • Remove all Android version in HwcComposer2D
  • Webide related topic
    • study
    • Remote Debugging Protocol
      • Javascript debugger, wedide related protocol
  • C++11
    • study
    • For refactoring

Chiajung Hung

  • bug 1146214 Refactor fence delivery to reduce ipc messages and code duplication
    • OOAD
  • bug 1118139 [FFOS7715 v2.1] [dolphin][Youtube video] 7715 FFOS shows black screen on launching some video, while audio can be heared while using Youtube app or Youtube site
    • OOAD
  • bug 1149923 [Flame][Search] The search bar becomes a rectangle when you switch device to landscape mode.
    • Test
    • Try m-c/2.2 local build + PVT build, can not reproduce.
  • Layout study
    • CSS spec

Ethan Lin

  • bug 1146214 - Refactor fence delivery to reduce ipc messages and code duplication
    • WIP
  • The flow of BuildContainerLayerFor
    • study

Jeremy Chen

  • bug 1152263 - [Messages][Text Selection] Hard to drag the caret when there is an attachment in the beginning of a message
    • file
  • Clipboard Web API

Jerry Shih

  • bug 1148718 - [Nexus5] The video preview is grey.
    • r+ and land
    • Layer attach timing issue for async video case.
  • bug 1149492 - Handle the duplication of fd for thread link
    • r-
    • need discuss with bent.
  • N5-L vsync-rd problem
    • debug

Morris Tseng

  • PTO

Tingyu Lin

Peter Chang

  • bug 1144990 - Dump display items with class id and name
    • r?
  • bug 1127170 - Layer transaction spends more than 150ms when switch app
    • wip
    • Remore the canvas padding in bottom for icon to make no overlap between icon and text

Team

   Q2
     performance improvement(include gaia tool)
     sharing to tw-all
     Orientation API
     Multiple screen/TV Overlay
     refactor/testing
     personal work sharing in work week
   Feedback
     How to work on new area/module
       Search for mentor/crash bug
       hackathon event for gfx/perf/layout(copypaste)
     Cross team communication
     How to prompt engineer work

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)