Showing messages 1 through 11 of 11.

• Java Applications
  2007-02-13 08:24:03 smbell [Reply | View]
  
  For an application I would most likely license under the GPL. However if there are reusable pieces I can pull out and jar up as libraries I would most likely license those under LGPL or an Apache license.
  
  I don't want somebody using my specific application code (assuming I've made the decision to open source it) in a proprietary product. I have less of a problem when it comes to reusable libraries with generic or general functionality.

• LGPL
  2007-02-11 21:03:09 sprhodes [Reply | View]
  
  The only Java code I've released as open source so far is, indeed, licensed under the LGPL. Although, I need to go back and add license headers to all the files, I don't think any of them actually have the header now... there's just a note on the webpage (at least I think there is) saying that it's all under the LGPL.

• none
  2007-02-10 22:40:42 jwenting [Reply | View]
  
  I'm unlikely to releast my source, but if it has to be it's most likely going to be an Apache style license.

  I don't want to be forced into a specific license for my products based on products I use, so why should I do that to others?

• LGPL or GPL with exceptions
  2007-02-10 03:40:05 bvansomeren [Reply | View]
  
  LGPL allows linking the code in without having to share your code (great for commercial use) while still ensuring that changes made to your code will be shared back.

• Public Domain
  2007-02-09 21:10:57 tompalmer [Reply | View]
  
  I'm probably crazy, but my favorite to use is none at all. It's worked for SQLite, SAX, and others.

• What about licenses you like to use in applications you USE?
  2007-02-09 12:16:38 jhannes [Reply | View]
  
  I think an interesting poll to compare this with is "which open-source license would you prefer for applications that you use?" If people understand the ramifications of GPL, it would be much less popular in that poll.

• LGPL
  2007-02-09 06:34:10 ctreber [Reply | View]
  
  I found that otherwise people often wouldn't/couldn't use my APIs in their own (commercial) projects.
  
  Chris
• LGPL
  2007-02-10 05:07:22 jwenting [Reply | View]
  
  if it must be OSS Apache most likely, but more likely I won't release the source to the general public (at least initially).
• LGPL
  2007-02-09 08:29:34 chrisadamson [Reply | View]
  
  You're totally right - I should have included LGPL. Since the poll's only been up for three hours, I've add LGPL. Feel free to change your vote if you're so inclined.
• LGPL
  2007-02-09 07:19:12 ahabra [Reply | View]
  
  yes. LGPL
  Why is it not listed among the options?
• LGPL
  2007-02-09 06:49:54 evickroy [Reply | View]
  
  Ditto.