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!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

More Thoughts … DNN Corp Acquires Document Management IP From Xepient Inc.

Over the last 48 hours, I have been both watching and receiving responses related to our recent announcement.  Andreas Di Palma has also reached out to the existing Xepient user base and received their initial reactions and responses as well (see Andreas' post).  Overall, the responses to the blog and to our communication to the existing Xepient customer base have been positive with some expressing their concerns at the move.  The discussions in our Forums, though, have been mostly of concern and fairly high discomfiture.

I said the following in a core team conference call when we launched the Professional Edition and also said numerous times at the DevConnections conference. One thing that won't change in the company, irrespective of funding OR the launch of commercial editions of the software, is that we will always ENGAGE with our community.  We will listen to people when we agree.  We will also listen to them when we disagree.  If anything, we will listen harder and more carefully when we disagree because we want to get our decisions right.

A great open source company is built on the foundation of a strong community.  Community and company are essential if we are to get this right and do well.  This doesn't mean we always agree with each other on everything but it does mean we always actively dialogue and dialogue with an open mind.

On the responses/reactions of different individuals, I do believe the concerns of different people are different: the concerns of an existing user/customer are different from those of possible new users and those are different from those of module vendors which are different from those of system integrators.  Broadly speaking, the concerns may be classified into the following generic themes:

Why will O-DL no longer be available as a standalone module? 

How will existing Xepient customers be supported? 

Is DotNetNuke Corp going to gobble up the most popular third party modules into the commercial version of the product, thereby affecting the add-ons market? 

What is DotNetNuke Corp's commitment to the Community Edition?  It seems like all they are focused on is 'differentiation'.

Each of the above decisions was made after careful internal deliberation or thought but, having said that, nothing is sacrosanct.  The only thing that is sacrosanct is having open dialogue, listening carefully, and deliberating thoughtfully to ensure we get our decisions and actions as right as possible.

So, what was the internal thinking/discussion on each of the above?

Should O-DL be continued as a standalone module?

Our first inclination was to have it both 'standalone' and as a part of the Professional Edition.  Like I said, our market research clearly indicates that the two markets are different. The market for add-ons (Average Transaction price of $80 to $100) is very different from the market for commercial platform editions (average sales price of $4K to $5K).  This meant we could get the benefit of both markets by leaving the module as is on our online marketplace.  However, as some of my colleagues (including Shaun Walker) pointed out:

This shouldn't just be about commerce.  Is this the right thing to do?  If we keep the module available as a standalone (i.e., a la carte) on the Marketplace, are we going to support, maintain, and enhance it separately as well?  If we did that, aren't we essentially becoming a module vendor?  Aren't we targeting the same market segment that our module vendors have built their businesses catering to?  Won't other module vendors feel that DotNetNuke Corp is going to build modules and go after the same market segment as theirs?

However, if we didn't keep it standalone, we would be taking an excellent, well developed module off the market and therefore it would not be available to Community Edition users. The good news, though, is that there is another mature document management module, Bring2Mind's DMX, that does fill this gap.

As you can tell, the decision wasn't easy or straightforward.  There were multiple dimensions to it that had to be considered.  Finally, we decided to ensure that all existing users of the module continue to be supported (i.e., our arrangement with Xepient and Andreas) and the module will continue to be available for a fixed period of time while we transition out.

I am not telling you our decision was right or wrong.  All I am saying is that the decision wasn't easy and the decision was made after a lot of deliberation.

How will existing Xepient customers be supported? 

We are in discussions with Andreas about this. We definitely won't leave Xepient customers at a dead end. That is something we just won't do. The possibilities being discussed are making compatibility patches available for existing customers of Xepient, availability of source code at a discounted price, upgrades to PE at a discounted price, or some combination. Either Andreas OR we will communicate this to the existing Xepient customers in due course. 

Is our strategy to acquire module vendors to build functionality?

There are over 8,000 modules and skins on Snowcovered.  We acquired two.  Both in terms of the number of modules and revenue share of the module market, this is miniscule.  This is not a strategy.  This is one instance of a feature being requested by many corporate customers and we developed a plan to build the feature.  However, on discussing this with Andreas, and when we explained what we were doing to him, we reached a mutual decision to complete a business transaction. This transaction decision was made by both of us and Andreas will tell you the transaction is benefiting both of us. 

I request that we don't read more into things than have actually occurred.

Our commitment to the Community Edition (CE)

Yes, there is some feature differentiation in the commercial versions of our product.  But please make no mistake, we are very clear that it is to the long-term benefit of the community, the corporation, and the ecosystem to ensure that the Community Edition is strong, stable, valuable, and very well received by the market at large.  In our minds, this isn't about the Community Edition and the Professional Edition. This is about ensuring that the open source version of our software is better than our open source competitor's products, irrespective of which technology stack they belong to or whether they are big or small.   In 2008, we had 1 FTE dedicated to development on CE, today we have 3 people who spend 60% of their time on CE bug fixes alone. We also now have 2 people dedicated full-time on CE feature development. I understand the 'feature progress' on our core platform (both CE and PE) has been slower than you (and we) would have liked and we fully expect that to ramp this year as the new hires understand the platform better and integrate better to become a much more productive unit.

Just to be clear, I am not saying the Community Edition is better OR best. All I am saying is the importance of the Community Edition is very well understood by us and the importance of an ecosystem is something we deeply appreciate. We will be very focused on ensuring that the Community Edition gains in strength over time.  My product and engineering team will be as focused on the Community Edition as on the Professional Edition, without doubt.  We will NOT build the Professional Edition at the 'expense' of the Community Edition, just as you don't build a building without a strong foundation.  Even in our internal discussions, this isn't a discussion item. Everybody in the company understands the need for the Community Edition to be strong, valuable and powerful for everybody's benefit (including our own).

Thank you for your feedback.  Thank you also for the open comments and the time you spent in communicating this to us.  We appreciate it.  It is this open dialogue that will ensure we don't skip a beat as we continue on this journey together. 


There are currently no comments, be the first to post one.

Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Daniels (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out