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...DotNetNuke Why? (light hearted conversation)DotNetNuke Why? (light hearted conversation)
Previous
 
Next
New Post
5/23/2006 5:21 PM
 

This might make you laugh (or not!).

I'm using DotNetNuke for all my personal websites because I see the scalability, simplicity and sheer speed you can get a solution up and running. And all those modules to hand you can simply upload.

Our main infrustructure is written in ASP.NET/SQL Server so Nuke just seems to be the logical choice as well, esp with our needs and requirements, and I can support it. The portal based functionality and modular scalability simply fits the bill like a glove.

Unfortunately I can't convince my technophobe boss at work, he simply refuses to look at the product. It simply makes him turn green (I see a few hairs falling out sometimes). Unfortunately he's the man who has to say yes to everything (he's my boss after all, so I guess I should listen to him) but won't trust IT people (who work their butt off to help him from day to day). So what's new hey!

Consequently little mini projects are being writting in perl (yes you heard right) which just can't be bolted together. IT department is given work which it really doesn't need to do. Business really has it's head up it you know what when it comes to an IT or development strategy (simply doesn't recognise the problem), yet he still wants a software solution for his various websites (queue smiley sales people knocking at the door, maybe they're sell it to him by stealth).

SO WHY? Well I am totally and utterly convinced my boss just doesn't like the name DotNetNuke. Otherwise he might even just give me 3 minutes to talk about it. Boy what will I kill to do a demo!

Two questions then:

1) Why is dotnetnuke called dotnetnuke. I realise it's written in ASP.NET, but why the Nuke? That bit seems to have negative implications to the tone of the word,esp. to technophobes, e.g. nuke weapons, nuke war, nuke the b**sards etc.

2) Is it or isn't it about time the project got renamed to something that, er hum, quote: "normal" people may relate to? The name appears to put technophobes off no end in my opinions. The very mention of .NET, RSS, ASP or XML sends technophobes running for the hill frothing at the mouth whatever shine you put on it. Any suggesions on what this name could be?

Your thoughts please?

Alex :)



Alex Shirley


 
New Post
5/23/2006 7:16 PM
 

Shaun gives a good explanation of the choice of the name in chapter 1 of the dotnetnuke book -it's a common name in portal/CMS technology and has no war implications. Typically most people refer to it as the DNN framework, as we've grown beyone a pure portal implementation and into a web application framework.

In the past renaming DNN has been discussed, but as it's so well known with that name, any name change would just lead to confusion. The BSD licence has no restrictions on you using/reselling it with the name of your choice (Alex Framework?), so the name shouldn't act as any restriction -it certainly hasn't stopped lots of major companies and government organisations from adopting it (Shaun's blog post mentions a few he became aware of recently). Also bearing in mind that lots of very expensive CMS products have named like plumbtree and percussion express, we got off lightly :)

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/23/2006 7:23 PM
 

FYI: We had some problems with the name in our language and with our customers as well, therefore we provide it using our own brand: "modulio.Net"


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/24/2006 7:54 AM
 

1) Because it is based upon a similar system called PHP-Nuke.  It's their fault, blame it on them.

2) DotNetNuke is open source. Call it DNN or come up with your own brand name.

Make a DNN website with your company logo.  Add a few modules to the home page.  Then show it to your boss. Let him edit something from his browser.

If he remains that far out to lunch, you may have to take your knowledge elsewhere.


Dwayne J. Baldwin
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke Why? (light hearted conversation)DotNetNuke Why? (light hearted conversation)


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