• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

How do I choose the appropriate license for my application?

 
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Everyone,

I have written a number of utilities in Java... some of them are only useful to my team at work, while others could be useful to anyone. Each tool uses some open source components (just uses, no modification). Each component might be distributed under a different license (GPL, LGPL, APL, Artistic etc.). What I am trying to understand is if there is any way I can be sure that I finally choose a correct license for my own application - Open Source or Proprietery.

Where can I find some write-up on how to license software that I write?

Many thanks,
Abhik.
 
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm going to move this to the "General Computing" forum, as it's not Java-specific.
 
Ranch Hand
Posts: 5093
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Unless you used GPL components in your programs (in which case you may better consider removing those), avoid GPL like the plague!

It's extremely restrictive, forcing you to release your programs (or anything that uses them) as open source under the GPL.

Personally, I'd consider an APL or IPL style license under which you keep total freedome while allowing others to create derived works if they so wish.
That is, I'd consider such a license if I were to release the code at all, which is not at all certain.

If you created the tools in company time, ask your company as they more likely than not own the code!
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic