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/9/2007 9:08 AM
 

So here is a slightly different question along these same lines.  From time to time the core team and DotNetNuke Corp develop custom modules to meet a specific need of the project or the Corp.  Sometimes these modules are of a general nature, like the release tracker or roadmap modules, and could be beneficial to the community.  We do not intend to start new projects around these modules or include them in the core release, yet there is some interest from community members with using these modules for their own sites.  These modules would not likely include much in the way of documentation and may not even be examples of best practices.  In several cases I know that they are quick and dirty hacks.  Should we release these modules, knowing they may never receive another update (unless we find internal needs drive additional enhancements)?  If we release them, what are people's expectations?


Joe Brinkman
DNN Corp.
 
New Post
8/9/2007 11:11 AM
 

What if we followed the more open source strategy....      reduce overhead on project releases ..    let everyone test ....           

Waiting 4 months for a bug fix to be released is a long time....     

 
New Post
8/9/2007 11:15 AM
 

Joe,

I do not think anything like that should be "released" by the core team.  There has been more than one module developed in the way you describe and "released".

If the code can be made available with clear intentions and management of expectations then that could be acceptable, but I believe anyone releasing code as open source should stand behind what they are releasing and be prepared to help people understand it.  If the project is specifically labled as "sample" code with no version numbers then expectations should not get out of line.

Clear seperation between code for developers and "released" modules for end users needs to be given. 

Just because someone "official" developed it does not mean it should be released through official channels.  I understand there is some presure to make these projects available, but it is the responsibilty of the people in charge to properly manage those pressures so that misconceptions like that with the "what's new" module are not common.

On the other hand, if someone in the community is willing to take the sample code and enhance it, and then support it, then that should be encouraged.  It does not have to be brought back in and made official to encourage further development and support either. 

Is it just me, or does anyone else see what I am saying is exactly how DotNetNuke (IBuySpy Workshop) started out?


DotNetNuke Modules from Snapsis.com
 
New Post
8/9/2007 1:27 PM
 

Joe,

I would agree that it would be nice to see the modules such as the Release Tracker and other items provided to the community, but I agree with John that those might need to be "released" in a different manner.

I personally think distributing a code only distrubution of the Visual Studio Solution might be the best approach for that type of thing.  THen there is an understanding that the individual MUST know how to package it and go with it from there.

I have a feeling that releasing it as a packaged module might setup some false expectations, however, I also see where keeping them private has created some 'tension' if you will within the community.


-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...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