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
4/1/2010 1:31 PM
 

First and foremost, I would like to thank Shaun for bringing clarity, vision, and confirmation to MANY more issue than were raised when I posted very early in this tread. Shaun’s commitment and passion to DNN was part of what brought us to this platform in the first place. It is not surprising that Shaun’s vision for DNN is still grounded and compassionate. Thanks again for taking the time to “Keep the Faith”.

I don’t post often because frankly, I pretty much always liked what I saw. I am not a module developer. I am not a large integrator. I don’t build skins for a living. I am a small integrator/website developer with my customer’s requirement first and foremost. I still believe that for so many reasons, DNN is the right solution for my clients both large and small. CMS environments like DNN are the present and future for website development (IMO) because it empowers customers and their communities to take control of their presence and engage them in something living and breathing, not just static. What makes DNN special amongst CMS platforms is the Community, the community of module developer, integrator (large and small), skin builders, hobbyists and enthusiast. If the DNN core does not fill the bill, then go out and find a module that will and I almost always do. With the extraordinary vision, passion and creativity of the Community, DNN can grow exponentially. The fight is to deliver the best solutions we can and go toe to toe with the hundreds of other CMS solutions available. The community is what is important. I guess I would be more concern if no posted anything on this thread, if no one cared.
I am a small DNN integrator. I use OpenDNN modules, I wish they were still going to be available for my CE customers that require them in the future because they work and I have experience with them. I have built by business around DNN and convert each and every site I can because I believe it is the right solution for my customers. I also push DNN because with my decision to adopt DNN as my platform of choice, we all benefit from the thriving community I am proud to be associated.
Thanks again to Shaun for clarification and vision and always know that we as a Community are watching...
 
New Post
4/1/2010 1:35 PM
 

 

Thanks for the clarification Shaun.
 
As opposite from you I don’t see me as a developer but I totally agree that you should let professional legal experts to handle those matters. But since I had handle questions like this maybe before you was born and saw a problem with the license I let the community know my view.
 
I felt it was an interesting issue so I did a call to a friend of mine with the right skills and discussed the case.  He gave me right about the product issue but he added a lot of ifs.
One of the ifs was what do DNN Corp mean the product is. And he said something like this “ If DNN thinks the product is a product you can change as you wish you may could claim that the Telerik license is still valid even if you do whatever changes you do”
 
 He also told me that if it should go to court both sides will have valid argument but you can’t know how the outcome will be for sure.  He also advised me that if this is a problem for me I should try to get a statement from the company how to interpret the license.
As I earlier said it’s not a problem for me personally. However it could be a problem for customers and I am now happy we can add the statement from Shaun that the intend from all parts is that we can do whatever we want with the DNN CE product without braking the Telerik license.
 
By the way he said shouldn’t you be more worried about this statement ..
“TELERIK reserves the right to discontinue at any time any product, whether it is offered individually or as a part of a product suite.”
 
I am not worried and I hope no one ells are.
Jan
 
New Post
4/1/2010 2:47 PM
 

Jan, since you were one of many who raised questions about the Telerik license, I tried to answer the question in a general manner which did not single out any specific member of the community. I appreciate your feedback on this topic and I think it was good diligence on your part to express your concerns and seek outside legal counsel for advice. Your friend's feedback about both sides having a valid argument in court is typical for almost any legal dispute, IP or otherwise - this is where the best litigator wins regardless of the facts, so it is usually best to avoid these types of confrontations. And the point raised about the vendor "reserving the right to discontinue at any time" is another reason why it is in our best interest to utilize wrappers for these controls. Abstracting an application from third party dependencies has a variety of architectural advantages and it is an approach we have embraced throughout the history of DotNetNuke.


My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
New Post
4/5/2010 8:38 PM
 
Shaun Walker wrote:

... We imposed this restriction on ourselves because we wanted to absolutely avoid a situation where we would be competing with module vendors.

Peter Donker wrote:

Unfortunately we seem to be in a situation where the interests of vendors is pitted against those of integrators (specifically those that rely on ODL). Let me reiterate why module vendors are keen to keep DNN Corp out of the CE market...

Sorry, but you have been a direct and vigorous competitor in the modules market for years. I agree with Will Morgenweck on this. The OpenDnn purchase is just more aggressive.

The core modules are a mixed bag of effective, simple, stale, underwhelming or uneffective functions the community has endeavoured for years to replace with better or custom options. When the core are updated, it has ripples. For instance, the DNN blog module was woefully inadequate and immediately replace by a 3rd party module. Since the recent upgrade however, it has been acceptable to more clients. I have never purchased a RSS reader because the core XML module is fantastic. This is pure and direct competition.

I think you should just embrace it - you sell modules. May as well sell the OpenDNN modules a fair market value. Should help take the pressure off monetizing the core.  Just stick to the modules that at least %30 of the users might need so you don't dilute the production efforts.

If you do it wrong and don't play fair, there will be a loyalty price to pay and the long term viability of the corporation will be at risk. You know it and the VC's know it. I'm good with that as mitigating factor.

 
New Post
5/6/2010 3:42 PM
 
Because they control your ability to sell the module to the market place. Remember!  They own SnowCovered and control what is displayed to visitors and in the weekly email.

Since they stopped sending an email with weekly updates and changed to to an email with their hand picked module list. Our module sales through Snowcovered have dropped 50%.

Now remind me again why we would try and compete directly against the store owner?
 
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