Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] GPL and Open Source Licences
- Date: Fri, 31 Dec 2004 11:02:57 +0100
- From: Pietro Zuco <maillist@example.com>
- Subject: Re: [tlug] GPL and Open Source Licences
- References: <41D5147F.5070505@example.com>
- Organization: www.zuco.org
- User-agent: KMail/1.7.1
On Friday 31 December 2004 09:57, simon colston wrote: > If I link to some GPLed code I understand that I have to licence my code > under the GPL too. If I then distribute my program I understand that I > also have to distribute the source code as well. I think you don't have to distribute the source code too. For example, usually distributions, do not have the source code in the CD. If we think about the four kinds of freedom as explained in: http://www.gnu.org/philosophy/free-sw.html - The freedom to run the program, for any purpose (freedom 0). - The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this. - The freedom to redistribute copies so you can help your neighbor (freedom 2). - The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this. So, you can for example sell the program and sell the source code. It's logic, because provide the source code have a cost for you and maybe you can't affront it. But this don't mean that the source is secret! After, someone else, can sell the program again, or modify it. The source code have to be available in some way. For example you can sell the source code, but after I can copy it to my friends or sell it again. > Under the GPL, do I also have to distribute the source publicly too? > That is, do I have to make the code available to _anyone_ who asks for > it or can I restrict distribution of the source only to the people I > distribute the program to? You can have the policy you want. The idea is that you don't have any legal tool or law to restrict the source code. For example, you can made a program but you don't have money to put the source code in a web or you just want to sell the source. You decide. But after you sell it, someone else can copy and distribute it. So technically you don't have to distribute the code. You have to provide it in some way, by a cost, in a CD, a web page, or in a paper... The really important think is that the four kinds of freedom have to be respected. > Is this the same for all "Open Source" licences? For example, the > Apache Licence, Mozilla Licence or BSD licence. Any license have differences. You have to read them all use the one that match your needs and ideas. Personally I encourage you to use GPL ;-) but it depends on your situation. -Pietro- -- ------------------------------------------- - Pietro Zuco - Email: pietro@example.com - Web: http://www.zuco.org - Linux User Number: #252836 - Get counted! http://counter.li.org -------------------------------------------
- Follow-Ups:
- Re: [tlug] GPL and Open Source Licences
- From: simon colston
- References:
- [tlug] GPL and Open Source Licences
- From: simon colston
Home | Main Index | Thread Index
- Prev by Date: [tlug] GPL and Open Source Licences
- Next by Date: Re: [tlug] GPL and Open Source Licences
- Previous by thread: [tlug] GPL and Open Source Licences
- Next by thread: Re: [tlug] GPL and Open Source Licences
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links