Policy on Locking Threads???

[MjrNuT]

Pardon me,

But does the moderation team have a policy on locking threads at all?

I have found the following updated rules, which I was quite happy to see when implemented. I think it helps to a certain extent.

This thread was put into a number of forums.
http://forums.srcds.com/viewtopic/10516

http://forums.srcds.com/viewtopic/10412

Reason I'm asking is that Mr. realchamp has graciously locked a thread in the Tutorials forum: http://forums.srcds.com/viewcat/11

Not trying to pick a fight, but tutorials are almost never out of date and the thread that I replied to (where I was completely aware of the last post date) was done intentionally. Locking the thread and your response of implying some cutoff date to bump a thread for the reason is quite inadequate in my opinion.

I'm not trying to pick a fight and maybe you were hasty there realchamp, but of the same token you as a moderator would do better to elaborate on your reasons and such I'm requesting that you provide what the Policy is for BUMPING "older" threads. I think that is viable for all the members here to know so that they can avoid having threads locked, whether by their accidental or intentional post.

If there is already a policy and I have just missed it, then please link me and ignore my thread.

Respectfully,

[Beaverbeliever]

Sometimes there really isn't a rule for a certain time period, it all depends on the circumstances. I agree with realchamp, as well as any other moderators judgments when it comes to locking old threads. It helps keep the forums nice and tidy as well.

The reason yours was locked because you opened a thread 13 months old and just said that it was great. Just because it is locked, it still remains readable, as well as a resource to those who utilize the forums. I don't see any problem in locking that thread in this case.

For those who don't know, this thread is the one MjrNut is questioning.

[Mooga]

That was a mistake. I'll fix that for you
Old threads are generally locked because they are repeats or irrelevant. I'm unlocking it now

[realchamp]

Mooga Wrote:That was a mistake. I'll fix that for you
Old threads are generally locked because they are repeats or irrelevant. I'm unlocking it now

That's why I locked it.

Also because you said it were a bad guide and to stop a discussion in there, I locked it immediately. But thanks for post, I might want to put in a reason next time, my bad!

Beaverbeliever Wrote:The reason yours was locked because you opened a thread 13 months old and just said that it was great. Just because it is locked, it still remains readable, as well as a resource to those who utilize the forums. I don't see any problem in locking that thread in this case.

I do agree. But I should have had a reason in there.

[MjrNuT]

Mooga,

Thanks for the professional reply and worthy explanation. Note that your explanation of categorizing "old threads" is quite general. I can see that applied elsewhere, but I don't see that in the Tutorials section.

That section by my interpretation is an area that is never outdated. The stuff works and the topic in question certainly is NOT out of date. It gives a great explanation, albeit at a slightly higher level, of explaining networking...which to be fair is 90% of the issues tackled here. "how come my SRCDS blah balh not working?!?!?"

To say that was a BAD guide is completely false. It's one reference that people can use among the many others. Did you even try it realchamp to make such a judgement?

Bottomline, Locking threads needs to be done with some care no matter what it is. You have alot of eyes here to receive support. The aim is to provide that support in whatever means possible. You can send the wrong message for some cases by locking threads, followed by poor reasoning.

Lastly, you really should consider a policy about what threads will be locked by timeframe, by content, or whatever. You need some criteria. It will be just as easy to link to like the stipulation on posting sufficient information to receive support.

Cheers

[realchamp]

I didn't said it were a bad guide, you said it were false and blablablablabla.. And I locked it due too I have seen several threads turning into wars, when they weren't locked immediately.

EDIT:

I should probably have posted a longer message followed by a good reason, on that area I'm sorry.

And lately, I locked it since it were like 13months old. And Munk would not come back I guess. So there would be no reason to start a discussion, unless it were a very exceptional question. Which in almost all cases it is not. However in case he would come back, I would have unlocked it.

[MjrNuT]

realchamp Wrote:I didn't said it were a bad guide, you said it were false and blablablablabla.. And I locked it due too I have seen several threads turning into wars, when they weren't locked immediately.

EDIT:

I should probably have posted a longer message followed by a good reason, on that area I'm sorry.

And lately, I locked it since it were like 13months old. And Munk would not come back I guess. So there would be no reason to start a discussion, unless it where a very exceptional question. Which in almost all cases it is not.

realchamp --

Again, not meaning to pick a fight. But allow me to try and clear something up here before it does go wrong. I don't want have a miscommunication here. I appreciate your participation and everyone will learn from this, hopefully for the better.

I have bolded your top part.

Below quote: Are you saying Monks HOW to was BAD or are you saying Mooga said it was BAD??

realchamp Wrote:That's why I locked it.

Also because you said it were a bad guide and to stop a discussion in there, I locked it immediately. But thanks for post, I might want to put in a reason next time, my bad!

MjrNuT Wrote:To say that was a BAD guide is completely false. It's one reference that people can use among the many others. Did you even try it realchamp to make such a judgement?

How does a HOW To ever get turned into a flame war? It was 4 posts long? Not one post said it was wrong or corrupt or otherwise. Drocona was the only that said it did not appeal to him, therefore everyone should silently agree with that?

Sorry man, I just want to understand where you are coming from. Again, I appreciate it and the best part is that if you lock thread, please please provide a sound reason.

[MjrNuT]

realchamp Wrote:I didn't said it were a bad guide, you said it were false and blablablablabla.. And I locked it due too I have seen several threads turning into wars, when they weren't locked immediately.

EDIT:

I should probably have posted a longer message followed by a good reason, on that area I'm sorry.

And lately, I locked it since it were like 13months old. And Munk would not come back I guess. So there would be no reason to start a discussion, unless it were a very exceptional question. Which in almost all cases it is not. However in case he would come back, I would have unlocked it.

I just saw your Edit.

NO tutorial or How To has a shelf life until the program or service associated with it has been terminated. Why do you assume Monk would not come back? Maybe he has a setting to notify email of a reply. You are the one to decide what is an "exceptional question"?

Sorry, your reasoning makes no sense at all. Maybe its just me and I'm sorry for that. The HOW to by Monk is a viable source of information. For me to post and give it kudos is one way to show that it is reasonable, not out of date, and is accurate.

I will discontinue as I did not intend for this to be strung like it was. Apologies to ppl for wasting their time.

[realchamp]

I've said in the future I'd put a reason in there, that were my fault I didn't do it.

However, I don't think you understand why I locked it. Well let's just say you have been here for like 4 months and I guess you haven't seen the same amount of flame wars as I have,m eventually in here.. To prevent yet another one, I proved a lock immediate to prevent that. As in an obligation, more likely, it's not what these forums are ment to be. It's ment as, you come and ask a question, and you get an answer. My conclusion is that, I should provided you with that information about I locked that thread(and to everybody else).

Now that I see this is already turning into a flame war, even the problem originally has been solved, by unlocking the thread. <--- Great example

And why I assumed Monk wouldn't come back, is that, since he hasn't been online since the first reply to his thread was made. Or he eventually logged in once, but he didn't do anything, that's why I assumed his not curious about his thread at this point. And then you came with more likely an useless reply for the public, so I decited to lock it. And the reply should've been either not been made or just in your brain. I don't have anything else to said, I admited my part of the mistake or more likely an omission by me. That wasn't my first priority at that point, I usually locked them, since people in here, by experince knew why. (I'm not telling you that you're unexperinced in the area of dedicated servers, but you are not used to these forums).

MjrNuT Wrote:Sorry, your reasoning makes no sense at all. Maybe its just me and I'm sorry for that. The HOW to by Monk is a viable source of information. For me to post and give it kudos is one way to show that it is reasonable, not out of date, and is accurate.

I strongly disagreed with the bolted text. I didn't said in anyway it were out-of-date or it weren't accurated to todays routers.
I ment, that you posted in an old thread - which is agianst the rules I believe - and when you do that, people will automaticly start to post a comment too, and then another comment. And when it's older, I would ratherly have you to or anybody else to post in the off-topic forum or just send him an email or PM, if it's a personally message to him. Since it's not topical for us today. But lately we have had alot of flame wars and by the experince I've in here, I locked it immediately to prevent yet another one. It could be even you there would be flamed and blamed at. As a moderater, I try to keep it fair for all peoples. And I did that by locking it immediately, however, in case Monk turned back and gave me a PM or another mod/admin one, we would ofcuase unlock it or make him create a completely new thread, if he is interesseted.

- realchamp.

[Beaverbeliever]

I agree with Realchamp locking it as I have too seen the flame wars start out of old posts. And as I said earlier, locking it does not delete it. It is still open for people to read and learn from it. People can still read it and grasp knowledge, and there really is no reason to post anything if it has sat dormant for 14 months.

I also disagree with your multiple "attacks" against our moderation team as I as well as anyone else who has been here awhile, would say how great and fast they respond to issues. We have the best moderation team of any forums I am active on, and that is a main part of the reason I stay active here, as I know I am contributing to a good environment.

My vote is to close this thread as realchamp has already apologized. Going back and forth arguing will not solve anything.

[realchamp]

Well if he would like to keep this up, then send me a private/personally/PM instead. Since this is not pertinet anymore.

Thread is locked.

reason to close thread Wrote:Problem was solved and no more to discuss.