Drigg asks the Drigg community for help -- please read this!

Hello People,

As you know, I have been working tirelessly on Drigg. I released Issue 1 thinking that I would have a break after that... little did I know, that Drigg had countless little glitches which caused you people a lot of stress and a lot of work.
Some of them were pretty much impossible to predict. Some of them were plain silly.

Now... I need help. If you go here:

• Submissions for Drigg

Now, I could do with some help. The problem is that a lot of requests were actually coming from people who had misconfigured Drigg. Those cases are really, really time consuming for me. I haven't written a single line of code over the last week, for this reason,

So... I changed the Bug Report page ( http://www.drigg-code.org/pages/bug_reports ), which now reads:

--------------------------------
1. Ask the Drigg community first in Drigg's forums.

A lot of questions can be answered in the forums, where community members help each other. Unless you are absolutely dead sure it's a bug, please ask your fellow members first. If nobody knows, then it's probably a bug.
--------------------------------

Basically, I would love to see the forums as the first step... if you guys can help people out, that's great. If you see that there's actually a problem, then you could either submit the bug for the user, or tell them to submit a bug confirming that there's probably one.

Do you think this would work?

Basically, I'd be delegating the initial contact with the problem. Once the problem is confirmed, you can either write precise instructions to reproduce it on a drigg-distr.tgz distro and submit it (I would love you for it!), or get the person to submit it.

A perfect example is this one: http://www.drigg-code.org/node/29 . Anybody with basic Drupal/Drigg knowledge should be able to answer it.

I hope the work I did for this module earned your trust and respect, and that you are able to help us out in this project.

Bye!

Merc.