| | 1 | |
| | 2 | |
| | 3 | Anyone who is a member of the group can do the following items. |
| | 4 | |
| | 5 | Here is a typical workflow: |
| | 6 | 1. Experimenter sends a question to geni-experimenters@googlegroups.com |
| | 7 | 2. Hopefully someone from the community will respond. |
| | 8 | 3. If no one responds in a timely fashion or if the question has a clear "right person" to answer, someone (probably a moderator) assigns email to an appropriate person via the web interface. |
| | 9 | 4. Assignee gets email asking them to answer the message. |
| | 10 | a. If assignee is willing to respond, assignee responds (via email or web interface) |
| | 11 | b. Otherwise, assignee reassigns to someone else |
| | 12 | 5. Once the thread dies down, someone (probably a moderator) marks the thread "Completed" (via the web interface) |
| | 13 | |
| | 14 | At any time: |
| | 15 | * Anyone who is a member of the group, can add tags (selecting from existing where appropriate) via web interface |
| | 16 | * In addition to marking threads as "Completed", anyone can mark them as "Duplicate" or "No action needed". This does not generate email, so you still need to reply to the experimenter. |
| | 17 | |
