Fair enough.  I'm sure there are plenty of satisfied customers (who don't speak up) and those that aren't (and do speak up).  The squeaky wheel is the one that will be heard.

I am just sick and tired of all posts that infer the core team is in some way irresponsive, irresponsible, careless, etc.  The core team and project teams work extremely hard and donate their time and experience to this project but they need to do it on their own timetable, not ours.  They have other jobs, friends, families, etc that take a little more precedence than this. You can only throw so many resources at something before it gets out of hand which is why the core team is limited in size.  

It would be more appropriate, as mentioned in several other threads through the past year, to offer help or offer solutions (in form of posted code, 3rd party modules, other) rather than gripe about problems.  Yes, it has also been acknowledged that the pathway to helping out is not the easiest... lots of hoops to jump through, but there are always avenues to take.  If you don't like a module or how it moves (or doesn't move) along, then write your own, make it better, and make sure it doesn't suffer the problems you are complaining about.

I expressed my opinion that I feel Tony is a trash marketer.  He markets things he doesn't even have yet; he makes "important changes" to make things "more secure" and in a lot of posts I saw during that time, apparently without notifying the website owners ahead of time, and more.  My opinion isn't based on personal hosting experience at PowerDNN, but based on the forum posts I've read over the last several years that I've been involved with DNN. 

I was harsh in my email, too much so I'm sure, and for that I apologize.  But seriously people, a delayed release to fix issues is so much better than releasing broken software.  Lets all quit complaining and hope that the extra time produces a very solid build.  The Core team seems to be making some large changes lately in how they release things (after a couple of less stable builds) and instead of griping about it, lets just realize the reasoning behind it and be happy they are doing damage control before damage actually occurs.

As you mentioned Tim, there is an apparent lack of progress and a serious lack of good communication; those are good points.  Those are issues that need to be addressed, but not in a way that puts down the core team.  If somebody is trash talking you (or your product) and/or breathing down your neck, how much do you want to actually perform any work for them?  I personally hate that.  I'm sure they feel like we're a bunch of ingrateful weenies and breathing down their necks and I can only imagine how flustered that makes them.  Lack of progress is a phantom; there is plenty of progress happening but most of it in the 5.0 release is behind the scenes, not something you can really show off.  Does that mean progress isn't happening?  No, of course not, but it isn't the sort of tangible progress any of us can palpitate.  In the end though, behind the scenes progress is still progress and moves us towards more "groundbreaking" changes.

I'm sure if a really good communications person offered to be a frontman for the corp and provided a good resume they'd be interested in taking a look.  My guess is that there aren't any really good prospects offering themselves up yet.