Planning 3 0 1
From Ekiga
Rule: The more GREEN, the better. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XX
- Green: Ready for 3.0.1, currently 0%
- Blue: Work In Progress (WiP), currently 0%
- Grey: TODO, currently 0%
- orange: Postponed, currently 0%
| No | Feature | Why? | Status | Due to... | Assigned to | Deadline
(Postponed the) | tested the... | Comment |
|---|---|---|---|---|---|---|---|---|
| 1 | Page 5/7 of the assistant, there is no more "test buttons" for the audio. Replace with Test call to 500@ekiga.net | Feature Regression | Postponed | 3.1 | Damien? | Not implemented 2008-20-07 | or automatically add 500 and 501 to the roster
Snark: what about some words at the end of the assistant, to explain that they should try 500@ekiga.net [only if they have an account?] | |
| 2 | The Address book window allowed to group and drag'n drop contacts, with 2.9, contacts are much more proeminent -thanks to the roster- but you can not anymore use drag'n drop. | Feature Regression | TODO | 3.1 | Waiting Someone | Not implemented 2008-20-07 | Hard to do in the given time | |
| 3 | Common actions should have a button (like the text chat) | Feature Regression | WIP (answer needed) | 3.0 | Snark | A tool bar is added at the bottom of the roster 2008-08-01 | Buttons for main actions: the the ShortMenuBuilder class makes it easy adding short toolbars, ie: buttons for main actions. See lib/engine/framework/menu-builder-tools.h ; so the basic code is there -- the UI just needs some love ; notice that since the roster view emits a "presentity-selected" signal, things should be pretty easy. The question is : where do we want this toolbar!?
Yannick: Do we agree to get this toolbar always visible next to each contact in the roster? Which means if you have e.g. 10 contacts in the roster, you'll have 10 minitoolbars, next to each of them. | |
| 4 | Is Do Not Disturb the same as the old "Busy mode"? | Feature Regression | WiP | 3.0 | Damien | Not implemented 2008-20-07 | ||
| 5 | Reregistering of accounts for which the registration failed when a new interface pops up <=> When an interface is added, the listeners are updated, but subsequent REGISTER requests are not sent using the newly added interface | Damien want it | WiP | 3.0 | I start Ekiga without any interface active. Then I activate the wifi. It seems it can not register, because there are DNS issues. (19-08-2008) | |||
| 6 | With all codecs enabled, one can not call 500 | Damien wants it | Postponed | 3.0 | SIP should support TCP, Ref: http://bugzilla.gnome.org/show_bug.cgi?id=544209 | |||
| 7 | User Documentation | Mandatory | WiP | 3.0 | Yannick | cf. http://wiki.ekiga.org/index.php/Documentation |
