TPESystem: Difference between revisions
Jump to navigation
Jump to search
Line 6: | Line 6: | ||
#*Module Peer: Gian Yeh | #*Module Peer: Gian Yeh | ||
#*Module Members: Shawn Huang, Ben Tian | #*Module Members: Shawn Huang, Ben Tian | ||
#*A2DP/AVRCP | |||
#**Gina Yeh | |||
#***A2DP | |||
#***AVRCP 1.0/1.3 | |||
#*HFP 1.6 | |||
#**Ben Tian | |||
#*Bluedroid Porting | |||
#**Shawn Huang | |||
#*Web APIs | |||
#**Eric Chou | |||
==Weekly status== | ==Weekly status== |
Revision as of 03:16, 15 July 2013
Resource Deployment
Resource deployment on the active work.
- Bluetooth:
- Module Owner: Eric Chou
- Module Peer: Gian Yeh
- Module Members: Shawn Huang, Ben Tian
- A2DP/AVRCP
- Gina Yeh
- A2DP
- AVRCP 1.0/1.3
- Gina Yeh
- HFP 1.6
- Ben Tian
- Bluedroid Porting
- Shawn Huang
- Web APIs
- Eric Chou
Weekly status
Rule of thumb
Here is the basic rule of weekly report style.
Format of a working item * Media Encoding Framework bug 879688 << level 1: abstract name, append META bug number if we have ** Encoding framework bug 842243 / Shelly << Level 2: more specific/ individual task, append bug number and PIC *** review: all patch get review+ << Level 3: item status, and comment
Keyword of item status
- Analysis: a developer is still collecting information and knowledge for assigned topic
- Design: a developer is constructing feature architecture or testing framework of assigned topic
- Implementation: a developer is starting programming activity.
- Review: finished most implementation and ask for review from domain expert. Status may go back to "implementation" or "design" if big architecture change is required.
- Fixed/ Suspend/ Wontfix: this feature is done. Suppose this item will not appear in the next weekly report.
- Debug: for a item which is essentially a bug.
If you write a technical blog or anything relative to work, it's welcome to share it on weekly report.
Weekly status catalog
2013 Q3 | 2013 Q4 |
---|---|