DNN Blog

Feb 18

Posted by: Navin V Nagiah
2/18/2009  RssIcon

 Less than 2 days ago, we launched the Professional Edition of DotNetNuke.  This was an offer we designed and made public after talking to various businesses that expressed a desire for a product that they knew an organization would stand behind, support and guarantee.

 
In an effort to publicize the benefits of this offer; we issued a press release.  There is no easy way to say it.  We went over-board in our choice of words in describing the Community Edition.  In an effort to market the Professional Edition, we used phrases that weren't appropriate for the Community Edition.  While we had every right to market and publish the benefits of the Professional Edition; we were wrong in the choice of words we used to describe the Community Edition in this press release.
 
We understand that this choice of words has caused angst amongst a lot of you; many of whom have built your businesses on DotNetNuke.  For that, we unconditionally apologize.  I can think of 20 reasons why this happened --- we were busy; it slipped under the cracks; it was an oversight; etc etc.  Truth be said, the reasons don't matter.  The point is we erred and we are sorry.
 
I would like to reiterate ...
 
1.  Our intention is not and will never be to hurt the community edition and/or participants in the community.  We will continue to invest in and promote the community edition.

2.  Our intention is to promote the Professional Edition as a package that we will stand behind for businesses (small and large) to use.

3.  As we start this commercial journey ... as an organization, we have to learn to strike the 'balance' between commerce and community.  During this learning process, we will make some missteps.  That is expected.  But, we will learn quickly from those missteps.

4.  We will listen to all feedback from the community --- We will strive to accept the feedback that will help us get better as an organization.
 
As we continue on this journey of balancing 'community' and 'commerce' ... we will make mistakes.  The above was a mistake, albeit an inadvertent one.  The one thing I promise you is that as an organization; we will always listen to what you have to say and when we make mistakes, we will correct them.  
 
My only request to you is to keep intense emotion out of the dialogue, to the extent possible.  We are keen on building a large commercial business ecosystem; with your help and by working with you.
 
Once again, our sincere apologies for the angst caused due to our poor choice of words in the press release.
 

Tags:
Categories:
Location: Blogs Parent Separator Navin Nagiah

12 comment(s) so far...


Gravatar

Re: We are sorry about our poor choice of words!

I appreciate you posting this, as there are many of us out there, that were troubled. I am excited about this new path DNN is taking and I look forward to taking it with you.

Stuart

By Stuart - Hilbert Solutions, LLC on   2/18/2009
Gravatar

Re: We are sorry about our poor choice of words!

Thank you so much for clearing this up. This has been a long 24 hours for me. I have been having to field questions from across the globe about those words. Without someone from the higher levels of leadership coming out to say something, my hands were tied. I dedicate an enormous amount of my time to help the DNN community grow. That being said, there is little else to do but take those words personally.

I feel so much better now, Navin. Thank you again.

By Will Strohl on   2/18/2009
Gravatar

Re: We are sorry about our poor choice of words!

Is there any technical difference between the two distributions ? i.e. is there anything additionally added to Professional Version ?

By Jaydeep Bhatt on   2/19/2009
Gravatar

Re: We are sorry about our poor choice of words!

Mistakes happen, and the fact that you came out and apologized for it and did not try to make excuses for it shows the kind of leadership you are providing to DNN Corp. DNN Corp has always been open with the community and IMO they have always had a lot of integrity. It appears that the new members of DNN Corp that are now helping guide the ship are following the same principles and will help to run DNN with Integrity and honesty when it comes to dealing with the community.

By Shawn Mehaffie on   2/19/2009
Gravatar

Re: We are sorry about our poor choice of words!

Jaydeep ... The code base for both are the same. There is no difference in functionality. We have made our message more clear on the web site now; and included an FAQ to help answer some of the questions.

Navin

By Navin V Nagiah on   2/19/2009
Gravatar

Re: We are sorry about our poor choice of words!

Hi Navin. Thank you for the followup, however, I would like to say in reference to this statement "Truth be said, the reasons don't matter. ", that trith be said, the reasons DO matter. Especially now that money is involved. You have a very fragile community at this point in time.

While most agree that this is a very good thing, having a Professional Edition, you have a sizable amount of people who are not so sure, and coming out of the gate as you did made them even more antsy. Please ensure that "whatever the reason" is not a mantra going forward.

Thank you and continued good luck to DNN.

By Mark Gordon on   2/20/2009
Gravatar

Re: We are sorry about our poor choice of words!

Thanks for this post. It clears up my worries.
But you said that you are going to correct mistakes.

It is not a mistake but a long lived bug since early releases. Some of Worldwide users won't be able to install dotnetnuke to their ecosystem because of lowercase and uppercase trouble in install scripts.

For instance, Turkish_CI_AS and Latin1_General_CI_AS is quite different while installing DotNetNuke. Try yourself. Set up a SQL Server that uses Turkish_CI_AS as server and db collation and try to install DotNetNuke.

The only way to fix this painful bug is working hard by correcting every SQL install& update script by hand. I believed some of people thought fixing this was a time waste. But to me it is a great way to welcome more regional users.

Please consider this with your members.

I was also wondering, let's say a French client contacted you about pro edition and asked about support. Will you provide support in French?

I mean is there any place we could send our resumes to join the team?

Thanks for listening.

By Ismet Dumlupinar on   2/20/2009
Gravatar

Re: We are sorry about our poor choice of words!

Mark ... Your comment is valid that reasons drive actions and therefore matter.

Clarification ... My point in saying "reasons don't matter" was to say "we made a mistake" and "there are no excuses for the mistake".

Best

Navin

By Navin V Nagiah on   2/20/2009
Gravatar

Re: We are sorry about our poor choice of words!

Right on. Very good to know--definitely felt the same as Will did about having that mini panic attack. Thank you for clarifying and thank you for the work you guys do. Does this mean the CE will get the cutting edge features that will trickle back into the PE as they mature? Or that the PE comes with SLAs backed by DNN corp?

By Andrew Marx on   2/23/2009
Gravatar

Re: We are sorry about our poor choice of words!


Andrew:

The current Professional Edition has the same code base as Community. It comes with SLA and legal/copyright indemnification backed by DNN Corp.

Best

Navin

By Navin V Nagiah on   2/23/2009
Gravatar

Re: We are sorry about our poor choice of words!

Thanks for your post and congratulation to the DNN team for it great software; however, it is difficult for me to understand the duality of having two versions of DNN when money is now involved.

The NATURAL RULE says that it will be more PROFITABLE to shift or spend the efforts into the PRO version, in order to increase the quality gap against the community’s version. The natural goals and incentives are pointing to opposite directions!

To maintain the community’s happiness (an important equity for DNN) there will be no other choice for DNN Corp. to go against that NATURAL RULE, however, I have to say that it is unfortunately a weak equilibrium.

Even for the understandable marketing of the PROFESSIONAL product, it is going to be difficult: can somebody inside DNN evaluate in an IMPARTIAL way if the PRO version is recommendable for a particular company? Can a DNN’s sales representative recommend the COMMUNITY version if they truly see the PRO version is not necessary for a specific company?

The previous was the concern of IMPARTIALITY. However, there is a concern of DEVELOPMENT also. For example, are not going to be some characteristic implemented in the community version just because they "sound" PROfessional attractive? For example, let see the outstanding enhancement number one for the community vote: "publishing workflow" (www.dotnetnuke.com/tabid/616/Default.aspx). Let me say that it sounds "PRO" and there is a high manifestation of "demand", so why do not take advantage and put it in the PRO version?

Hope you can see my point. It is "concern" and not intended to be "critic" of an additional income for DNN Corp..

If the intention is to maintain the same source code (as I have read somewhere) and it is to focus in the "service" around it, my humble recommendation is not referring this as a different "version". Why do not calling this a "Professional Support"? Or "DNN professional Warranty" that you can buy on top of the distribution? (There are many other alternatives). That will solve the concerns of IMPARTIALITY and DEVELOPMENT.

If your intention is to maintain different source code, I can humble recommend that DNN made, for example, a kind compromise of transition of the enhancements from the PRO to the COMMUNITY version, with a certain delay (6 month for example). That way DNN Corp. can transparently maintain a PRO version without high conflicts, allowing to profit of the PRO and to maintain the community happy.

My intention is to support the DNN. That is why I see necessary to make an open dialog of this. All the commentaries and options are for me welcome. Looking forward to clearing all the concerns.

Best regards!

By ASomm on   3/4/2009
Gravatar

Re: We are sorry about our poor choice of words!

I had two clients that were considering a Pro version of DNN until they asked about the flaws in the current Media gallery and Forums. I told them it was unknown if the core modules were going to be stablezed before being "sold". This answer has caused DNN to drop out of the consideration for one Intranet. I have been asked to provide 3 other solutions for demo.
I prefer to keep like for like in a business I.E. MS O/S structure with M/S intranet. Unforunately, they are few and far between for low cost and quality of product.

Good luck with your endeavors. DNN has promise, but has a tough road ahead of itself in these times.

Dean

By Dean Craft on   3/5/2009
Attend A Webinar
Try An Online Demo
Download DotNetNuke Professional Edition Trial
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

Sponsors

DotNetNuke Corporation

DotNetNuke Corp. is the steward of the DotNetNuke open source project, the most widely adopted Web Content Management Platform for building web sites and web applications on Microsoft .NET. Organizations use DotNetNuke to quickly develop and deploy interactive and dynamic web sites, intranets, extranets and web applications. The DotNetNuke platform is available in a free Community and subscription-based Professional and Enterprise Editions with an Elite Support option. DotNetNuke Corp. also operates Snowcovered.com where users purchase third party apps for the platform.