TPE-Layout/2016-07-26

Weekly Report

Shing Lyu

• Done
  • Studying Servo flexbox status
  • Read flexbox spec
  • Update #11107: Bug 10452 - Page Load Time Test Runner
  • Write WebRender overview wiki and trace the code

• WIP
  • Enabling reftests on Stylo

Tingyu Lin

Shape-outside

• bug 1288626 - Add shape-outside support to the style system
  • file | r?

Layout

• bug 1277129 - rename nsHTMLReflowState and nsHTMLReflowMetrics to ReflowInput and ReflowOutput
  • land
• bug 1288992 - Rename nsHTMLReflowMetrics variables to ReflowOutput
  • file

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)