-
Notifications
You must be signed in to change notification settings - Fork 0
/
TODO
173 lines (140 loc) · 4.87 KB
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
Introduction
============
The follow list are features still to be implimented in the dialer application.
Each entry has the fields:
- <brief description>
Details: As much info as is needed to understand the purpose, complexity,
impact and dependancies of the feature. The goal being to allow
those interested in helping to determine if they have the
knowledge and time to do so.
Priority: An indicator of the project perceived urgency for implementation.
Values are: Low, Medium, High
Complexity: A estimate of the difficulty to implement or potential impact to
the rest of the project.
Values are: C1, C2, C4 and C8 (See "What is Complexity?" below)
BMC#: Bugzilla id from bugs.meego.com (optional, but recomended)
Owner: Who has accpted (or been assigned to) the task
What is Complexity?
==================
First, I am borrowing this from the Ofono project, so if you are familiar
with how they use it, it is the same here.
Complexity scale: C1, C2, C4 and C8.
The complexity scale is exponential, with complexity 1 being the lowest
complexity. Complexity is a function of both task 'complexity' and task
'scope'.
The general rule of thumb is that a complexity 1 task should take 1-2 weeks
for a person very familiar with oFono codebase. Higher complexity tasks
require more time and have higher uncertainty.
Higher complexity tasks should be refined into several lower complexity tasks
once the task is better understood.
===============================================================================
TODO:
Dialer Features
---------------
- Add event feedback (haptic, audio, other)
Details:
Priority: Low
Complexity: C1
BMC#: BMC#2661
Owner: Shane Bryan <[email protected]>
- Add Advice Of Charge (Cost) to all call views
Details:
Priority: Medium
Complexity: C1
BMC#: BMC#2658
Owner: Shane Bryan <[email protected]>
- Multi-party call capabilities
Details:
Priority: High
Complexity: C2
BMC#: BMC#550, BMC#2806
Owner: Shane Bryan <[email protected]>
- Volume up/down and Mute
Details:
NOTE: Depends on Audio routing integration
Priority: High
Complexity: C2
BMC#: BMC#2809
Owner:
- User Determined User Busy
Details:
Priority: Medium
Complexity: C1
BMC#: BMC#2794
Owner:
- Explicit Call Transfer
Details:
Priority: Medium
Complexity: C1
BMC#: BMC#2803
Owner:
- Private Conversation during multi-party call
Details:
Priority: Low
Complexity: C4
BMC#: BMC#2807
Owner:
- Split Multi-party call
Details:
Priority: High
Complexity: C2
BMC#: BMC#2808
Owner:
- Auto redial / Call Completion to Busy Subscriber
Details:
Priority: Medium
Complexity: C2
BMC#: BMC#2804
Owner:
- Support of Emergency call w/ and w/o SIM
Details:
Priority: Medium
Complexity: C4
BMC#:
Owner:
- Integrated hands-free
Details:
Priority: Low
Complexity:
BMC#:
Owner:
System Interaction tasks
------------------------
- Ringtones associated per contact
Details: Should be able to set/get a ringtone for each contact. This
is mostly a requirement on libseaside, but dialer will need to
determine if, for an incoming call, the contact associated with
the lineid has a ringtone preference set, and use it instead of
and defaults if so
Priority: Medium
Complexity: C4
BMC#: BMC#2661
Owner:
- Call settings UI
Details: A settings plugin for letting the user see (and change
when allowed) the various dialer and ofono settings
Priority: High
Complexity: C2
BMC#:
Owner:
Misc other tasks
----------------
- Migrate to using libofono-qt
Details: With the maturing of libofono-qt, we need to standardize
upon it's API rather than our own local introspected XML
interface proxies.
Priority: High
Complexity: C1
BMC#: BMC#18701
Owner: Shane Bryan <[email protected]>
- Refactor debug output
Details: The debugging output of dialer is crude, simplistic and
prone to inconsistent use by different contributors.
We need a filterable and formalized set of debugging
functions/macros that make this simple to use as both
a developer writing new code, and dev/QA/user trying to
root cause an issue or understand how dialer works
Priority: High
Complexity: C1
BMC#:
Owner: