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...Why is DotNetNuke giving itself a black eyeWhy is DotNetNuke giving itself a black eye
Previous
 
Next
New Post
8/18/2008 1:12 PM
 

You're right Mitch.  There have been lots of improvements, but nothing major.  Getting AJAX was really a good plus for DotNetNuke, but it wasn't newsworthy.  When it was finally delivered, it was pretty darn buggy too (remember all those ScriptManager errors?).  Provider-ized authentication is nice, but who uses different authentication?  Not very many people.  In DotNetNuke 5.0 they now have a "widget" framework.  When I went to OpenForce Connect and got to see the official DotNetNuke 5.0 demo, I was very un-impressed.  It would have been really nice if the Corp had invested time in concrete features like Versioning instead of abstract concepts like "widgets".

Does anybody remember when DotNetNuke 3.0 first came out?  I still remember when I first got my hands on 3.0.  My heart was pounding, my hands were shaking, and all I could say was "Holy Crap!  This is is awesome!".  It was soooo much nicer than 1.0 and 2.0.  That didn't happen when 4.0 came out.  That won't happen when 5.0 finally comes out.

 
New Post
8/18/2008 1:38 PM
 

My point in mentioning the DNN_Blue skin is that DNN is becoming stale, at least as far as look and feel goes.  DNN has a lot more flexibility and "under the hood" power than many of the other open source systems, but it is still rather dated.  I don't think that 4.0-5.0 changes have been underwhelming, the performance improvements alone were worth the trouble for upgrading.  I often complain that changes happen too fast, but mostly because documentation lags so far.

I don't have a solution.  but I'm pretty sure the solution isn't to rely on the core team to fix these issues.  If it was, the issues wouldn't exist now.  It might be the core's job to organize solutions, but I don't think the qualified staff has stepped up that can be assigned. There are modules that are really outdated, and several that have been having fantastic progress of late.  Documentation sucks, but I'm not sure that relying on coders to produce it is any better.  There really need to be project managers that handle the organization and documentation of products but don't handle programming.  Again though, I'm not sure qualified people are available.

But, I am willing to contribute to the problem.  Uhh...  I mean the solution.  :)

Jeff

 
New Post
8/18/2008 1:51 PM
 

Tony - Let's get this straight... two and a half months ago, at OpenForce Connect in Florida, you saw the DotNetNuke 5.0 demo and were "very un-impressed."

Today, you're continuing to suggest that no one's hearts will be pounding or hands will be shaking after they get a copy of the final version of DotNetNuke 5.0 after it comes out of Beta testing.

All very interesting, considering the fact the title bar on your website's title bar has been blaring "DotNetNuke® DNN Hosting > Home [DotNetNuke 5.0.0 Cambrian Cluster on Windows 2008]" for months now.  Considering that DNN 5.0 isn't in production yet, and you're declaring it a bust already, it's a pretty interesting marketing tactic you've got going on there...

 
New Post
8/18/2008 2:32 PM
 

Just like any person using DotNetNuke, when 5.0 is officially released to the public, we're going to jump on the bandwagon and say "DotNetNuke 5.0 Rocks!  Get it now!"  Who wouldn't?  We're certainly not going to say "Get DotNetNuke 5.0 now!  It is a big bugfix!"  That wouldn't be good for anyone.  We want to do everything we can to create as much hype about 5.0 as possible to someone on the outside looking in.

However, as a long-time member of the DotNetNuke community and as a former project lead, it is really hard for me to get pumped about 5.0.  If you look at all the Gemini work on 5.0, and scroll to the Enhancements and the New Features section, there's nothing major.  No casual DotNetNuke user is going to say "Oh my gosh!  They've added the [IActionControl] Interface!  This makes my life so much better!".  No enterprise architect is going to tell his boss "You really need to consider DotNetNuke 5.0 for this project.  They've just added [The option to select your docType] which makes DotNetNuke a much better fit for us than Alfresco".  Replace either of those items with an enhancment or new feature in 5.0, and it just doesn't sound right.

I know this analogy breaks down at points, but when DotNetNuke 3.0 came out, I felt the same way I did when I upgraded from Windows 3.1 to Windows 95.  4.0 was like Windows98, and 5.0 was like Windows98SE.  Windows 95-98SE were all pretty much the same.  When XP came, things were noticibly different.

I don't want this to turn into a thread hammering the Corp.  I used to work for a software company and and I think of all people in the community, they've got the hardest jobs by far.  I'm glad they write the code for DotNetNuke because I certainly wouldn't want to.  But, I do think that the Corp has lost focus on what originally made DotNetNuke great and that will be obvious when 5.0 comes out.

 
New Post
8/18/2008 3:56 PM
 

I was wondering how long it would take before the first flame showed up in this semi-controversial subject.

I'm pretty impressed - we made it through 35+ posts before the first flame!!!

I'm just glad we are having this discussion - even if it is all in one thread!

I think most people would agree with Jeff - the blue skin is very stale - and, sorry guys, the new one doesn't look a whole lot better.  I'm guessing this has less to do with abilities and desire than it has to do with resources and time.  And once again I think the problem is the same as with most all the other issues with DNN - a small group of people trying to do everything themselves. With regards to the skins - why not have a skin contest - with the top five being included in the release??  Why should the core team spend time on this when there are huge numbers of skin developers, both commercial and individual, who could do this and would love to contribute?? (either for monetary gain - commercial developers or bragging rights - individual developers)

And back to the original post - the website. While it's visual design was cool and got a lot of kudos when it was built it could use a refreshening. Especially with regards to content.  Click on the DNN careers link to see what I mean.  With regards to the home page you only have a few seconds to grab someone's attention and interest to make them want to dig deeper.  Since the main question most every potential new user has is "What can it do?" and/or "Will it do what I want to do?" (how many forum posts have we seen along these lines?) I could envision the left panel being screen shots of what can be accomplished with DNN. i.e. First picture could be a full blown relational web app built with DNN and ListX (or better yet get Kevin to build one in OWS showing it's ability to integrate with Google Gears!), next picture might be a shot of one of the two main document management modules for DNN, and so on with a link at the bottom to a whole page of screen shots!  That's just one idea and I won't go into the others but the two points of this post is things need refreshening and the cummunity needs to be allowed and asked to contribute.

With regards to the new features of DNN 5.0 - it seems to be a constant battle between new features and bugs.  A year to year and a half ago the main bitch was bugs. Then the core came out with the project release system and now it seems to take forever for a project to make it through the system - of course they are close to bug free when they come out.  There were also lots of complaints with the core project in this regard - in the 4.3 to 4.6 range a new release would come out and you would wait at least a week for 3 patches before you tried it. I'm guessing the powers-that-be are using the same approach on 5.0 as they are on the projects which should mean that it will be pretty clean when it comes out but it is 3/4's of a year behind schedule with less new features than orignially planned. So the question is if you can't have everything which is the lesser evil??

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why is DotNetNuke giving itself a black eyeWhy is DotNetNuke giving itself a black eye


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