Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsFCKeditorFCKeditorLicensing implications? FCKEditor is LGPL and DotNetNuke is BSDLicensing implications? FCKEditor is LGPL and DotNetNuke is BSD
Previous
 
Next
New Post
4/13/2006 2:03 PM
 
David A-W

Joined: 12/21/2004
Posts: 30
Hi, can you let us know what the licensing implications are for companies selling DotNetNuke installations commercially?
 
New Post
4/13/2006 6:39 PM
 
Mauricio Márquez

dnn.tiendaboliviana.com
Joined: 5/5/2003
Posts: 1126

You must take in mind that you cannot sell open source code. You can sell your services installing it, but your are not selling the product itself.

I think this could have implications if your are offering DNN or FCK as your product. You must offer "DNN Installations" or "FCK Installations"

At this moment, there is a established relationship between DNN and FCK about using FCKEditor inside DNN and exchanging references. You can visit: http://www.fckeditor.net and you will see an announcement about this there.

DNN and FCKEditor have different license types, but both are open source and they both can be still used because they still are separated projects. I will try to clarify more later on the project page.

Returning to your question, you must be clear on what you are offering

Hope it helps

Locopon
Free modules: E-commerce, Complete localization (Portal, page, module settings, skins, etc.), Secure Login, and more
http://dnn.tiendaboliviana.com
 
New Post
4/13/2006 6:58 PM
 
Mauricio Márquez

dnn.tiendaboliviana.com
Joined: 5/5/2003
Posts: 1126

Just to complement:

There many people there selling their modules, and most of them allows your to install and use their modules with the normal license. You are not always allowed to re-distribute those modules

Ask your modules providers for this kind of permissions. Most of times, you will need to buy redistribution licenses to be allowed to install them for others (the cost of this kind of licence could be higher).

Maybe you can continue this thread on the "Let's chat about it" forum here:
http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/118/scope/threads/Default.aspx

Locopon
Free modules: E-commerce, Complete localization (Portal, page, module settings, skins, etc.), Secure Login, and more
http://dnn.tiendaboliviana.com
 
New Post
4/14/2006 4:29 AM
 
David A-W

Joined: 12/21/2004
Posts: 30
within the "let's chat about it forum" I found this thread:
http://www.dotnetnuke.com/tabid/795/forumid/118/threadid/28989/scope/posts/Default.aspx

Under the terms of the BSD license:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software ...

So as you say, yes there are implications w.r.t. using non-core modules that have different licenses - typically if installing externally, that means purchasing another site license, etc. 

I guess what I'm asking is that even though the FCKEditorProvider is now an official DNN project, I'm assuming we need to treat the FCKEditor component that it uses in a similar manner to other 3rd party modules - so what are the considerations?
Is it just that when installing, we need to include the LGPL license file & copyright notice in the site files? 
(couldn't spot anything apart from this on the FCKEditor site)

As an aside: I know that the Survey project team tried to negotiate to sub-license 3rd party nSurvey code under BSD as part of DNN, but this fell through so they are no longer planning to integrate (under the core "DNN" banner anyway).
 
New Post
4/25/2006 6:15 PM
 
Scott Willhite


alkihomes.com
Joined: 4/11/2003
Posts: 3047

Two things.

1) We've been diligent in working with the FCKeditor team to ensure that we have permission to redistribute their executables along with our Editor Provider.  However, FCKeditor does ( in fact ) have it's own licensing which is currently Open Source - LGPL.  We will not, however, redistribute source with the Editor Provider ( which will be designed for use with a specific version of the FCKeditor ).  There will be no "FCKeditor" specific actions required by someone installing the provider with respect to licensing.  The applicable files will be installed with the provider.

2) As with ANY software, one must be conscious of the licensing.  One reason DotNetNuke utilizes a provider model implementation is to enable supported use of alternatives... which come in either free or commercial flavors.  It is our sincere hope ( and belief ) that the FCKeditor will remain free and open source, just as DotNetNuke will.  However if ( for any reason ) someone felt compelled to change Editor Providers, it could be done universally with a configuration change ( in the same way that switching TO the FCKeditor Provider is accomplished ).

All code provided by DotNetNuke is provided under the same BSD license as the core framework.  This particular project represents our very first foray into wrapping third party controls in an "official" project... but it is likely not to be the last that you will see.  While anyone is free to create wrappers for any third party controls that they wish... offiicial DotNetNuke Projects will likely be limited to those controls with extremely broad appeal ( such as an alternative provider ) or very widely used commercial controls.

Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry
 
 Page 1 of 1
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsFCKeditorFCKeditorLicensing implications? FCKEditor is LGPL and DotNetNuke is BSDLicensing implications? FCKEditor is LGPL and DotNetNuke is BSD


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