Open sourcing something

1. #  Prasenjeet 10:21 AM
   Depends on the motive behind Open-sourcing. If the intention is to prevent private commerical forks, LGPL may be better. BSD is better for code where you don't care who does what with it - e.g., TCP/IP's BSD license probably reduced fragmentation because OSS and commercial versions of TCP/IP shared a common ancestry.
   
   And if the intention is to allow your own code to be used in the OSS community while still maintaining a revenue stream, dual-licensing under GPL and proprietary licenses is probably best, the way Trolltech does with Qt.
2. #  Rob 10:52 AM
   Prasenjeet,
   
   First off, thanks for the feedback.
   
   I want one license that allows GPL guys to use it and commercial apps to use it. It's my understanding the BSD license will cover both? If not I may have to find another one. The only real requirement will be proper attribution in your application.
   
   Hopefully this doesn't turn into a mess. I may have to make my own, which I really do not want to do.
3. #  Daniel Jalkut 12:47 PM
   Rob, BSD would be a good choice for you. It requires attribution and may be used in GPL or closed-source projects.
   
   The term for "can be used in a GPL project" is "GPL compatible".
   
   BSD and MIT are for all intents and purposes the same, so use which ever one you like the name of better ;)
   
   Daniel
4. #  Rob 9:37 AM
   Daniel,
   
   Thanks, I was hoping you'd drop by. There are so many license choices, I wanted to get the right one.

Powered by Blogger and the Hemingway template for Blogger. Copyright © 2001-2009 Rob Fahrni