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...Suggestion – Stop making modulesSuggestion – Stop making modules
Previous
 
Next
New Post
8/6/2007 11:48 PM
 

This is just a suggestion. I realize a lot of hard work hard work has gone into making modules for DotNetNuke. But let’s face, this is no Linux. Most of them are not very good, a great many haven’t been updated in ages. Sure they are free, but for only for 10-40 dollars I can get something much better. How many serious websites are using the core modules? DNN is a great framework for third party module developers, who have the time and resources, to make great modules.

Focus on Security, Search, Performance, and Control. The things that make DNN great. Not modules that haven’t been updated in the past year.

Thanks.

 
New Post
8/7/2007 10:24 AM
 

This suggestion has my vote.

I agree that the core focus of the core team should be on the core framework.

The opposing argument will be that the modules are actually not developed by the core team, but by separate project teams though.  One way to look at it is that the DNN Module Projects are not really any different than any other free modules you can get from the developer ecosystem.  

As long as someone spends a little time understanding what is available there are many great alternatives to the core modules.  Just because it is an "official" DNN module project does not mean it is any better. Cost does not always have to be a factor either, but I believe monetary incentive goes a long way in providing dedication to the task of supporting and enhancing a project.


DotNetNuke Modules from Snapsis.com
 
New Post
8/7/2007 10:42 AM
 

Well I disagree...I think the core modules have a place within this open source project.  If the core modules were not there, then once folks download the core, they would then have to go to snowcovered to get modules just to make their portal even work.  TO me that doesn't make any sense.

I think the core modules are great.  It gives you a point to start and if you want to expand on what's there you can buy something better from a third party.  And it's my humble opinion that because there hasn't been very many core module updates, that core team has been focusing on the framework.  That is evident from all the core releases. 

Personally I would like to see less core releases...It is my humble perspective that pre 4.4.1 when there were less releases per year, they were a bit more stable.  Now that the core team has switched direction on trying to appease the masses by releasing core updates more frequently they are rushing the core out.  I'd much rather see a release 2 -3 times a year that has been tested.  For example when 4.5.4 came out something required 4.5.5 to be releases.  WHich I understand it happens, and I applaud the core team for doing so, but it appears thats common practice after 441. 

I think if the core reduced the number of releases, they would reduce their stress and release something good.  Not that they aren't now.  I hope they are not letting people's high expectations drive them.  Fore a FREE CMS, this project has made vast improvements over the last year and I expect more great things are coming. 

Jerry

 
New Post
8/7/2007 10:48 AM
 

There is much truth in what you say, my trusted friend (John).  I've always thought of the modules as a learning tool, which helps me understand some of the methods being used in the Core Framework.  The modules may not be as good or updated as frequently as we like, but they are a good tool for developers, and I doubt that many other 3rd party modules would have been developed had these examples not been available. Some of the 3rd party modules still have code from these modules in them.

I'm just as frustrated as the next person with the slow progress on some of the built-in modules, but I understand that the DNN Framework IS the focus for the most part.  It's hard on the Core Team to focus on the modules with the attention placed on the framework.  As you mentioned, DNN's modules are mostly efforts of active DNN members with some oversight by the Core Team, so the focus is in the right place, as far as the Core Team's efforts go.

If anything, the Project teams need to step up the pace, but even that is difficult with the time it takes to test and integrate with new DNN framework updates.  All said, I'd prefer, at least more communication on the status of these projects throught the project Blogs, rather than in the forums in answer to a project forum post.  The posts come so fast that many communication responses are lost, unless you go through a lot of pages.

But, I digress, and I've said it all before.  Just can't help it...

 
New Post
8/7/2007 10:51 AM
 

Maybe the title should have been. "Stop making new modules".  That was the way I understood the original post.  I agree that it is nice to have a place to start, but i don't see any problems with seperate module packages being available right alongside the core download.  The community could rate and review all these modules and make a much better start than just the core modules alone.

Here is an example that seems to work really well for another well known open source project:  http://extensions.joomla.org/


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Suggestion – Stop making modulesSuggestion – Stop making modules


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