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/7/2007 11:20 AM
 

Agree with what you say.  Also, I don't see anything wrong in offering the modules right along side the framework, and including some of them in the download as is being done.  I'm using Linux, as well, on another machine, and it's not all pretty either, so that critcism is really not justified either.  Afterall, Linux is an O/S not a web development framework.  Yes, many flavors include applications, but that's not the same type of thing DNN is doing at all.

 
New Post
8/7/2007 11:29 AM
 

Oh...I guess I did take it the other way.....

 
New Post
8/7/2007 7:07 PM
 

I am a little concerned that the Core modules will eventually go extinct as some have already have dropped and this might continue.
I currently work in a country where a lot of people don't have 50c to spare, let alone the cost of a new module - no matter how reasonably priced it might seem to me and although I have bought a couple of modules from Snowcovered neither of these were to replace core module functionality.
I abandoned my previous intranet platform because some of the Core modules stopped working and no-one fixed them (I didn't have the tools or knowledge to fix them), and I made the switch to DNN because I saw I could quickly get my Intranet up and running again with improved functionality to boot! I know with the other platform the focus seemed to be on the framework so the project became very targeted at Developers etc and ignored us "ordinary users". It is pretty moribund now. DNN however just keeps growing and as long as there are people who are keen to contribute Core modules I will be glad to see and use them.
I am hoping to have the time to sit down and learn how to make my own modules soon. But if there hadn't been a set of core ones to get me (and all the other newbies) on board I would have probably gone to Joomla.
I have nothing but admiration for the efforts of everyone who has contributed to the DNN Framework and the Core Modules and, at the moment, am trying to contribute in my own small way by answering some of the easier questions that come up on the forums so these busy people don't have to. I encourage all you newbies to do this too. Help free up the veterans' time if you can.
Good on the lot of you DNN peeps!
Cheers, John

 
New Post
8/8/2007 5:08 AM
 

ok, my personal view from my experience as dotnetnuke user, project lead and core team member:

IMHO the modules and associated projects are a necessity for DotNetNuke, because

  • a framework w/o packaged modules, demonstrating its power and options become unattractive
  • as I understand, the selection of bundled modules shall cover basic common needs of web sites. This is, where new modules like a membership directory, map and chat were selected to be developed and get bundled in the future
  • the new release tracking process shall guarantee, that the modules can be trusted and work as "best practices". (There is of cause a downside, that this testing slows down the release process and binds core team resources, but IMO the result makes it woth this)
  • new features of the core needs to be demonstrated and tested for their practical value; in the past, there have been always some of the modules jumping up very fast on the train
  • the need of module teams are also a valid source for extensions or modifications of the framework. e.g. problems of modules with the URLcontrol led into improvements in the past releases.
  • we are also working on identifying features from the projects, that would have a benefit for many other modules and move them to the core framework. This started recently, but I expect a number of enhancements moved in the future
  • projects are a test ground for new core team members. most of the newly recruited members have been team leads before

The current selection of modules demonstrate different developement approaces (DNN3, WSP and WAP) and different levels of complexity - starting with simple Text/HTML up to complex Forums, Store and Repository. This allows each developer to start his own modules by looking at a core module of adequate level. 

PS: John, AFAIK there are no plans to retire core modules and never had in the past. Some are no longer bundled with the core, as they currently don't meet the quality standard and some modules as not under continuos developement due to a missing team (while we are on search of a new one) - and please, always keep in mind that all project teams are run voluntarily. In fact, there have been only two modules retired yet, because they had been superceeded by other modules: Discussions (now Forums) and Contacts (replaceable with more flexible UDT).

As stated in the first line, this is my personal view, not an official position of the core team and DotNetNuke Corp.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/8/2007 11:06 AM
 

Sebastian wrote

PS: John, AFAIK there are no plans to retire core modules and never had in the past.

John Replies

I don't think I or anyone else said there were any plans to retire core modules and no one is advocating that in this thread.  The suggestion was that the core team should focus less on making modules and more on making the framework work better for 3rd party module developers.  In my opinion, the extensibility of the framework is the #1 factor in it's growth and acceptance.  I do realize also that work is continuing to be done in that area and that is a good thing.  It seems that these extensibility enhancements usually come about as a need from internal projects though, and I just think it would be better to even have dedicated resources on the core team that worked on nothing but extensibility features. 

The main point I was trying to get across in my initial reply was that if the official project owners would open up more to promoting all third party development efforts instead of focusing on the "official" dnn module projects, then the entire community would be better off.  The other point I'm trying to get across to anyone that reads this thread is that if anyone spends a little extra time to search out alternatives to the core modules then they will find a lot of value in the third party developer market.

As for the acceptance testing and tracking process put into the official DNN project reviews, that is a good thing to.  All projects should have quality control.  But the problem with promoting that process with the core modules is that it implies that any module that is not "official" does not meet those standards, when in fact a lot of times the unofficial projects are often better.

Lastly, it seems that any suggestion of making things better is often construed as an insult to the people who are "officially" volunteering their time.  The original post in this thread uses some wording that I wouldn't have used, but we should all be open to criticism. After all, can you say that you have not heard any criticism about the "other modules" that are available in the developer ecosystem?

 

 


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