| | 1 | = Support Response Tips = |
| | 2 | |
| | 3 | Priorities of support: |
| | 4 | |
| | 5 | 1. Maintain the shared infrastructure |
| | 6 | 1. Help and teach people how to use the shared infrastructure |
| | 7 | 1. Teach and empower people to be self-sufficient with free and open source technology |
| | 8 | |
| | 9 | Except with regard to priority 3 above, support is not intended for: |
| | 10 | |
| | 11 | * Fixing people's web sites |
| | 12 | * Fixing people's local area networks or broken local email clients, etc |
| | 13 | |
| | 14 | Useful tips: |
| | 15 | |
| | 16 | * Most questions are variations on questions that have already been asked. Be sure to check the [wiki:faq] and do a search of the site. Searching the entire site may turn up similar tickets providing ideas on how to answer |
| | 17 | * Check the "Reported By" field. If you see an email address (it will be displayed in an obscured way, like {{{joebob@...}}} then it means the poster did not login, which means they will not see a comment box, which means they won't be able to respond. If you are asking them for more information, be sure to point out that they will need to login to respond and remind them that they can use their ssh/sftp or email user/password to login to the support site. |
| | 18 | * If the poster does not identify the server they are working on or any other information that would make it easier to debug, don't be shy about asking |
| | 19 | * Whenever possible, teach. It's not our job to fix people's web sites and teaching people how to fix their own websites is our last priority. |
