Handling change and feedback

[King Kovifor]

Originally Posted by hambil

Policy is being discussed in the coders forums right now.

The thread in the Coders forum started out as a "Why remove this, I did checks" and for support. It may have morphed into a "What to do" suggestion thread, but it wasn't started by staff.

so, what do we do ?!" ... merging all these complain threads to become one big suggestion ?!". loo

[hambil]

Why should there be anything wrong with discussion policy in the coders forum? I didn't say it was the only place it could be discussed. But, certainly discussing the parts of policy that effect coders, and getting coder feedback on said policies, is valuable to do in a less chaotic environment. That doesn't mean there can't also be similar 'townhall' threads to get member input.

Here is an example of the problem I am addressing in this thread:

https://vborg.vbsupport.ru/showthread.php?t=153425

The final post comes across completely wrong. The problem stated in the thread (and elsewhere by others) is that a hack can be difficult to uninstall properly when access to it's documentation is removed. That problem was not solved. The user happened to find the file on their system, which solved their specific problem.

Ending and locking the thread that way feels like a response from someone who doesn't believe the issue is real and doesn't want to deal with it. Why not merge it into other threads with similar complaints, or at least point to other threads in which the subject is already being discussed when you close the thread?