We appreciate bug reports, always. But when we get them, it's always nice to be able to read it and understand the bug. And, while it may not usually seem that way, the developers are familiar with the project's history.

Everyone here that could possibly care about a bug already knows what the edit queue is, when it came into being, how it works, and who wrote it. There is no need to dedicate most of your bug report to what amounts to a history lesson for historians.

Amongst all this, it was difficult to even find the purpose. I had to read it twice just to realize it was a bug report for the edit queue. Even then, you don't specify what version of Scoop this affects, nor are there clear steps to reproduce. I assume you mean whatever version is currently on K5, since you mention it.

The biggest problem I see with this, however, is the air of smugness spread throughout it. As I read it, I got a feeling that you were trying to say, "Look at this bug I found. You're all idiots! I spit at your feet!" I, personally, don't appreciate that, and I'm sure the other developers don't. We're all volunteers here, and we put a lot of effort into Scoop because we like the project, and we would like to see it improve and succeed. But there's only so much time that we can put into it.

Of course, all of that really doesn't matter, because the bug report hidden somewhere in this story is for a bug that was fixed a month ago. theantix, who single-handedly wrote the edit queue code, submitted a patch for it to address a few problems, and to add some things. I noticed the bug, and let him know about it. He promptly fixed it, checked it out, and sent me a fresh patch. And I'm sure that he hit himself in the head for it enough that no one needs to help.

In the future, if you find a bug, we'd love to hear about it. We'd like nothing better than to squash all the bugs in Scoop. However, when you (or anyone else!) submit a bug report, try to do completely different than how it was done here.