Well, as much as I hate to say it, Armand might have a point here.

While it is important to keep things in a public forum civil I think it is also important to the project and it's community to be vocal about it's good as well as bad.  One of the benefits of open source - it doesn't have to be a "buyer beware" like commercial products can sometimes be.

I have a very good idea of the developer DavidT is speaking of as I had very similiar experiences.  Luckily I found out the quality of this developers products / support before I used any of their modules in a production environment so my pain wasn't nearly as bad as DavidT's but the subscription wasn't cheap so there was some financial pain. Not to mention the frustration of those very short support emails (when you were lucky enough to get an answer at all!).

I have heard from / about many other people who have had bad experiences here and a small few who actually liked the modules. The question is whether we are doing a good thing or a bad thing by keeping mum on the developer's name???

Greg

When I first started using DNN (years ago) it seemed the thing to do was find every free module out there, and purchase others, and provide every kind of functionality possible.

That was a long time ago indeed. Now the goal is to squeeze down the number of vendors to a minimum for many reasons. Knowing you got good folk, knowing you're helping improve functionality of solid products and fewer places to go for support. Fewer folks who might affect what you are providing to your clients - good service.

Still, it's not all in one place. And we can't know the rep unless we hear it. I guess I don't see the point in the mystery. Civility is one thing but knowledge is important, too.