I'm not sure I'm liking the new policing of these forums. It's good that the dupes are weeded out but some of it seems overbearing and overreaching. I've had some dupes fixed (thanks Scook) but I also have a well meaning thread deleted and one moved. I'm not impressed. Larry's banter with IK wouldn't stand a chance here today. Thanks for listening, I feel better now.
 
Rocky

Oops......This probably should have gone in the forums forum. Will this result in another move and delete?
 
Rocky

You are welcome for the duplicate removals but don't recall moving or deleting any of the threads you have created. I don't see anything wrong with having this thread here but if you want it moved to Forum Discussions I can do that for you.

I think it best be here...

Hi Rocky,


I did post you a PM and you have chosen to respond here, please let me explain what happened. I think there is some confusion as to what the problem report forums are for, this is the problem report forums, not the problem forums. I did explain this and I have also given you references to the handbook.


This is what happened:


*  You posted a new thread in software forums (unknown to me). It was a question about behaviour of a third party product which is apparently crashing Sonar.

* You then posted the exact same thread about 5 hours later in problem report forums. As there was no steps to repro, and it was more of a question that required troubleshooting or answers about a third party product, I moved the thread to the Sonar forums (toss up between this or the software forums, note at this stage I am still unaware there is another thread the software forums). You should have been PM'd automatically that the thread was moved, and I wrote an explanation in that thread.


* A member of the community pointed out in that thread that there is an identical thread in software forums which is ongoing. Now I am aware of it, so now I freeze the thread I moved (explaining the reason on that thread) and pointed it to the software forums where discussion is taking place.
 
* You then posted another thread in the problem report forums once again asking why his thread got deleted (even though it was actually moved, you should have been automatically notified, and you should have been able to read the comment I made on the thread I pointed to). So now we now have three threads about the same thing....

* I then sent you a PM explaining what happened and why in a lot more detail, and locked the thread.

* I didn't get a reply asking for further info, however I have just read this in the coffee house.

Please note the "problem report" forums is a special forums that's why threads get treated differently than other forums (please see the forum handbook), it is not the "problem forums". If you had posted in another forum it would have been treated differently. The problem report forums is a lot more managed and hands on.


Also please note the forum handbook is not altogether clear at the moment and is currently under revision. There are debates still ongoing, but it should be a reasonable idea. Finally posting duplicate threads can cause a lot of confusion.


I hope this explains the situation from my perspective at least. I'm sorry it wasn't a good experience.

Cheers...

Alex
 
(edited to supply link).

I didn't see a problems forum only a problems report forum and I had a problem to report. Perhaps the problems report forum should be renamed the bug report forum. I posted there in the hopes that one of the bakers would see it and have some helpful input. The repost had an explanation of why I reposted but that was deleted when it was moved. Any who my intention isn't to argue about it here. I'm just curious how many people are not digging the new format.
 
Rocky

bluzdog
Perhaps the problems report forum should be renamed the bug report forum.

You raise a fair point. That is something personally I totally agree with, or something similar, the name can cause confusion and it is still under discussion.... so are the processes behind this, there is some confusion that needs to be clarified by Cakewalk (some are even arguing that I'm confused). In the meantime please check the current handbook I linked to earlier, which is likely to be revised soon.
 
I guess it is early days for these forums and things will become clearer in the fullness of time, I'm really sorry it wasn't altogether clear and got trapped in the middle of a work in progress.
 
Cheers....

Okay I actually laughed out loud when I saw it reposted there. Fair enough. No harm,no foul.
 
Rocky

Again sorry, to be honest we've had two or three like this in these forums, and until some clarification happens (hopefully soon) the situation will likely continue. Apols for the confusion (you should note, you are not the only one! ).
 
Cheers...

The problem (!) with renaming it to the Bugs Forum is that most problems reported aren't actually bugs, or can't be proved to be bugs without a good session of trouble shooting first, at which point the "bug" either turns out to be user error or a fault with some other software or hardware.

The intended use goes like this...

If you don't know how to use a particular feature, ask in the Sonar forum.
If you think you know what you're doing but you're not getting the results you expected, ask in the Sonar forum.
If you're convinced you're doing it right but you're getting unexpected results, post in Problem reports. It could indeed be a problem or it could be that your expectations are wrong and it's doing exactly what your asking.
If you follow simple steps that consistently fail, and you can repeat it, post in Problem reports and see if anyone else can make it fail with the same steps.

If you've done all that and others can repeat it then it may be a bug.

All bugs are problems, not all problems are bugs in Sonar, but all problems need reporting.

A good example is the staff view. It is horrible, has been for a long time. There are all sorts of problems with it. Some of them are being reported in the problems forum. They're not "bugs" as such, the whole staff view needs a major rewrite.