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/11/2008 3:24 PM
 

Ok, before I get to the point et me just say...NO I do not contribute to DNN in any meaningful way. I'm a user. So therefore some think I shouldn't complain. But please hear me out. Think of this more like a good friend keeping his drunk buddy from making a fool of himself. I love DNN and am a big fan, but some things are troubling me. To be fair I'm sure there is an explanation and I don't have the whole picture, but let me tell you what I see.

Why on earth has no one fixed the glaring CSS FireFox issue in the forums. (I don't mean to pick Crispy). I can understand taking time to roll out a fix for the module, but please someone hack something together. It's like DNN is walking around with it's fly down. Embarrasing. Who wants to say "Dude DNN rocks, check it out" when you know this is what they will see.

Plus what's up with the Projects or is it the Forge now? The project pages were a great idea. Unfortunatley many of the pages were not kept up very well. Many have a small one or two paragraph description and are updated rarely. The project blogs in many cases are so out of date that one might think the project is dead. If you say all the activity is in the forums then take down the blogs. They are embarrassing. The forge is a great idea too, but as it is implemented it seems like a DNN step child. Make a decision. Is it the forge or the project and then make it look and act like the first class open source framework that is DNN.

I'll stop there. There is more however.

Maybe DNN is getting too big to operate effeciently. Maybe it's going the way of MS and taking great potential and wasting it by not being able to keep it's act together. If you can't do it right maybe you shouldn't do it at all.

I know....If I'm not part of the solution, then I'm part of the problem.

But at the same time a good friend will tell you when you ripped your pants or have toiletpaper stuck to you shoe.

 
New Post
8/11/2008 6:57 PM
 

Very similar is when posting to somebody's blog on dotnetnuke.com and it requirs a confirmation.

You get a bunch of \n's in the popup.   You are right..  it's these easy to fix bugs that leaves you with questions.

Then you go and read http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1922/Default.aspx

Then you get everyone saying there is no time..  we are volunteers...  but enough time to flame Microsoft.

 
New Post
8/13/2008 8:26 AM
 

Does my post not even warrent a reponse from anyone on the DNN team? Is anyone accountable?

Or do you recognize the problem and maybe just don't have answers? That's ok. No one says things have to be perfect.

But without some accountability (even in a free open source project) DNN is destine for failure or worse mediocrity.

I know it takes people and the right people and whole lot more. Is the current organizational and developmental model capable of ensuring quality and driving innovation and growth?

I am EXTREMELY thankful for the DNN team and community who have made DNN what it is today. Please don't let DNN go the way of so many others.

 

 
New Post
8/13/2008 10:08 AM
 

There's always the question of whether you'd rather have the DNN core team working on making the web site pretty or working on the next version of DNN.  But the solution might be for the core team to include a webmaster, someone to keep links and content current and perhaps fix or push to fix some of the display issues.

In my own personal opinion, these are quirks I can live with.  This type of issue has been in every open source forum or demo site I've seen.  Try looking at almost any support site and it gets dated quickly if there isn't a dedicated team working on it.  Commercial sites can pay someone to do the job, volunteer sites can't always get qualified dedicated volunteers.

Jeff

 
New Post
8/13/2008 10:12 AM
 

I'm in no position to comment, but just a FYI, the toolbars issue you are on about is logged in Gemini here:FOR-7937



Alex Shirley


 
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