Shaun,
This is definitely one of those Netflix moments where the Owner/CEO needs to step in and start implementing emergency damage control. Unless the goal is to shed the open source community baggage, DotNetNuke, excuse me, Evoq, is on the wrong path.
I've been using DotNetNuke since the IBuySpy days, and it seems just as the product (version 5, 6 and 7) has fully matured, decisions are being made which threaten to destroy everything that you've built. Maybe a viable commercial product can be forged from of the ashes of DotNetNuke, that's beyond my ability to discern, but the community, the developer community -that's going to die unless you change course.
Here are my recommendations:
1. Separate the two products: Commercial/Community - Use different websites, different brand names, and develop them for different audiences. I am perfectly fine with DNN spinning off some grand cloud based hosting business, and I wish you the best of luck, God knows you guys/gals have earned it, but leave the community platform in place and as is.
2. Bring the pricing down, way down, on the commercial (pro) version. $99 a year for the professional version seems reasonable, and something that I would pay for. If you want to include your own hosting, as in a cloud environment, great, but that's maybe $500 a year for shared hosting. The enterprise versions can be scaled up accordingly.
3. Re-Build your developer community. It's gone to heck in a hand bag. Snowcovered was better than the current store. The old web site was better than the new one. Perhaps, what is needed is a new module development scheme which will enable module developers to program for multiple platforms (including PHP, Net, etc). Maybe you need to create a developer web site, separate from the community web site, which is itself separate from the commercial web site.
4. DNN has largely closed the performance and stability gab between DNN and competing technologies. That is great, now you need to focus on the end user experience with the controls. This is still a major pain point that I see in trying to get end users to interact with DNN web sites. Everything is still too complicated, and the Control UI's are not modern enough for most users to effectively interact with DNN. You need more wizards for module configuration, and better Control UI standards for module developers.
5. Keep the name Evoq, it sounds good. DNN works too. The brand DotNetNuke has long since lost it's relevance.
My Use Case: I create inexpensive web sites for small businesses and organizations. I rely heavily on the portal implementation to cut down on module costs, web site development and management time, and hosting costs. I think that my use case was at one time probably a fairly common scenario for many DotNetNuke users. Perhaps not any more, and I just need to face facts and move on to a different platform. That sounds like a lot of work. What I would prefer is to continue using the product for free or a nominal fee, paying reasonable hosting fees, and purchasing modules and/or functionality as needed.