What has happened to the project team for this module? This module has gone no where in the past 6 months- I have even offered several times to help- not one courteous email back anyone- Why have an open source project if the project team has closed itself off.

Let’s get going as a team and perhaps some of these core modules wouldn’t be as bad as they are. Of course, this post will never see the light of day, as the forum is moderated- What is up with that anyway?

Let’s get some constructive plans in place to make this module better. It has lots of potential- don’t you agree?

We could start with some search capability?

Mark Kendall

I feel sad that threads like this goes unanswered from the core or project teams.
Obviously the project progressreports back into the core management do not work properly. The core management needs to make sure/maintain that subprojects are alive and kicking. Entusiasm fades in this degenerating state.

I have worked with this product since IBuySpy 2001 and DotNetNuke really took off in the 2.x, 3.0 upgrades, however community interaction has stagnated somewhat although the new features are awesome.

Seems like the Core team have fallen into a classic trap, work harder to deliver the expectations in order to satisfy the requests at once (Results only in widening/deepening the frustration and communication errors)  instead of dedicating time towards communication, dialogs, collaboration, interaction related to the future and current status.

If time is dedicated to community interactivity, It's not done in an efficient way. I follow this project in many different dimensions and channels, and I'm starting to expect no improvements.

Take some of the money dnn generates and establish a rewardsystem for "a professional MVP program" that ease the communication load on the core teams. CommunityServer have managed quite well by copying the MS evangelist strategy.