Blueprint assignments for “dSM”
This listing shows the assignment of work for blueprints currently associated with dSM. 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 → 6 of 6 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 4 High | Reliable message transfer between peers | 0 Approved | 1 Not started | dSM Core Team | ||
| 3 Medium | Service synchronization to new peers | 0 Approved | 1 Not started | dSM Core Team | Vincent Verdot | |
| 3 Medium | Enable multiple jxta interfaces handling | 3 Drafting | 1 Not started | dSM Core Team | ||
| 3 Medium | Porting dSM to android architecture. | 4 Discussion | 2 Deferred | dSM Core Team | ||
| 3 Medium | Optimizing the Java P2P API. | 4 Discussion | 1 Not started | Vincent Verdot | ||
| 2 Low | Same-device service transfer | 4 Discussion | 0 Unknown | Abderrahmane |
| 1 → 6 of 6 specifications | First • Previous • Next • Last |
