Shaun Walker wrote Clearly PowerDNN does not have the slightest clue when it comes to these matters. But I don't buy the 'ignorance as an excuse' argument. How can anyone continue to make one brutal mistake after another? At some point you need to come to the conclusion that perhaps these are not mistakes at all. Based on recent events it is starting to become clear that PowerDNN has malicious intent and is working through a series of premeditated steps to unleash it on the DotNetNuke community. I am still waiting for the conclusion to all this which I hope will clarify the end goal. Because at this point I completely fail to understand the logic behind the actions, especially considering the fact that PowerDNN has built a successful business on the backbone of the DotNetNuke project/community. I guess time will tell...

You want to know why? Because they think they are strong and influential enough to do so. They can ask or hire some people keep posting that they are innocent and they did what’s best for their customers. Because of BSD license, they can create "a customized build of the DotNetNuke Web Application Framework" on top of "a standard 'vanilla' version of DotNetNuke", which make people think that although they didn't "make DotNetNuke", they "make it better" or their version is better. You see, they think have nothing to lose.

Michael Gerholdt wrote Frank, Puh-leeze. PowerDNN is hiring people to post nice things about them to this forum? Absurd.

That's exactly what's happening. Some people kept asking the same question in the forum even it has been answered by different core team members. This keeps pressure on dnn corp and make people think dnn corp is incompetent and didn't deal with the situation properly, although most people will know who is good guy and who is not if they read the full story.

Edited: By "some people", I actually meant someone in this post. Sorry about confusion caused by my poor english.

AliCommerce wrote  This keeps pressure on dnn corp and make people think dnn corp is incompetent and didn't deal with the situation properly, although most people will know who is good guy and who is not if they read the full story.

For what it's worth, I agree that DNN corp didn't deal with the situation as well as could have been done ... but that does not at all go hand in hand with considering them incompetent, or considering them to be other than "the good guy." I think many folks would agree with that. In fact, it might even be true, and not just an opinion.

Very interesting drama, but I'd rather have seen it as the plot of a made-for-TV movie than scuttlebut surrounding DNN, acted out in real life on these forums. Makes me want to protect DNN from those who use it, and to some degree, even from those who sustain it. Not, of course, that there is any way I could do so.