Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...So why is DNN Corp Purchase of OpenDNN a good thing?So why is DNN Corp Purchase of OpenDNN a good thing?
Previous
 
Next
New Post
3/26/2010 6:51 AM
 

 Thank you Lars for pointing this out as I am now wondering more on the direction things are going.  It making no sense to not enhance both products and focusing on only enhancing the PE kinda shows a lack of commitment to the CE version of to which will receive no enhancement for a area that even by core standard has pointed out as lacking.

Disappointed

Craig

 
New Post
3/26/2010 12:24 PM
 

I stick by my original statement that DNN is forcing CE installs into paid PE versions. I still think that removing OPEN apps for CE purchase is wrong. Maybe I we need to look at his from a different point of view…

Many developers would not be so resistant to the PE version if it were not SOOOO expensive. I have no problem with DNN making money, but the DNN pricing models are ridiculous. I cannot justify to my customer base $2,000 A YEAR.
I suppose DNN could make some PE versions priced similar Snowcovered pricing structures. A one-time single install price without support, a one-time multi install price without support, a one-time multi install price without support (With Source), etc. – you get the picture.
I am NOT a module developer. I have no interest in building the next OPEN Doc. I build websites based on DNN CMS. When DNN highjacks modules the CE community has embraced and forces us to spend $2,000/YR to get access to a one-time $175 module it makes it very difficult to base our development on DNN in THIS or ANY economy.
 
New Post
3/26/2010 12:41 PM
 
Lars Tungen wrote:
 
There is no wiki. Important information is scattered around on various external sites that appears and disappears as time goes by. Even critical information like safe upgrade instructions and upgrade paths is located on external unofficial sites. 
 

It's coming, that's the best I can offer right now, but a public Wiki for all things DotNetNuke is in the works

 

Lars Tungen wrote:

Dead or slow moving teams. Many core modules have very few releases each year (if any). Not because they are perfect, but because their teams are not functioning. And it's very difficult to find information about how to join a team and submit patches. May be they don't want any help.

 

That too is something that Scott Willhite is focusing on, trying to revive those slow moving teams, overhauling the release process for modules, and speeding up things to make teams more proactive and faster to develop and release.

 

Lars Tungen wrote:

No decent repository for user contributed extensions. "The forge" is a joke and an insult. Nough said. 

 

I'm sorry, but that isn't "nough said". Feel free to step up and provide some suggested enhancements to the Forge. Just saying "it sucks" doesn't do anyone any good except to bitch and moan.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
3/26/2010 2:16 PM
 

I understand that DotNetNuke employees have to defend every decission the corp make. But no one can think its possitive for the community if good modules will be removed for sale "just" for making the PE version stronger.

I do think that the Corp will change mindset and sell the module on the market when the time will come it's in the PE version. As I see it its just a win/win situation. If the PE version not can bee sold on other merits there is no need for a PE version.

Maybe the deal includes paragraphs that make this impossible but I doubt someone could sign such  agreement.

 
New Post
3/26/2010 2:20 PM
 

Just listened to my first DNNVoice edition (you can get it here). In response to that as well as Chris's post here allow me to share the following:

On dnnvoice.com it is explained that "Chris goes on a little rant, he's a tad passionate about the community".  So in other words when someone who agrees with DNNCorp gets "passionate" in their communications it's called a "rant" and when someone who disagrees with DNNCorp. gets "passionate" in their communications it's called "bitching and moaning".  Now that we have the correct DNN terminology let me just say that those who are tired of community members "bitching and moaning" (giving their opinions) may not have to wait too long for a solution. If things continue as they are in another 12 to 18 months there may not be a whole lot of community members left to bitch and moan - problem solved.

While there are a couple of issues regarding the purchase of the Open modules I believe much of the problem here is the same one that DNN has had for some time - piss-poor PR/Communications.  If you weren't ready or didn't know for sure which way you want to go you shouldn't have announced.  I also believe that this thread might possibly be less about the specific issues and more about another straw being added to a growing haystack of discontent.  You'll also notice, if you look at the join dates of the posters in this thread, that the vast majority of the posters in this thread are not DNN newcomers but are the loyal base of the community. That should be some type of wake-up call - or at least I hope it would be.

Last, I always try to offer a solution when I "bitch and moan" (offer my opinion) and I could offer several that deal with individual symptoms.  But why don't we just attack the main problem and thereby solve many of the symptoms at once?  DNN.com needs to become the domain for PE and DNN Corp (since that domain has the big following).  A new domain (accessed via DNN.com) needs to be set up for CE and the DNN community.  That domain/site needs to be built, managed, and maintained by a project team made of up of one or two Corp. employees and a large group of community members. This would give the community members the ability to volunteer for not only technical positions on project teams but also for other positions such as community building, COMMUNICATIONS, site maintenance, free module listing (the new forge), etc, etc., etc.  This way the community might at least feel like they have some say so in what happens to CE.

Ok, got that off my chest - I promise not to "bitch and moan" for at least another 6 months - I'll assume it is ok to "rant" as often as I would like.  I would also like to point out that while there are some issues that seem to be getting bigger and bigger there are some positive things happening too.  The inclusion of Telerik in 5.2 CE, the new Telerik wrappers in 5.3, and especially the new profiles, taxonomy, and messaging in 5.3.  I think it has been a long time since non-technical users have had new features to wrap their fingers around so 5.3 is a bit of a milestone.

Edit:  Opps, forgot to mention the skin contest - another positive thing.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...So why is DNN Corp Purchase of OpenDNN a good thing?So why is DNN Corp Purchase of OpenDNN a good thing?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out