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 → 7 of 7 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 5 Essential | The deciding ACE should be able to pass out one argument | 0 Approved | 1 Not started | Gustavo Narea | Gustavo Narea | Gustavo Narea |
| 5 Essential | Write the API documentation for PyACL | 0 Approved | 1 Not started | Gustavo Narea | Gustavo Narea | Gustavo Narea |
| 5 Essential | Support for configuration files | 0 Approved | 1 Not started | Gustavo Narea | Gustavo Narea | Gustavo Narea |
| 5 Essential | Create a logo for PyACL | 0 Approved | 11 Implemented | Gustavo Narea | Gustavo Narea | Gustavo Narea |
| 5 Essential | Groups could be members of other groups | 0 Approved | 1 Not started | Gustavo Narea | Gustavo Narea | Gustavo Narea |
| 5 Essential | Create the users' manual | 0 Approved | 1 Not started | Gustavo Narea | Gustavo Narea | Gustavo Narea |
| 4 High | Create the developers' manual | 0 Approved | 1 Not started | Gustavo Narea | Gustavo Narea | Gustavo Narea |
| 1 → 7 of 7 specifications | First • Previous • Next • Last |
