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/29/2010 11:49 PM
 
Thanks for the candid and polite conversation everyone. Lots of good thoughts and replies. I think that says very good things about the future of DotNetNuke and the community. Lots of people are concerned, including the ones within DNN Corp making the decisions. The feedback in this thread should help keep things on the right course. We should speak up and voice our concerns. This threads shows our concerns are being heard and our reactions (and our business models) were considered prior to making any moves. I am nervous about outside VC money funding so much as the decisions will not always be in the hands of the founders who have repeatedly shown true commitment to the community as a whole. Ultimately, all of us who are so heavily invested in DNN are all on the same boat and this type of honest communication is vital to keeping it all together.

David O'Leary
Efficion Consulting
 
New Post
3/30/2010 12:34 AM
 
Will Morgenweck wrote:

Why can’t DNN Corp come right out and say what's next on their agenda?  Why can't they define this "complete solution" we keep hearing about when it comes to DNN Pro?  I still don't think the original question that was the start of this post has been answered.  Why was the Xepient IP acquisition a good thing?  We've heard that it was a good business transaction and that it made sense for both parties, but what does that actually mean for DNN Pro?




 

For me this has been the biggest problem with DNN Corp and DNN Pro, COMMUNICATION!!!

 
New Post
3/30/2010 1:25 AM
 

Despite claims that DNN Corp didn't want to throw its weight around or that it was catering to Andreas' perferences, DNN Corp could have easily paid to obtain a copy of Xepient source and then provide any enhancements and integration they wanted for PE integration.  The could have even called it Elite-DL and Elite-SE (as opposed to Open).  This would have left Xepient's existing products on the community market to follow thier own development path.  Everyone would have been happy and DNN Corp would have everything they "claim" they want. 

Let's not kid ourselves.  The only reason to remove the Xepients products from the community that funded and helped develop the IP is to deprecate the CE version.  Despite their VC, DNN Corp must think this is the only way PE can complete.  Who at DNN Corp wants to admit that?

Who wants to tell our clients that the Xepient products (that we vouched for and charged them to integrate) are now dead ends?  Who should pay for the training and cost to buy and migrate to DMX?  Our clients?  The implementors?  DNN Corp? 

BTW - does anyone know of a decent search option?

Chris

 




Chris Wylie
Chief Executive Officer
www.AccordLMS.com
1775 W. State Street Suite 371, Boise ID 83702 USA
 
 
New Post
3/30/2010 1:33 AM
 

Do module vendors really have to worry a ton if DNN bundles a similar module in the PE version? How many people buy the PE version vs the number of CE users? It seems this is a better opportunity for a module vendor by selling more of their $100 modules than people paying $2000/year to get the competing module. As a module developer, you are working full time on it to make it better. I doubt the corp will hire a full time developer to maintain a single module.

There are many commercial shopping carts even though DNN comes with a free one. Make your module superior and people will notice. Microsoft eventually pulled Microsoft Money from the market against Quicken.

The CE version seems to be getting better with more features. I don't mind PE having more features. Those added features in PE are really not that important for me. People who use CE should worry less. You are using CE for the features which are offered NOW. Not for future features which you don't know about. This is just like any software. You bought it for what it does. If DNN CE dies tomorrow, it's not the end of the world. The community has the source code and it can fix bugs and add features if needed. It seems the vocal people here are the module developers and the systems integrators. As a user, I never heard of ODL. I know about DMX. As a DNN User, I am happy that CE is free and that its development speed is getting faster and better. Unless DNN CE is being crippled compared to prior versions and no progress is being made, I don't see why some people think it's dying.

 
New Post
3/30/2010 1:36 AM
 

So this is what we have become. A bunch of scared to death chickens running around reading press releases from the corporation trying to figure out if they still want our eggs or if they're having our filèt and wings for dinner tomorrow. Our worries are well founded, because remember this:

The corporation is only one board meeting away from doing something really stupid.

Thats how fragile this ecosystem has become. This is your wakeup call. If the PE introduction didn't scare you, or you really thought that proprietary Telerik components in what used to be the open source version was a gift from heaven, then please think again:

The main strategy for the corporation is to sell the PE version.   

Thats what paying the bills, and more importantly, thats what the investors came for. The community version is supposed to be the entry level product and the PE is the natural upgrade for serious use. The tactics to implement this strategy are quite simple:

Take control of the community and use it to sell the PE version.

So how is the community controlled?

  1. Owning Snowcovered.
  2. Introducing proprietary licensed components to the "open core" (Teleriks) where it's use are governed with an agreement between the two corporations.
  3. Refusing necessary tools for the community on the main site.
  4. Slowing down the development of the free and open "core modules and providers".

If you don't believe me, consider this: Does it take 3 years to setup a wiki? No, but it may take 3 years for a corporation to decide if it will profit or hurt the PE version. I don't think it's a coincidence that the corporation is not looking for volunteers to help out with the community extensions. For an open source project that is down right suspicious. They want to do everything themselves so they can control it and make sure the CE-PE gap is inline with the overall strategy. The only community activity that is getting all the attention from the corporation are the user groups. Their purpose being sending users off to the annual event so that someone from HQ can visit and pitch the PE version.

If this is allowed to continue the CE-PE gap will continue to expand until the CE has found it's proper position as the entry level product only usable for the small and low traffic sites. In the coming months and years we will see that the PE version will replace all modules and extensions shared with the CE version. In the end they will only share the "open core" which amounts to nothing from the end users perspective. The long term effect of this, is that companies that are willing to spend some serious dollar on DotNetNuke will do it by utilizing the PE version. 

So how do we fix this?

We need to setup an independent and open community taking responsibility for core modules and extensions for the open source version of DotNetNuke. It's as simple and hard as that. We also need a competing marketplace to Snowcovered. It doesn't have to take 50% of the market to be important. It's mere existence would make it important. Ready to take over if the corporation screw up Snowcovered.

One way to get this started is to fix one thing at a time. Fixing the search engine. Create a distributed cache. Replace some rotten core modules with new solid quality ones. Improved file uploader. Lot's of interesting tasks to do. While the corporation are "looking into things".  

 

    

 

 

 
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