Blueprint assignments for “OpenKeys”
This listing shows the assignment of work for blueprints currently associated with OpenKeys. 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 | OpenKeys API 0.8 | 3 Drafting | 5 Started | Dominik Fuchs | Dominik Fuchs | OpenKeys Team |
| 4 High | OpenKeys common library code | 3 Drafting | 3 Needs Infrastructure | Dominik Fuchs | Dominik Fuchs | OpenKeys Team |
| 3 Medium | Apple Keychain backend implementation | 5 New | 1 Not started | OpenKeys Team | ||
| 3 Medium | Gnome Keyring backend implementation | 5 New | 1 Not started | OpenKeys Team | ||
| 3 Medium | Kwallet backend implementation | 5 New | 1 Not started | OpenKeys Team | ||
| 3 Medium | File-based backend implementation | 5 New | 1 Not started | OpenKeys Team | ||
| 2 Low | KeepassX backend implementation | 5 New | 1 Not started | OpenKeys Team | ||
| 1 Undefined | OpenKeys API 1.0 | 5 New | 0 Unknown | OpenKeys Team |
| 1 → 8 of 8 specifications | First • Previous • Next • Last |
