Linux Today: Linux News On Internet Time.
Search Linux Today
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Server Daily
IT Management Daily
Subscribe News
Subscribe PR
Subscribe Security

internet.com
Internet News
Small Business

Advertise
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

RebeccaBlackOS - First Live CD Running Wayland Display Server

The Linux powered LAN Gaming House

5 Best Android Apps For Reddit Lovers

SECURITY: Flash Player Sandbox Comes to Firefox

The Future of Kubuntu

SECURITY: Symantec should not be afraid of 'open' source code

Linux 3.3 rc3

60 Fantastic Free Android Apps

Ready for Another Linux Tablet? Meet the Rugged Trimble Yuma

How can the layman get involved with free software?



Applications Management Engineer Sr (NYC)
Next Step Systems
US-NY-New York

Justtechjobs.com Post A Job | Post A Resume
:Licensing 101 for Open Source Projects: Choosing an Open Source License
Licensing 101 for Open Source Projects: Choosing an Open Source License
Jul 9, 2009, 22 :03 UTC (0 Talkback[s]) (4012 reads)

(Other stories by Ossi Niiranen)

"How the License Type Affects Your Project

"1. Strong copyleft
Choosing a strong copyleft licensee (e.g., GPL) ensures that the source code of all modifications, additions, or derivatives of your work will be disclosed (eventually). In case of the GPL, derivatives are likely to include also other components licensees link your program to and distribute your program with.

"If your project uses a strong copyleft license, most enterprises relying on licensing revenue for their business are unlikely to use your software as their own software linking to your code could be subject to GPL obligations. In fact, many companies have prohibited the use of GPL interally for this very reason. Your code is more likely to be used by companies requiring the software for internal use, or companies that do not rely on license fees for their business but instead make their money out for example the provision of IT services."

Complete Story

Related Stories:
New CAOS report on open source licenses, uses(Jul 07, 2009)
Amazon code release irrelevant, Kindle is still closed(Jun 19, 2009)
Special Episode: Amicus Brief in Jacobsen v. Katzer(Jun 18, 2009)
FOSS and the Labyrinthine Land of Licensing(May 31, 2009)
Finding the right open-source savvy lawyer(May 23, 2009)
How To Turn Customers Into Pirates(Mar 03, 2009)
Joe 'Zonker" Brockmeier Fights FOSS LIcense FUD(Mar 02, 2009)
Bruce Perens: How Many Open Source Licenses Do You Need?(Feb 17, 2009)



No talkbacks posted.
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!

..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP