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/20/2008 10:03 AM
 

Tony Valenti wrote
 

now, this is my oppinion, but I definately would agree that a build or release should not be held up because Shaun Walker, the benevolant dictator of DotNetNuke, happens to not be available.  Sure, that's important stuff, but executives and figureheads shouldn't be writing, deploying, or managing software - they should be being executives and figureheads.

It's not just your opinion, it's good practice, that's why releases aren't held up by 1 person being unavailable. We have an automated build process (Joe describes this @ http://blog.theaccidentalgeek.com/post/2008/07/05/DotNetNuke-Independence-Day.aspx ), and there are a number of people with the rights to upload the release to sourceforge and create the necessary announcements etc.

So far I've thought this thread was quite valuable, with most of the criticism being constructive in it's nature. I'd prefer it it stayed like that and didn't descend into an unhelpful thread full of speculation and (incorrect)guesses at the internal workings of the corp and core.

Thanks,
Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/20/2008 10:19 AM
 

ROBAX wrote

I believe it's important for new people coming into the scene to accept DNN simply as they find it rather than expect it to be like anything else, especially not a commercial product.

Echo that.  Please, please, please don't change DNN, no matter how much we whine about it needing to change.  There's a reason I'm using DNN instead of a commercial product.  There's a reason I don't use Joomla.  Or even Umbraco.  Or Community Server.  And I'm not sure I can put a finger on what that reason is.  I actually like Joomla and love both Umbraco and Community Server.  But not for what I use DNN for.  While there are parts of the others that I wish were in DNN or that DNN did better, as a whole DNN wins.  Even with the flaws.

And this thread has made me realize that I really do need to commit to giving back where I can.  As soon as I can find that piece that makes DNN better than if I had left it out, I'll do it.  Now, if only DNN needed the input of my mad Pinball skills...

Jeff

 
New Post
8/20/2008 12:08 PM
 

I don't think that the DotNetNuke platform needs major changes, but I do think that it needs a buttoning up and a polishing to stay competitive.  As I have mentioned before, last year, at OpenForce Vegas, Cambrian was promised in January and right now, it is very late.  I know that things have happened that have interrupted and slowed things down, but not almost 3 quarters worth.

When it is all said and done, we all need the Corp.  At PowerDNN, our staff is built do to one thing:  Support.  Everything else that we do is really just an extension of that.  We're just not cut out to run a development shop, and we certainly don't want the responsibility that the Corp has for furthering the Platform.  :)  However, when the Corp or the platform is having issues, the issues affect the entire community and as a member of the community, I want to propose every feasible solution to help them out.  Every decision they make or line of code they write has a wide range of impact.  When there's a major DotNetNuke bug, that hurts us a lot.  We've been definately taking an interest in betatesting 4.9.0 as well as the 5.0 betas.

By the way, it is coming up on 2 months since Cambrian Beta 6 was released.  Do any core/Corp guys know when the next build is scheduled to be available?

 
New Post
8/20/2008 12:30 PM
 

Alex Shirley wrote
 

... I notice you have had an advertisement out which states, and I quote:
"MORE SUPPORT - PowerDNN's AtomicSLA gives you access to the world's most knowledgeable experts 24/7/365. With an English-speaking, USA based support team, when you need help, you'll be talking with someone who knows your issue, understands your problem, and does not have an accent!"

Is PowerDNN an equal oppertunies employer? Pray tell please exactly do you mean by "not have an accent". I'm from the United Kingdom, does that qualify me as not having an "accent"? What about other English speaking people who may come from other counties, do they have accents in PowerDNN's view? What exactly is wrong with an accent?

Pretty insulting to some, I'm certain.  And I don't think you'd find too many businesses or corporations advertising their services in this manner.  It's even more odd considering that such a large portion of DNN's user base - and developer talent - resides outside the USA.

This again reminds me of one my wife's favourite sayings - "Kehre erst vor deiner eigenen Tür."  Translation: first sweep in front of your own door.  (She is a recent emigrant from Germany.)

Everybody is giving the DNN team suggestions as to how this project can grow, thrive, and expand.  Often, fingers get pointed in one direction, but certain finger-pointers continually refuse to look in the mirror themselves.  They promote their companies by saying "Don't use DotNetNuke," run confusing advertisements, include questionable ad copy (like above) in printings of international books based on DotNetNuke technology, spark security scares - the list goes on-and-on.  The DNN team addresses these issues in a public forum, but they go ignored. 

So Tony, you say PowerDNN has now re-factored how their management works... you have people in roles in your company who have decision-making abilities, and are responsible for getting things done.  I have a suggestion - if you can forward over the names and email contacts of these management people in your company, we can speak to these people directly about the issues that have been discussed in this forum.  So far, neither yourself nor John Grange have made these changes (perhaps there is a bottleneck somewhere.)  You have our contact info - we'll be interested to hear from you.

 
New Post
8/20/2008 1:22 PM
 

Tony, will you answer my post please? I've labelled each question from a to e to make life easy :)



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