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...Dotnetnuke 5.0Dotnetnuke 5.0
Previous
 
Next
New Post
11/23/2008 10:18 PM
 

Brian,

 

I see your point, and I think we all agree that 5.0 needs to be out soon, and we should thank Shaun for giving us a little guidance on when that might be.

The thing you must understand about creating a sustainable revenue model around DotNetNuke is that it is not quite as simple as charging $20 for the software.  While you are right in saying that most of us would gladly pay to use this great product, we would also have much higher expectations for a product we paid for.  For DotNetNuke Corporation to charge money for their product they would need to set more strict quality standards which would probably require hightened code review and testing processes, which would require more dedicated resources.  At that point you have to sit back and ask yourself "what is the best model to persue that yields the greatest returns while maintaining open source ideals and preserves the ecosystem?".  This is not an easy question to answer, and definitely not an easy question to answer when you are trying to release a major version of your software AND you are short on the revenue to support that development. 

The announcement of DNN Professional greatly raises the ceiling for all of us offering services around DNN.  Many people have lemented on this board that it's hard to sell dotnetnuke because of a host of reasons mostly related to stability (both in the application and the organization behind that application).  Now it's a much more enterprise viable solution because of stability, support, indemnification, and security notifications.  Organizing and funding such an effort is not easy, but for anyone operating a business based around DotNetNuke, this should be a welcome evolution to DotNetNuke.

We are all a little bit disappointed in the time it's taken to get 5.0, and I think communication like Shauns post really helps everyone understand whats going on.  Most of us just want something to tell our customers about the 5.0 timeline.  But DotNetNuke Corp. has had their hands full building a business model that will grow the ecosystem and overall adoption of the software that many of us make our living off of.  I am sure most of the Corp. would love it if it were just as simple as turning around and charging $20 a pop and calling it a day. 

Hang tight, DotNetNuke is not even in it's prime yet.  The best is yet to come.

 
New Post
11/23/2008 10:40 PM
 

it only helps if enough people sign up and it doesn't use as many resources as it provides for

the sponsorships were supposed to be the product saving model, remember?

stability does not come because you have support, only if the product is more stable.   Thus your statement "For DotNetNuke Corporation to charge money for their product they would need to set more strict quality standards which would probably require hightened code review and testing processes" shouldn't be made.   Those standars should already be here but they are not. 

 
New Post
11/24/2008 8:40 AM
 

 I agree that DNN has to find a sustainable revenue source. No one works for free, I think we can all agree on that. DNN has been for a long time a great resource for us all.
 


Hector Minaya
Microsoft Visual Basic MVP | Speaker INETA - Latam
MCSD | MCT | MCTS : SQL Server
blogs: Hector Minaya | DotNetNuke SEO | Blogger SEO | facebook junkie | Google SEO Tools

 
New Post
11/24/2008 9:48 AM
 

I need to upgrade my current version of DNN this week. I am currently using 2.1.1. I don't want to do everything twice, so, I have several questions.

  1. Is there an upgrade tool or some scripts somewhere that will help me to do an upgrade?
  2. Am I better off installing 4.9 or 5.0? It is production.
  3. If I go with 4.9, will I be able to upgrade to 5.0 when it releases?
 
New Post
11/24/2008 10:16 AM
 

upgrade from dnn 2.1.1 is a daunting experience. From dnn 2 to dnn 3 there where many breaking changes, which means that probably none of your custom modules will work. You would have to find dnn 3.0 versions of those modules first. Next, i would try upgrading to dnn 3.0.13 first, and see how that goes. If that works, you can then upgrade to newer versions.

In all honesty, it would probably be a much better idea to build a new site from scratch, and import data from the old site to the new one.

ALso: dnn 5 is not ready for production yet, its only RC2.


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Dotnetnuke 5.0Dotnetnuke 5.0


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