Blueprint assignments for “trunk”
This listing shows the assignment of work for blueprints currently associated with trunk. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.
| 1 → 8 of 8 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 5 Essential | Re-factoring of OSCAR protocol realization | 7 Obsolete | 0 Unknown | |||
| 4 High | ActionGenerator API improvements | 5 New | 7 Good progress | Ruslan Nigmatullin | Ruslan Nigmatullin | Ruslan Nigmatullin |
| 4 High | qutIM Jabber support | 7 Obsolete | 11 Implemented | |||
| 4 High | qutIM plugins support | 7 Obsolete | 0 Unknown | NeiRo21 | NeiRo21 | |
| 4 High | Implementing of profile system | 7 Obsolete | 0 Unknown | |||
| 3 Medium | Proxy Support | 5 New | 7 Good progress | Alexey Prokhin | Vsevolod Velichko | Ruslan Nigmatullin |
| 3 Medium | Support of adium Contact List themes in qutIM | 7 Obsolete | 11 Implemented | |||
| 3 Medium | Re-factoring of contact list implementation | 7 Obsolete | 0 Unknown | Daemon |
| 1 → 8 of 8 specifications | First • Previous • Next • Last |
