| 5 | | However, this ticket tracking system can be very daunting! There are a wide variety of issues, many of which are at a very high technical level. Sorting through the tickets to find one that you might be able to help with can be very overwhelming. |
| | 5 | To help you help other members - we've written a few guidelines: |
| | 6 | |
| | 7 | * Before beginning to answer a question, scroll to the bottom and click the Accept radio button (and, of course, be sure nobody has already accepted the ticket). |
| | 8 | * Post comments as you go. Even if you can't figure out how to solve the problem, posting what you've done can be tremendously helpful. |
| | 9 | * If you run a command that gives output - copy the entire command, output of the command, and the final command prompt (to indicate to everyone that the command completed). |
| | 10 | * If you do any web searching related to the issue - include any relevant links even if they don't fully explain what is going on - they may trigger ideas for the next person. |
| | 11 | * If you have root on a box and you are trouble shooting a server-wide problem, consider running mf-analyze-server - that script will run a series of tests and store the output of those tests for later viewing. Even if you have no idea how to fix the problem, running this command leaves a helpful trail for the next person. |
| | 12 | |
| | 13 | There are a wide variety of issues, many of which are at a very high technical level. Sorting through the tickets to find one that you might be able to help with can be very overwhelming. |
