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...Very Impressive DNN SiteVery Impressive DNN Site
Previous
 
Next
New Post
3/31/2007 11:13 AM
 

Brian,

I offered to integrate PageBlaster technology into the core when I was on the core team, but it was rejected because I have another commercial module with the same technology.

There isn't anything to stop it from happening if they want to do it though, as there is a PageBlaster.Net Open Source project with a BSD license on CodePlex.

It's also a free module with support on my site, so there is no real need to put it in the DotNetNuke core either.


DotNetNuke Modules from Snapsis.com
 
New Post
3/31/2007 12:38 PM
 
John Mitchell wrote

I offered to integrate PageBlaster technology into the core when I was on the core team, but it was rejected because I have another commercial module with the same technology.

For the sake of clarification only...

Any substantial (largely complete) code contribution to DotNetNuke must be accompanied by a "Software Grant".  Essentially, this provides for the ability to have dual copyright by both the original contributor & DotNetNuke.  This means that the contributor is protected because they can continue to do anything they like with the code without restriction (which includes commercial use).  However it also ensures that it can be included in DotNetNuke without "tarnishing" our BSD license, which protects all users of the DotNetNuke platform.

We do ask all of our Project Leads NOT to engage in commercial development (retail) of DNN applications that are like the project they are responsible for.  This is simply to avoid any appearance or possibility of conflict of interest which might arise from "holding back" on a project due to competition with their own offerings.  However, many of our Project Leads engage in commercial development (retail) of other modules and also enhancement of their projects for custom use, which generally winds up back in the Projects (and provides broad benefit).


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

 
New Post
3/31/2007 6:20 PM
 

I find it more common in the corporate world TO encourage the growth of the product you are responsible for.    I have seen numerous agreements where custom code was to remain under ownership of the company/creator but would roll into the core product code.

So..  if you encouraged the entire team to grow the product they are responsible for..   I think it would be better.

You have already stated a few times that 'stakeholders' (at times core team customers) custom work ends up as features in the core product.    I say why not encourage what you should be most familiar with, the product you team lead.   I just don't see the difference of retail development of other modules, selling books, etc yet restrict the development of the one module that the person should be expanding.

Just my .02..  probably .02 more than wanted.  :)    

 

 
New Post
3/31/2007 6:52 PM
 

Thanks for clearing that up Mr. Willhite. 

As a user of the platform, now I can sleep much better knowing that you are keeping people from "tarnishing" the DotNetNuke BSD license.

 


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Very Impressive DNN SiteVery Impressive 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