Blueprint assignments for “3.0”
This listing shows the assignment of work for blueprints currently associated with 3.0. 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 → 9 of 9 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 4 High | Incoming Event Data Feeds | 4 Discussion | 1 Not started | |||
| 4 High | Refactor Group App to Multitable Inheritance | 4 Discussion | 1 Not started | |||
| 3 Medium | Restrictions on Access to Event Information | 4 Discussion | 1 Not started | |||
| 3 Medium | Users Booking into Events | 4 Discussion | 1 Not started | |||
| 3 Medium | Personal Calendar. | 4 Discussion | 1 Not started | |||
| 3 Medium | Registration More Usable and Sensible | 4 Discussion | 1 Not started | |||
| 3 Medium | Sharing of Data Between Installations | 5 New | 0 Unknown | |||
| 3 Medium | Consume and Provide OpenID | 5 New | 0 Unknown | |||
| 2 Low | Automated Minification of Media | 5 New | 0 Unknown |
| 1 → 9 of 9 specifications | First • Previous • Next • Last |
