TPEPlatform

Billboard

• This page is obsolete. See Individual team's portal below.
• TPE Platform team open issues
• How to arrange engineer resource more efficiently
  • Due date: 9th May
  • How to setup search criteria in each team to let engineer notices important bug on bugzilla more efficient.
  • KPI for each team. Have an internal discussion in each team, define how to process KPI in a reasonable way for each team

• Individual team's portal
  • Taipei Graphics Team
  • Taipei Media Recording Team
  • Taipei Platform Team

• 今日豪語
  • おピーターさま: 勇敢take issue. For exp, bug 997367. ㊙ それは俺のやる気だ！
  • おChiajungさま: ㅎㅎ学業賞は5回だ！
  • 新米TY: 顆顆 偷偷take bug居然被發現了 XD

• Team chatting room
  • IRC: taipei-platform on MozNet

• New hired info
  • New hired need to know
  • Here are things that we think new member should know.
  • Everyone in team has the responsibility to maintain the correctness and availability of these documents.

• Bug dashboard

Developer's friend

• Debugging OOM

CJ: I hope we can more utilize this section. Any suggestion is welcome.Basic idea is each member can be easily to access team information from this portal by less than two URL redirect.

EPM Section

Firefox OS General Information

• Graphic for Firefox OS backlog meta bug 1016870
• Multimedia Platform backlog meta bug 912380
• Functional team planning doc
  • SystemPlatform, MultimediaPlatform, webRTC, Graphic Planning
  • This is the Google sheet for our function team internal sprint tracking
• Firefox OS Product Roadmap
  • Product Roadmap Wiki
  • Key focus/feature on every Firefox OS release version
• Release management schedule: Release version/schedule
• Release Dashboard: Blocker bug dashboard
  • Dashboard for the blocker bugs of Firefox OS, grouped by components

Functional Team Agile Process/Practice

• Multimedia Platform/WebRTC Functional Team Info and Sprint Tracking Wiki

Story Points, Target Milestone and ETA

• What's Story Point?
  • It is the effort estimation in Agile way.
  • 1 point means approximately 2 working days.
  • By using Fibonacci Number, the story point will be a number in "1, 2, 3, 5, 8, 13" (Actually 13 is not recommended unless you really have to)
• How to apply Story Point?
  • Put in whiteboard, format: [p=2]. When you first got the ticket & after a quick estimation.
  • The efforts shall include "unit test", "getting review+", "landed".
  • When closing a bug, you may make correction to the p to reflect actual efforts.
  • p means "the effort you spent", NOT "how long the ticket is closed". For example, you're assigned a bug on Monday, but you wait and start working on it Thursday and Friday then done, p should put as 1, not 3.
• Target Milestone
  • There is a filed in bugzilla called target milestone. Every milstone is in 2 weeks basis. When doing the sprint planning, this filed has to be assigned an milestone to indicate the bug is planned to be done in the given sprint.
• ETA
  • Sometimes for the urgent blockers or overdue bugs, the ETA will be required so that the stakeholders will know when the bug is expected to be fixed.

Firefox OS 2.0 Information

• 2.0 Schedule by Sprints
  • Development Phase
    • Sprint 1 (4/28/2014 ~ 5/9/2014)
    • Sprint 2 (5/12/2014 ~ 5/23/2014)
    • Sprint 3 (5/26/2014 ~ 6/6/2014) -->Feature Landing (Was Feature Complete)
  • Stabilization Phase
    • Sprint 4 (6/9/2014 ~ 6/20/2014)
    • Sprint 5 (6/23/2014 ~ 7/4/2014)
    • Sprint 6 (7/7/2014 ~ 7/18/2014) -->Feature Complete (Was Release To Partner (RTP))

Firefox OS 2.1 Information

• Graphic for Firefox OS 2.1 Feature Meta bug 1016796
• 2.1 Schedule by Sprints
  • To be updated

Regular Meeting

• Team weekly meeting
  • Location: TPE 5A- Blue Mountain
  • Time: Thursday, at 3:00 PM Taipei time
• Media team weekly meeting
  • Location: TPE 5A- Blue Mountain
  • Time: Wednesday, at 3:00 PM Taipei time
• Gfx team stand up meeting
  • Location: working area
  • Time: 11:00 AM each day
• Platform team weekly meeting
  • Location: mocha
  • Time: Tuesday, at 3:00 PM Taipei time

Team Organization

Blockers

• Blocker dashboard

Bug Statistic

Diagram 1 is a bar chart to reveal owned issues of each engineer.

Diagram 2 is pie chart which describes categories that we are working on.

Table 1 lists all dead issues which have no activity at all for a long time. Please take action, CPR or anything help, don't just let them die...

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Weekly Report

Rule of thumb

Here is the basic rule of weekly report style.

Format of a working item
===={PIC}====
* {bug number} - {bug title}
** {Status code}
** Comment 1
** Comment 2
** etc..
Example:
====CJKu====
* bug 951044 - [MediaEncoder::GTest] Implement unit test of VP8 video track encoder
** WIP 
** Reviewer take a vacation. No progress in this week
** I want to take a vacation as well.

Status code:

• OOAD: In analysis or design phase.
• WIP: Working on WIP patch.
• feedback(F): Give feedback to a patch
• feedback?(F?): Ask feedback.
• feedback+(F+): Get positive feedback.
• feedback-(F-): Get negative feedback.
• review(R): Review a patch.
• review?(R?): A patch is under review
• review+(R+): Get positive review.
• review-(R-): Get negative review.
• land(L): A patch have been check in.
• debug(D): Activities of figure out the root cause of a bug, try to repro that bug, etc...
• file: Find out a bug and file it.
• PTO: Take personal leave
• study(S): Spend time on domain knowledge study, such as multimedia transport technology, compress format, real-time rendering.
• interview(I): Find talents for team.
• presentation(P)
  • 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
** R+|R?

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)
** land(1.3|1.3T)

Weekly status catalog