iTGB Forum Guidelines
by Michael Perry · in iTorque 2D · 05/08/2009 (7:22 pm) · 3 replies
Please make note of the forum guidelines and instructions found below:
Remain civil. The first and most important rule for all our forums. Flame wars and threads that derail completely will be locked.
Thread Tagging. If you are posting a regular discussion or inquiry, please mark your thread with the "General Discussion" tag. This helps keep our forums clean and make it easier for users to navigate.
Post proper bug reports:
To be of maximum use to us here in the Garage, we need to have the following information included in your iTGB bug report :
Please post the completed bug to the iTGB Bug section, with the tag "iTGB 1.2 Bug" - followed by a clearly written brief description of the bug in the forum post title.
Next, follow up in the body of the post with :
1. A clear description of what you were trying to do when the problem occurred. Include reproducible steps if necessary.
2. The results you expected to have happen.
3. What actually happened? If you need to include any crash logs, etc. please feel free to do so.
4. Any relevant information such as compiler or OS version, etc. Use your judgment on this one... For example if you feel that it is a video related bug, please include your video adapter and the driver information.
5. If you have a fix for the bug - all the better. Post it in the body of post as well and enjoy the feeling of happiness that washes over you for your good deed.
We really want to try to have people stay away from posting multiple different bugs in the same thread or in any thread other than its own dedicated thread, to avoid having a huge thread that is too confusing to try to comb through. If we can keep all the bugs in the iTGB Bug section and keep each bug in its own thread, it will make it much easier to address them and get them logged into our internal bug tracker.
While not strictly enforced, the following topics could result in thread consolidation or deletion:
- ETA threads
- "Wish Lists"
- Repeat feature requests
- Repeat bug reports
- Nonsensical (read "Puppy Slapping") threads
Remain civil. The first and most important rule for all our forums. Flame wars and threads that derail completely will be locked.
Thread Tagging. If you are posting a regular discussion or inquiry, please mark your thread with the "General Discussion" tag. This helps keep our forums clean and make it easier for users to navigate.
Post proper bug reports:
To be of maximum use to us here in the Garage, we need to have the following information included in your iTGB bug report :
Please post the completed bug to the iTGB Bug section, with the tag "iTGB 1.2 Bug" - followed by a clearly written brief description of the bug in the forum post title.
Next, follow up in the body of the post with :
1. A clear description of what you were trying to do when the problem occurred. Include reproducible steps if necessary.
2. The results you expected to have happen.
3. What actually happened? If you need to include any crash logs, etc. please feel free to do so.
4. Any relevant information such as compiler or OS version, etc. Use your judgment on this one... For example if you feel that it is a video related bug, please include your video adapter and the driver information.
5. If you have a fix for the bug - all the better. Post it in the body of post as well and enjoy the feeling of happiness that washes over you for your good deed.
We really want to try to have people stay away from posting multiple different bugs in the same thread or in any thread other than its own dedicated thread, to avoid having a huge thread that is too confusing to try to comb through. If we can keep all the bugs in the iTGB Bug section and keep each bug in its own thread, it will make it much easier to address them and get them logged into our internal bug tracker.
While not strictly enforced, the following topics could result in thread consolidation or deletion:
- ETA threads
- "Wish Lists"
- Repeat feature requests
- Repeat bug reports
- Nonsensical (read "Puppy Slapping") threads
About the author
Programmer.
Associate Sven Bergström
Luma Arcade