Line 35: |
Line 35: |
| | | |
| === Coordinator === | | === Coordinator === |
| + | |
| + | Coordinators are appointed to filter all incoming requests to: |
| + | * find out duplicates |
| + | * tweak request properties e.g. if requester is not experienced in some cases |
| + | * set priority, deadlines and schedules |
| + | * could appoint/invite contributors |
| + | |
| + | Each group of users should have one or several coordinators. Every subgroup inherits coordinators from parent group e.g. group of school users will inherit area and global coordinators. |
| + | |
| + | Possible workflows: |
| + | |
| + | * login to coordinator mode |
| + | * check incoming queue of newly created requests |
| + | * accept/retain/deny/tweak new requests |
| + | * inspect deadlines/schedules of ongoing requests |
| | | |
| === Contributor === | | === Contributor === |