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/15/2008 6:33 AM
 

Yes. Thank you Cathal. I appreciate your time and response.

I have to say that I understand all the points you made and I think I understood those before I posted. What I don't see is who the community should be holding responsible. Unless I can infer from your post that we can hold the core team accountable. That sounds like a logical place to me. If so then please represent these views to the core team.

The DNN website should represent the best that DNN can offer not just in an application, but in content and community. This is what most people naturally expect. People are looking and there are more and more reasons not to be impressed.

I have often been accused of living in utopia but I have learned to have more realistic expectations. At the same time I think a high level of excellence can be achived under the right conditions and I try to have that as a goal. You stated quite clearly my hopes for DNN as well when you said: "i hope we can exceed the standards of proprietary software" but I would go further and say "exceed the standards of any software" becuase propriety as you well know doesn't mean a whole lot these days.

My answers to the problem:

- Hire people: To me DNN now has enough of a following and reputation that it should able to apply some business model which would allow it to take on enough top noch staff to meet or exceed expectations. This can be done while still keeping with community driven open source standards. At least that's what I think should be possible.

- Make excellence a priority without excuses. I know what people are thinking "If DNN focuses on fixing every little bug and keeping the site updated there won't be time for any new features or innovation". Your right, unless you add more of the right people to the project and have people to mamange and organize the work. That brings be back to my first point. Hire people - Incentivise volunteers.

Thanks for listening.

 

 
New Post
8/15/2008 6:38 AM
 

Just want to correct an inaccuracy here without commenting too much on other stuff:
"I just read a blog entry about a big fix for the forums code; it can finally parse the word “a1ert” properly".

I believe this was a fix in core code that was effecting a whole load of projects. So to say other things in the forums project should have been fixed first may be true, but priorities are done on a project by project basis. This fix was done by the core project team, not the forums team. Core code was corrected, not forums code.

... and if I’m wrong here, maybe somebody could correct me!

Thanks

Alex



Alex Shirley


 
New Post
8/15/2008 7:04 AM
 

Andrew Hawes wrote
 

- Hire people: To me DNN now has enough of a following and reputation that it should able to apply some business model which would allow it to take on enough top noch staff to meet or exceed expectations. This can be done while still keeping with community driven open source standards. At least that's what I think should be possible.

- Make excellence a priority without excuses. I know what people are thinking "If DNN focuses on fixing every little bug and keeping the site updated there won't be time for any new features or innovation". Your right, unless you add more of the right people to the project and have people to mamange and organize the work. That brings be back to my first point. Hire people - Incentivise volunteers.

Thanks for listening.

 

Andrew,

I agree with you, but theres a simple flaw here - to hire people you have to have money, a commodity that dotnetnuke doesn't have much of at present.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/15/2008 7:05 AM
 

Alex Shirley wrote
 

Just want to correct an inaccuracy here without commenting too much on other stuff:
"I just read a blog entry about a big fix for the forums code; it can finally parse the word “a1ert” properly".

I believe this was a fix in core code that was effecting a whole load of projects. So to say other things in the forums project should have been fixed first may be true, but priorities are done on a project by project basis. This fix was done by the core project team, not the forums team. Core code was corrected, not forums code.

... and if I’m wrong here, maybe somebody could correct me!

Thanks

Alex

you're correct Alex, the issue was in core code, it wasn't a forums issue. The fix is in the new 4.9 release.


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

cathal connolly wrote
 

 Andrew Hawes wrote
 

 

- Hire people: To me DNN now has enough of a following and reputation that it should able to apply some business model which would allow it to take on enough top noch staff to meet or exceed expectations. This can be done while still keeping with community driven open source standards. At least that's what I think should be possible.

- Make excellence a priority without excuses. I know what people are thinking "If DNN focuses on fixing every little bug and keeping the site updated there won't be time for any new features or innovation". Your right, unless you add more of the right people to the project and have people to mamange and organize the work. That brings be back to my first point. Hire people - Incentivise volunteers.

Thanks for listening.

 

Andrew,

I agree with you, but theres a simple flaw here - to hire people you have to have money, a commodity that dotnetnuke doesn't have much of at present.

Cathal

I would like to say that Cathal points out the most important part of this.  Money I'm sure is a big factor, incentives for volunteers?  Wow, that would be nice....but it isn't practical.....


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
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