TPE-Layout/2016-12-20

Weekly Status

Shing Lyu

Stylo

• #1323399 - Enable stylo-vs-gecko reftest (again)
• #1323404 - Fixing Stylo text render as grey issue

Servo

• Surveying the Chinese support status of Servo
• #14359 - Minor patch fixes
• #12630 - Practice reviewing

Team Affairs

• Hawaii All Hands
  • Expense should be reimbursed no later than 2/28.
• Update your Q4 goals to wiki & workday TODAY!
  • 2016 Q4 goals
  • Workday
• Seat relocation by 12/23.
  • Map
• Employee Engagement Survey
  • Survey will close on Sunday, December 25.

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)