[h1]Moderating forums[/h1]
In the CF Support forums (eg Report Bugs, Suggest New Features), we will respond to member question to the best of our ability or try to find the answer from the relevent Admins or Erwin.
[h2]Closing threads[/h2]
At our discretion, we will close the thread when the problem is solved, or question answered. This is to help those administrative staff members the ability to quickly find the threads that require their attention. We encourage members to post if their bug is fixed, or question adequately answered.
[h2]Similar posts[/h2]
If we receive multiple reports of the same bug, we may choose to close all but one of them, leaving a link to the active report in the closed one. We may also edit the title of the post to enable members and administrators to quickly assess all the posts on the page. Again, this is purely for efficiency.
We encourage members to check to see if their bug has already been reported, and then to post on that thread. It is useful to hear from any member that is experiencing a problem, so that we can gauge the nature and extent of the problem.
[h2]Moving threads[/h2]
At our discretion, we may move threads that we feel are more appropriate to a different CF Support forum. If we do this, we will leave a one-week redirect in the original thread.
[h1]Report handling[/h1]
We will assess each report against the current CF rules to determine whether the post breaks any of these rules. If we determine by team consensus that there is a violation, we will then determine what we will do with the post. This means we will decide whether to edit (either RFE or staff edit), delete, or move the post. When this work is complete, we will explain to the member via PM.
Members are free to read the public Support reports threads. They may comment in report threads if they have some clarification to add to the discussion about whether the posted report is a violation or not. However, further attacks, personal discussions, or continuation of the argument from the reported thread are NOT acceptable and will be deleted from the report thread at the moderators discretion. Discussion of other posts should be only take place when needed in order to add context to the reported post.
While reaching a consensus is important, at this time there are no set definitions of a consensus, for the purpose of reports. Both staff and member opinions will be taken into consideration when deciding whether or not the post breaks a rule, and what steps to take.
There is a statute of limitations of two weeks (fourteen days). In other words, if no decision is reached and initial staff action taken by that time, the report should be closed and the post left unacted upon.
[h1]Thread Cleanup[/h1]
When a thread becomes unproductive and is producing several reports, we may elect to close the thread for review and cleanup. We would announce this via a mod-hat in thread, giving a brief explanation of the problem. During cleanup, we delete any bad post (and posts that quote a bad post), and use a single automated PM to serve as notice. Further explanation and guidelines for the thread can be given via mod-hat when the thread re-opens.
If there is nothing salvageable, we may decide to leave the thread closed after cleanup, and this would be explained in a mod-hat.
[h1]Chat Box Rules[/h1]
4. Chat Box Rules (in CF Rules and FAQs)
Wiki: Chat Box and IRC Rules (Link is Wiki, not the rules of Chat Box, but place to edit and discuss future revisions.)
In the CF Support forums (eg Report Bugs, Suggest New Features), we will respond to member question to the best of our ability or try to find the answer from the relevent Admins or Erwin.
[h2]Closing threads[/h2]
At our discretion, we will close the thread when the problem is solved, or question answered. This is to help those administrative staff members the ability to quickly find the threads that require their attention. We encourage members to post if their bug is fixed, or question adequately answered.
[h2]Similar posts[/h2]
If we receive multiple reports of the same bug, we may choose to close all but one of them, leaving a link to the active report in the closed one. We may also edit the title of the post to enable members and administrators to quickly assess all the posts on the page. Again, this is purely for efficiency.
We encourage members to check to see if their bug has already been reported, and then to post on that thread. It is useful to hear from any member that is experiencing a problem, so that we can gauge the nature and extent of the problem.
[h2]Moving threads[/h2]
At our discretion, we may move threads that we feel are more appropriate to a different CF Support forum. If we do this, we will leave a one-week redirect in the original thread.
[h1]Report handling[/h1]
We will assess each report against the current CF rules to determine whether the post breaks any of these rules. If we determine by team consensus that there is a violation, we will then determine what we will do with the post. This means we will decide whether to edit (either RFE or staff edit), delete, or move the post. When this work is complete, we will explain to the member via PM.
Members are free to read the public Support reports threads. They may comment in report threads if they have some clarification to add to the discussion about whether the posted report is a violation or not. However, further attacks, personal discussions, or continuation of the argument from the reported thread are NOT acceptable and will be deleted from the report thread at the moderators discretion. Discussion of other posts should be only take place when needed in order to add context to the reported post.
While reaching a consensus is important, at this time there are no set definitions of a consensus, for the purpose of reports. Both staff and member opinions will be taken into consideration when deciding whether or not the post breaks a rule, and what steps to take.
There is a statute of limitations of two weeks (fourteen days). In other words, if no decision is reached and initial staff action taken by that time, the report should be closed and the post left unacted upon.
[h1]Thread Cleanup[/h1]
When a thread becomes unproductive and is producing several reports, we may elect to close the thread for review and cleanup. We would announce this via a mod-hat in thread, giving a brief explanation of the problem. During cleanup, we delete any bad post (and posts that quote a bad post), and use a single automated PM to serve as notice. Further explanation and guidelines for the thread can be given via mod-hat when the thread re-opens.
If there is nothing salvageable, we may decide to leave the thread closed after cleanup, and this would be explained in a mod-hat.
[h1]Chat Box Rules[/h1]
4. Chat Box Rules (in CF Rules and FAQs)
Wiki: Chat Box and IRC Rules (Link is Wiki, not the rules of Chat Box, but place to edit and discuss future revisions.)
