As for Telerik controls, those are no more limiting than any other component that we deliver as part of DotNetNuke.  Whether it is SharpZipLib, DataAccessBlock, Syndication, OpenID, WebFormsMvp, FCK, jQuery or even the icon library (yes we use a licensed Icon library), there are lots of components that have their own licensing restrictions.  You as a user of the software have a choice when chosing to do custom development with DotNetNuke, accept the licenses for each of those components or pull them out and replace them with your own component.  You have the full source code and are free to use or not use the components we include.

DotNetNuke does not absolutely depend on Telerik in order to run.  We use that because it allows us to focus on the core software and move out of the business of writing WebControls.  This also provides a value to module developers since they can rely on Telerik being a part of the core framework and don't need to worry about redistributing a 13Mb file with their module.  Hopefully over time this also helps minimize some DLL hell for end users as well.

Joe there is one difference the license included from Telerik.

@Will I changed the line when you read it...:) So I'm not sure you understands me right this time either.:)

As I said before I have no personal  problem with the license. A license is a license open source free or not free.

However the license make it much harder to use the DNN  CE for customers in your buisness.

I have worked with product management in a wordwide  IT company and I think  the Telerik licence is rather vague. Maybe as vauge DNN corp and Telerik wants it.