Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

AspDotNetStoreFront
  Ads  
Iron Speed Designer is a software development tool for building database, reporting, and forms applications for .NET without hand-coding.
 


  Sponsors  

Meet Our Sponsors

R2integrated - formerly bi4ce
Jango Studios - Skins, Modules and Hosting for DotNetNuke
eUKhost.com is commited to offer exceptional UK Windows Web Hosting solutions with quality 24x7 technical support.Our plans support ASP.Net, ASP, ASP.NET Ajax extensions, XML, MSSQL, MySQL, PHP,DNN, multiple domains and Shared SSL as standard.
SmarterTools
Verndale
The Official Microsoft ASP.NET Website
 


DotNetNuke Forums
 
  Forum  DotNetNuke® Pro...  Blog Module [Le...  License terms GPL or BSD?
Previous Previous
 
Next Next
New Post 8/29/2005 11:02 AM
User is offline Michael Levy
119 posts
www.wildvoice.com?dnnbenefactor=true
9th Ranked


License terms GPL or BSD? 

I’m just wondering what the license terms will be for the blog module? I believe NewBlog is presently licensed as GPL. Will the blog module produced by this project continue to be GPL or will it be BSD style like the rest of DNN?

 

Can one take a GPL codebase an un-GPL it?


WildVoice.com Michael Levy - Are you ready to be heard? WildVoice.com
 
New Post 8/29/2005 11:39 AM
User is offline Scott Willhite
2178 posts
www.alkihomes.com
5th Ranked










Re: License terms GPL or BSD? 

Greetings Michael ~

The copyright holder is essentially the owner of the Intellectual Property (IP).  In this case, Hans-Peter was gracious enough to grant joint copyright status to DotNetNuke for his NewBlog module.  This is a condition of any and all DotNetNuke® Projects, so that they can maintain the same BSD license as the core framework.

Joint copyright means that Hans-Peter can do whatever he wants (now or in the future) with the original code under separate license.  But the IP that DotNetNuke took possession of at the time of contribution is now managed under the traditional DotNetNuke BSD license.

When we release under the DotNetNuke® Projects, program... the module will be fully BSD.

Cheers


Scott Willhite
DotNetNuke Corp.

It is only with the heart that one can see rightly... what is essential is invisible to the eye.
~ Antoine de Saint-Exupéry
 
New Post 10/28/2005 9:06 AM
User is offline Michael Levy
119 posts
www.wildvoice.com?dnnbenefactor=true
9th Ranked


Re: License terms GPL or BSD? 
Modified By Michael Levy  on 10/28/2005 11:13:38 AM)

Due to my previous job, I have a high level of paranoia regarding license terms. So, please forgive me for taking this question to a very deep level.

 

Is there a version of the NewBlog Module or is the DNN version of the module available in Source Code with a BSD License? Can I get a BSD licensed version today? or is the only source availble the GPL version?

 

 

 

I would like to use the NewBlog module and to make some customizations to it. However since it was released under the GPL license I believe that making any changes to this source  (even minor changes) and incorporating in my web site may legally bind me to make all of the source code to my site public under the GPL terms. (I know this is an extreme view of GPL, but I prefer to look at this carefully before I touch any GPL code).

 

Please see http://www.opensource.org/licenses/gpl-license.php

 

2. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

 

 

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

 

Since NewBlog is a DNN Module which is deployed as a library, why wasn’t it originally released under the L-GPL license (http://www.opensource.org/licenses/lgpl-license.php)? My understanding is that the L-GPL license has less restrictive terms and is meant to be used when a library component is to be released, but the L-GPL clearly defines that the rest of the system is not subject to the GPL license.

 

One last totally paranoid note: If the DotNetNuke core team has used the NewBlog Module and made modifications to it, and that is being used in DotNetNuke.com, does that imply that the GPL terms of NewBlog now supersede the BSD terms of DotNetNuke itself?

Now, I am not an Intellectual Property attorney and I am not an expert in this field, but has the DNN core team consulted an IP attorney about this? Is there any definitive guidance?

 

Thanks for your patience and any insights you have.

 


WildVoice.com Michael Levy - Are you ready to be heard? WildVoice.com
 
New Post 10/28/2005 9:44 AM
User is offline Hans-Peter Schelian
468 posts
www.schelian.com
8th Ranked


Re: License terms GPL or BSD? 
 michaelplevy wrote

Is there a version of the NewBlog Module or is the DNN version of the module available in Source Code with a BSD License? Can I get a BSD licensed version today? or is the only source available the GPL version?

NewBlog is still licensed under the GPL license, the new blog module which I have contributed is licensed under bsd license as all other DotNetNuke software (modules)

The new version is not yet available for download, it should be available soon.

 michaelplevy wrote
Since NewBlog is a DNN Module which is deployed as a library, why wasn’t it originally released under the L-GPL license (http://www.opensource.org/licenses/lgpl-license.php)? My understanding is that the L-GPL license has less restrictive terms and is meant to be used when a library component is to be released, but the L-GPL clearly defines that the rest of the system is not subject to the GPL license.

I found that the GPL license is a very good license for a community software.
I believe it is a good idea that everybody who take advantage of my module should publish his work on the module also to the community.

 michaelplevy wrote

One last totally paranoid note: If the DotNetNuke core team has used the NewBlog Module and made modifications to it, and that is being used in DotNetNuke.com, does that imply that the GPL terms of NewBlog now supersede the BSD terms of DotNetNuke itself?

The NewBlog module which was installed here in DotNetNuke.com is the original version which was available from my web site.
Nobody has done any changes on this version and have forgotten to publish the source with the changes.

Regards

HP


Best regards
Hans-Peter Schelian
www.schelian.com (English)
German DotNetNuke Community
 
New Post 10/28/2005 10:42 PM
User is offline Bradley Scott
39 posts
www.spherenet.co.nz
10th Ranked


Re: License terms GPL or BSD? 
Modified By Bradley Scott  on 10/30/2005 4:16:09 AM)
 michaelplevy wrote
One last totally paranoid note: If the DotNetNuke core team has used the NewBlog Module and made modifications to it, and that is being used in DotNetNuke.com, does that imply that the GPL terms of NewBlog now supersede the BSD terms of DotNetNuke itself?



Although I am not intimately familiar with the details of the agreements between DNN core and HP, here is my explanation of it-

A copyright gives rights to a developer when software is authored. This means that HP has copyrights in the NewBlog module.

The copyright owner can allow others to do things that would otherwise infringe his copyright. This includes the normal use we usually associate with software and modules, copying onto your computer, changing code, deploying to servers etc. This is done through releasing the work subject to a license. The license has terms that impose restrictions on what you can do to the work.

As I understand it, HP allowed the community to use his code under a GPL license. Granting certain rights and imposing restrictions.

What has happened now, under the DNN Subproject agreements, is that HP has assigned to DNN the status as copyright owner in the work which is now the Blog module. This means there are now 2 different copyright works out there, with 2 different copyright owners.

HP will still have copyrights over his Newblog module, and can still allow the community to use the module using the GPL, or any other license.

DNN now has copyrights in a SEPARATE work, which is the now Blog module. Although they retain some common code, they are now considered 2 separate copyright works. DNN now will release the code of the Blog module under a BSD license. Allowing people to use work, but on different terms to the GPL terms.

That's my overview of it all. I probably have got some of the facts wrong, but I hope that helps the understanding of how the copyrights and licensing in the Subprojects might be working.
 
Previous Previous
 
Next Next
  Forum  DotNetNuke® Pro...  Blog Module [Le...  License terms GPL or BSD?
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


BataviaSoft DotNetNuke Solutions
BataviaSoft offers custom DotNetNuke solutions especially for the European and the South East Asian market.
www.bataviasoft.com
Viva Portals, L.L.C.
Expert module development and graphic design.
www.continure.com
DNN Photo Gallery
DNN Photo Gallery is a truly unique photo management module released January 1st 2006. With DNN Photo Gallery you can REALLY integrate images into your existing portal and make them look like they were designed for your site.
DNN Photo Gallery

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP