Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...So why is DNN Corp Purchase of OpenDNN a good thing?So why is DNN Corp Purchase of OpenDNN a good thing?
Previous
 
Next
New Post
3/30/2010 12:48 PM
 
As a person like the rest of you who spend nearly every waking moment living and breathing DotNetNuke, I am conflicted about the shim jammed between the DotNetNuke Community and the DotNetNuke Corporation. As an integrator, I spend a great deal of time purchasing and testing modules for use on both CE and PE versions of the platform and feel that there are some good and some bad. Those modules which make the cut as good modules in my humble opinion are worthy "Enterprise Level" modules. I believe that DotNetNuke Corp has a rightful ability to also see these as "Enterprise Level", and therefore include them within their package, either as a license agreement with the original developer or by simply purchasing the IP directly from the vendor.
 
For those of our  paying customers, and in paying I mean those corporations which are purchasing  the "Enterprise Level" platform of DotNetNuke, I must say I feel that the inclusion of Enterprise Level modules is not something that should be considered, but rather, an absolute and certain MUST for PE to be exactly what it boasts: "Professional".
 
I am unfortunately taken aback by those people in the community who are users and integrators and see this any other way. Yes, obviously, there are things we all want on the cheap, but when we have a client who chooses to go with the supported and dare I say "Professional" version of DotNetNuke, we are all up in arms. 
 
Now, this is not nearly the same argument against the opinions held by Module developers. For them, this is a bit more dramatic, and obviously, puts more pressure on their endeavors. However, Enterprise Level is Enterprise Level, and those modules which are Professional and High Grade and obviously Enterprise worthy will still be available to all PE and CE versions. Frankly, I don't think any of us need a list of those modules because we are well aware of their fantastic track records.
 
The only valid lament I can see in this entire verbose thread is an inability to obtain the existing OpenDNN Document Library for use within our CE based clients. And for this, we can ask them to pay for the Enterprise capabilities, or pick yet another "Enterprise Level" module off the market, of which there are still many (atleast one of which is more often recommended over the now PE Document Library anyway). For Module Developers, I cannot see theirs as a valid argument anyway, because changing a price point from under $200 to over $2000 simply eliminates competition that currently exists, creating a void which can either be filled by the competing products, or exploited by a new player in the market. For the DotNetNuke community to succeed, we MUST have DotNetNuke Corp succeed, regardless of which hat we wear. 


Kevin M Schreiner
[P] 410.327.0007 [F] 410.327.4082 | info@r2integrated.com
 
New Post
3/30/2010 12:56 PM
 

Charles,

I asume alll work gemini and CE features are also work for the PE version as it is the same codebase.

Just to get it right or have there been a change in the same codebase statement?

Jan

 
New Post
3/30/2010 1:10 PM
 
Jan Olsmar wrote:

Charles,

I asume alll work gemini and CE features are also work for the PE version as it is the same codebase.

Just to get it right or have there been a change in the same codebase statement?

Jan

 

Jan, the codebases are still the same. PE is still built on top of the CE product through the use of added extensions


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
3/30/2010 1:27 PM
 

Ok Chris, So all work gemini and features will be a benefit for the PE version as well.

I think its important to tell that all testing that the CE version users do by using the CE version is of great importance for the PE version as well.

Both in blogs and in this tread it sounds that the work are separated. (I understand that PE extentions must be tested separate)

Jan

 
New Post
3/30/2010 2:04 PM
 
Jan Olsmar wrote:

Ok Chris, So all work gemini and features will be a benefit for the PE version as well.

I think its important to tell that all testing that the CE version users do by using the CE version is of great importance for the PE version as well.

Both in blogs and in this tread it sounds that the work are separated. (I understand that PE extentions must be tested separate)

Jan

 

Jan, what you say is true - all work done on CE benefits PE, but what I was trying to say is that 75%-80% of work being done today benefits CE (only 20-25% is purely PE). In the last 15 months this means approximately 6 Full-time developer resources are committed to CE work - compared with 1 (me) prior to funding.

Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...So why is DNN Corp Purchase of OpenDNN a good thing?So why is DNN Corp Purchase of OpenDNN a good thing?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out