Re: What happened to your beloved DotNetNuke?

I think releasing the "PE" edition is fine, but I question if it is the same code base in CE... This is from the FAQ:

DotNetNuke Professional Edition includes additional security, stability, and support assurances for production or mission-critical applications, and is available at a substantially lower cost than alternative proprietary solutions.

How can the CE version not have the "...additional security, stability..." elements that the PE version has?

Re: What happened to your beloved DotNetNuke?

I am considering registering DotNetNuke in the UK as a religion....
please let me know your thoughts :).

Re: What happened to your beloved DotNetNuke?

Is there any difference in the code of Pro and Community Editions?

Re: What happened to your beloved DotNetNuke?

Chris, I see this as a normal evolution. I guess I've been in a unique place as a former member of the core team. I always knew this was going to happen and really its always been said by Shaun that addtional resources where needed. DNN has allowed many people who never have coded on the core to build a viable business model and the core deserves that same right.

I don't code that much with DNN any longer as the day job got in the way, but I follow this project closely still and will still install it when the need arises. I see this as positive and with the BSD license if things where to change, there is always the option of someone else picking it up and running with it.

Re: What happened to your beloved DotNetNuke?

@Jonathan Johnson,
Note: I'm not aware of what form the "additional" security could take but there are plenty of options such as direct email contact/notification of security fixes, testing of proposed patches onto support sites, providing of code changes required so that enterprises can choose to make the changes rather than update etc. All of these would be good value-added services for users of a pro version. I could also envisage other options such as purchasing (at discouted rates) services such as security auditing of custom modules or training in development of secure modules.

At the end of the day, theres not a huge amount of point worrying about what these will take, I'm sure the corp will be posting more in the next few days about the composition of the pro offering - i'm also sure that this won't be fixed, and will evolve over time.

Re: What happened to your beloved DotNetNuke?

@Alex Shirley,
If you're looking to find right religion, I can help you :).

Re: What happened to your beloved DotNetNuke?

In regards to security, probably just more of a standalone updating. What I mean is if they find a small glitch / hole that is barely noticable but still one. aka a super low priority security issue. Pro version would get the option to just patch the one fix, while the community would end up on wait till they fix a few others etc.

It works well both ways, businesses that worry / have much much more at stake, possibly billions of dollars, get a good warm feeling, have the resources to do constant updates, and dont mind.

Meanwhile the average community user would be haggled with so many constant updates to their sites, when there typically wouldnt be a problem / issue.

Also in regards to security, remember its not just about hacking its about administration. What I mean is the DNN Core has an ok AD connector but for a large business this presents risks. Some added benefit could be better AD administration from within DNN. This being the case once again your average user / power user wouldnt really have an AD (active directory) setup. But for a larger business this would be a key area.

There is lots of room for the two versions to differ, without either being better than the other just different. Also if this gets extra funding, and the teams can get payed / expand. Then more stuff will be added on a regular bases. Business love getting new shinies.

Re: What happened to your beloved DotNetNuke?

@Alex Shirley,
If you're looking to find right religion, I can help you :).

Re: What happened to your beloved DotNetNuke?

I think both editions will have their place, but I don't think security is one area that they should differ. It only takes one significant security breach and I am out of business or I will lose a significant amount of users regardless if I am a billion-dollar multi-national company or a startup. If I would have had the opportunity to download the patch prior to the breach then that could have saved my business. I know there is a risk that the patch could cause possible disruptions to my site, but that is the chance I would be willing take and err on the side of caution as it relates to security.

Once my business grows and it makes sense then I can purchase DNN Pro.

So there you have it...My vote that the DNN Community edition has the same security feature as DNN Pro.

Re: What happened to your beloved DotNetNuke?

I think that the team has made the right choice. This will open up many more possibilities for our beloved DotNetNuke.

Re: What happened to your beloved DotNetNuke?

The way I understand it when they talk about stability they are talking more about what version is packaged with the pro version. The pro version is currently the latest 4.9.2 version, even though 5.0 has been released. The pro version will not be upgraded to the 5.x version until it has been in the wild for some time and more bugs fixed (thus more stable)

This means that as a business you are getting the most stable version of the program. But as a user of the CE edition you are free to download the latest and greatest and use it for testing, production sites, etc. This does not mean the releases immediately following the community edition are not stable. It just means that as developers we all realize that once a product is released to the general public that there is a good chance that more bugs will be reported, no matter how good of testing was done before the release. IMO the pro edition will protect any business I recommend to use the pro version from being negatively affect by a possible "surprise bug" that was missed in internal testing.

Some form DNN Corp might wan to verify this, but that is the way I understand it when they are talking about the stability of the professional edition. And as Cathal stated about the "additional" security feature of the pro edition, there are also many options that have nothing to do with the code base being different DNN Corp could offer to provide a more stable product to those who decide to pay for the pro version.

Bottom line is this will continue to evolve and right now the DNN Corp has not given anyone any reason to think that the codebase between the 2 will be different. Therefore to speculate otherwise it just worrying about something that might never happen. The pro editions is a good thing and give DNN more credibility with businesses who would never us it as an OS product.

Re: What happened to your beloved DotNetNuke?

For those concerned about the future of Community Edition - I would suggest that the important thing to remember is that "Actions speak louder than Words".
It doesn't matter what we say - its what we do this year and in the future.

I believe that the benefits of the increased funding will be that CE will become a much better product, and thats what we all want.

Re: What happened to your beloved DotNetNuke?

May be it is a right choice.