This is not good for the DotNetNuke ecosystem. The DotNetNuke community is becoming unbalanced and left at the mercy of a few people in a corporate environment. I don't trust their commitment. Their past tells a tale. What is good for the corporation is not always good for the community. There are some areas where there is a conflict of interest between corporate DotNetNuke and community DotNetNuke. If the corporation wanted to do the right thing, they could have created their own proprietary modules to bundle with the PE editions. Chris Hammond is wrong if he thinks that would have caused a similar outrage. The community has accepted all previous proprietary extensions to the PE editions.

To restore the balance of the DotNetNuke ecosystem we would need to build a community outside dotnetnuke.com. Preferably some org-domain where all major DNN open source players can work together to improve the free community offerings. Same core, but new open source core modules and providers that take the community edition to a higher level. Licensed in a way that prevents the corporation from taking it off the market. A decent searchable forum, a forge that can be browsed and a wiki. Maybe even a competing commercial marketplace. It doesn't take much to pawn the current community offerings from the corporation. The hard part is getting all the stakeholders to join in on such a project. It looks like everybody is running their own site with forums and wikis.

How long before DNN creative magazine joins the corporation? 

Jan, acquiring a localization solution wouldn't make sense for DNN Corp, due to 2 of 3 leading solutions are available as open source and won't provide PE with an outstanding feature over CE.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN