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...Licensing implications on integrating custom controls (web parts) in a DNN site Licensing implications on integrating custom controls (web parts) in a DNN site
Previous
 
Next
New Post
2/25/2008 10:04 AM
 

Hi All,

My question (which I believe is very basic...) is:

I am planning on having a commercial B2B web site built using DNN. At a later point, I might want to add .NET Custom Controls (web parts) onto the site. This code is proprietary (and is actually a part of a product we sell). Can somebody please elaborate at what point there will be the consequences in terms of licensing. Our company is probably not ready to turn our product code into open source code.

Thanks in advance!

Niklas Johnsson

Head of Product Marketing, T-systems Nordic

 
New Post
2/25/2008 7:45 PM
 

DotNetNuke uses BSD as it's licence (see http://en.wikipedia.org/wiki/BSD_license for a description), which is a commercial friendly licence i.e. it's not a viral opensource licence such as GPL where new code "inherits" the licence. .In real terms it means you can do what you like as long as you retain the dotnetnuke comment blocks at the top of each page i.e you don't have to tell your customers that you're using an opensource project, and you can make any changes/renames etc you desire without having to contribute them back or credit them.

"DotNetNuke is provided as open-source software, licensed under a BSD agreement.  In general, this license grants the general public permission to obtain the software free-of-charge.  It also allows individuals to do whatever they wish with the application framework, both commercially and non-commercially, with the simple requirement of giving credit back to the DotNetNuke project community. "

 


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Licensing implications on integrating custom controls (web parts) in a DNN site Licensing implications on integrating custom controls (web parts) in a DNN site


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