Feb17Written by:Will
2/17/2009
Today started out innocently enough. But it was clearly a day for me to remember, as far as my DotNetNuke involvement goes...
I wasn't planning on blogging tonight, but something happened tonight that kind of pushed me over the edge...
Walking into work today, I had my day completely planned in my mind like I normally do. I knew everything that I planned to accomplish. Fortunately, I was able to accomplish the one big thing I wanted to. I was able to roll out a major bug fix to RezHub.com, as well as a few other minor ones.
So, I mentioned that today was the day for DotNetNuke highs and lows. Here we go.
Today's DotNetNuke High
Just after lunch, I got a call from the front desk that a package had arrived for me. That is not unusual for me, so I walked up there as normal to pick it up. I immediately was excited when I noticed who it was from. It was from Wiley Press (Wrox). It was a copy of the first book I helped to edit, Professional DotNetNuke 5. I ripped open the package, because it was the first time that my name was in the credits of a book. I was like a school kid getting ice cream for the first time. Does that make me sad? ;) Needless to say, I showed everyone that would care.
I did notice one thing wrong with my bio though. It is completely my fault, but my website URL is not in the bio. D'oh!
Today's DotNetNuke Low
Before I continue, let me tell you something. I am 100% in favor of there being a Professional and Community Edition of DotNetNuke. That is, if it is implemented how it's been described to us so far. Also, there are several Core DNN members that I converse with on a daily basis, and in many cases would call friends. I hold no ill will towards anyone. However, I do need to talk about something that may ruffle a few feathers. For that, I apologize ahead of time.
As I find myself doing a great deal of the time, I began to do a couple of updates for the ODUG website. I wanted to put up announcements for the DNN version 4.09.02 release, and for a DNN press release I saw come out today. In writing the announcements, I needed to know what I was announcing, so I finally read the press release I saw earlier. The announcement was expected. It was talking about the first release of DotNetNuke Professional Edition. Everything looked pretty standard, but one sentence really burned into me.
"DotNetNuke Community Edition is excellent for testing, smaller scale, and non-production environments, while DotNetNuke Professional Edition is optimized for more rigorous, mission-critical applications"
Reading this verbatim, it could be very easy to lose one's temper, assume the worst, and really just lay in with some choice words and phrases. If you're one of the folks asking, "Why," let me tell you.
Let's break it down into two sentences. Actually, I will break it down into bullet form:
DotNetNuke Community Edition:
- is excellent for testing
- is smaller scale
- is for non-production environments
DotNetNuke Professional Edition:
- is optimized
- is for more rigorous applications
- is for mission-critical applications
As I read it, the world is being told that the Community Edition (CE) of DotNetNuke is substandard to the Professional Edition (PE). In fact, PE is "optimized" to be used for production websites. I cannot tell you how frustrating this is going to make any meetings with potential clients that know anything about DotNetNuke. This is a nightmare. :( It makes me feel that the DNN Corp is trying to compete with the community, rather than embrace it as they have always done.
Right off of the top of my head, here are some questions that some clients may be raising:
- Are you offering the Professional version?
- Is the CE the same? How is it different?
- I thought CE was only for testing?
- Can CE handle my site if it gets a lot of hits?
- Do I have a production environment?
- I thought you cannot run CE on a production web server?
The list goes on, and the answers will be very tough to sell. Effectively, this really puts any DNN consultants out there in a bind if their clients read this press release. I can only imagine how they might feel right now if their business is completely modeled around DNN support, DNN site roll outs, etc.
Now, I am really not trying to over-criticize the DNN Corporation, or tick anyone off. Quite the contrary. I am simply voicing some concerns, in the hopes of starting a necessary open dialogue that is apparently long overdue. We as the community can only feed off of what is given to us, and this press release directly contradicts a couple of quotes I read today on a forum thread, titled, "The Day of Dread". (This forum thread speaks about concerns and fears of the Professional Edition.)
"DotNetNuke Professional Edition has the same code as DotNetNuke Community Edition."
- Charles Nurse
"The platform for Community Edition & Professional Edition is the same."
- Scott Willhite
"Nothing about our philosophy has changed. Nothing has become more closed, in fact, quite the opposite is occurring."
- Scott Willhite
"Over the coming months you will see an increased commitment to the Open Source ideals which we truly value. The business model we have chosen allows us to grow our support of DotNetNuke Community Edtion rather than kill it off and you will see the proof of that in the coming months as we accelerate development of DotNetNuke Community Edition."
- Joe Brinkman
I am deeply saddened at the choice of words in that single sentences of the press release. I honestly am at odds with myself and do not know how to feel about it.
I challenge the DNN Corporation to please address the community and put our concerns to rest at last. Pretty please with cherries on top? ;)
Technorati Tags: DNN, DotNetNuke, DNN Blog, 4.09.01, Community
Copyright ©2009 Will Strohl
13 comment(s) so far...
Agree with the poor choice of phrase. However, at Openforce 08 when the professional version was announced they did say that it would have some things aimed at the enterprise market. 'things' wasn't expanded on then. In fact a lot of questions were left unanswered, mainly because I think the corp were still figuring things out.
The things that concerns me is that the Pro version is going to have "Proactive management and communication of security-related updates to minimize potential threats to the stability and integrity of your websites" and "Comprehensive documentation and support Knowledge Base"
As the Pro version is probably going to be at least a version behind the latest release of the community one and if the Core is more proactive from a security perspective on the certified version. Then why would anyone put the latest version into production? This is going to mean that new versions aren't going to get as much exposure in the real world to sort out the possible security issues as they do now.
As to the documentation this has always been a weakness. A couple of years ago there was discussion of the core creating a Wiki and better documentation, now it looks like only those who pay will see this documentation.
The Pro version 'framework' is certified. So what happens when 3rd party modules are brought into the mix? How many (enterprise) sites using the DNN framework only comprise of the core?
I am still undecided on whether the direction is good or not. The idea is, but we have to wait to see the execution. In the end it is the community that will determine where it goes.
If enough people disagree with the current leadership of the project then there are sufficient community resources to allow a fork to occur. Just look at the number of programmers involved who are not employed by the Corp.
Anyway end of my 'blog comment'
By Antony on
2/17/2009 |
Anthony,
Your last paragraph sums up what I feel is on the cards. Despite the comments from Scott, Charles and Joe, many in the community including myself feel ill at ease.
A new product was announced at OpenForce 08 (and mentioned before that) but as yet we, in the community, are still in the dark as to what that product really is. Until the Corp come clean and provide details on both Pro and CE versions with comparison grids and costs the rhumour mill will be working overtime.
One cannot blame people for being concerned. Many now rely on DNN for a living and need to know what the future holds, sooner rather than later.
By Declan on
2/18/2009 |
Please forgive my lack of response. Your comments are well taken, and there is nothing for me to add. I am in the same boat as everyone else. Sitting a dark room, waiting for the DNN Corp to open the door and tell us what's on the other side.
By Will on
2/18/2009 |
I am also disappointed in the choice of words, but I'm also willing to give DNN Corp a break here. They are currently engaged in something they've NEVER done before (marketing speak, public relations, sales, etc.). We've done all that for them in the past and they're not sure how to pilot or navigate those waves. I've spoken personally with DNN Corp about the pro edition - most of my clients don't want or require that level of support. But there are some large corporate clients who might find it easier to sell DNN into their organizations if it's backed by a support contract. The same thing is true in the Unix world - there are some corporations that will only install versions like Red Hat because they can purchase support for it. In many cases just the fact that they CAN get support doesn't mean they DO get support - it just makes the sell easier for the guy doing the implementations.
It comes down to this - if DNN corp can sufficiently offer a good set of products and services at a reasonable price they'll be in business in 10 years, and their success will drive the success of the CE - floating all our boats. If not, they'll probably just turn the code back into unsupported open source once they burn through their investment capital. No big deal.
I wouldn't worry too much about a fork - if they create a compelling corporate product and price it at a price that will sell - great for them. If they make it too expensive - it won't sell. So far I think they've chosen a price point that is way above the value they're providing. They originally were going to provide development tech support at that price - but no longer. As such it's priced too high and they're struggling to prove the value (and not succeeding).
By Lee Drake on
2/19/2009 |
I have to disagree with you on one point, Lee. They (specifically, Shaun) have been here before. Just read the first chapter of any of the 3 Professional DotNetNuke 3/4/5 books, where Shaun describes how DNN has grown up. It is kind of eery to read some of the similarities in this moment and the moment when Shaun nearly made DNN a subscription model. His words are very fitting for todays challenges.
You've hear a price point for DNN Pro? Really? Many of us with access to inner circles still know nothing. Do tell! :)
By Will on
2/18/2009 |
Remember that, despite the good intentions of the core team members, it is very likely that majority shareholder status is no longer in their hands (post-venture capital). The open model rests on the razor's edge of any given annual meeting.
By Anonymous on
2/18/2009 |
Hi Anonymous... I see your name all over the place. It's good to hear from you here in my very own blog. ;)
While I understand your point as well, I am on the ground floor of a start up myself, which is very similar to what they are part of right now. We both face many of the same challenges and hurdles. The financial stakeholders only have the amount of power that the Board of Directors allow them to have. To say that DNN Corp doesn't have control is just naive. Though, if this were true, we are already in a load of trouble as a community.
By Will on
2/18/2009 |
It is the shareholders that elect the board of directors, not the other way around. It is likely that a VC company is now majority shareholder. Many VC deals are structured to include preemptive rights, anti-dilution, escape-hatch board seats, and both redemption and exit rights.
Interesting times ahead!
By Anonymous on
2/18/2009 |
Anonymous graces me with his/her presence twice in the same day. I am blessed. :)
DNN Corp already had a Board of Directors. While I know we are not privvy to such insider information as to how the Board has evolved since the last press release that mentioned it, it does help to note our last public update of the Board. In it, we see that Larry Augustin was only added to the existing Board. It was not changed. Keep in mind, that the press release I just mentioned was after the Series A funding.
By Will on
2/18/2009 |
Navin Nagiah, has finally weighed in on his blog and explained the press release. I feel much better, and you should too.
By Will on
2/18/2009 |
It might be confusing to your readers that you post your reply to my comment, without posting my comment..... Or maybe I'm just not seeing it here....
Cheers,
Lee
By Lee Drake on
2/19/2009 |
Nice catch, Lee. I had missed approving your comment. Thanks for following up. I really appreciate it.
By Will on
2/19/2009 |
I like the comment that the board of directors control the share holders - you yanks seem to run things backwards over there!
Plus if there is venture capital in there then the community interests come about 5 places below last VC suppliers are not interested in free give aways
PS I am actuiallys Anonymous's brother our mum did not know who the father was
By Anonymous on
2/23/2009 |