Search results
GPLv3 improved compatibility with several free software licenses such as the Apache License, version 2.0, and the GNU Affero General Public License, which GPLv2 could not be combined with. However, GPLv3 software could only be combined and share code with GPLv2 software if the GPLv2 license used had the optional "or later" clause and ...
- GNU Affero General Public License
GNU Affero General Public License. The GNU Affero General...
- GNU Affero General Public License
Informatica. Vrije software. De GNU General Public License of kortweg de GPL is een copyleftlicentie voor software, bedacht en uitgewerkt in 1985 door Richard M. Stallman van GNU, die (in het kort) stelt dat je met de software mag doen wat je wilt, inclusief aanpassen en verkopen, mits je dat recht ook doorgeeft aan anderen en de ...
- The Foundations of The GPL
- Neutralizing Laws That Prohibit Free Software—But Notforbidding DRM
- Protecting Your Right to Tinker
- Stronger Protectionagainst Patent Threats
- Clarifying License Compatibility
- New Compatible Licenses
- More Ways For Developersto Provide Source
- Less Sourceto Distribute: New System Libraries Exception
- A Global License
- When Therules Are Broken: A Smooth Path to Compliance
Nobody should be restricted by the software they use. There are fourfreedoms that every user should have: 1. the freedom to use the software for any purpose, 2. the freedom to change the software to suit your needs, 3. the freedom to share the software with your friends and neighbors, and 4. the freedom to share the changes you make. When a program...
You're probably familiar with the Digital Restrictions Management(DRM) onDVDs and other media. You're probably also familiar with the laws thatmake it illegal to write your own tools to bypass those restrictions, likethe Digital Millennium Copyright Act and the European Union CopyrightDirective. Nobody should be able to stop you from writing any co...
Tivoization is a dangerous attempt to curtail users' freedom: theright to modify your software will become meaningless if none of yourcomputers let you do it. GPLv3 stops tivoization by requiring thedistributor to provide you with whatever information or data isnecessary to install modified software on the device. This may be assimple as a set of i...
In the 17 years since GPLv2 was published, the software patent landscapehas changed considerably, and free software licenses have developed newstrategies to address them. GPLv3 reflects these changes too. Wheneversomeone conveys software covered by GPLv3 that they've written or modified,they must provide every recipient with any patent licenses nec...
If you found some code and wanted to incorporate it into a GPLed project,GPLv2 said that the license on the other code was not allowed to have anyrestrictions that were not already in GPLv2. As long as that was the case,we said the license was GPL-compatible. However, some licenses had requirements that weren't really restrictive,because they were ...
In addition to clarifying the rules about licenses that are alreadyGPL-compatible, GPLv3 is also newly compatible with a few other licenses.The Apache License 2.0 is a prime example. Lots of great free software isavailable under this license, with strong communities surrounding it. Wehope that this change in GPLv3 will foster more cooperation and s...
One of the fundamental requirements of the GPL is that when you distributeobject code to users, you must also provide them with a way to get thesource. GPLv2 gave you a few ways to do this, and GPLv3 keeps those intactwith some clarification. It also offers you new ways to provide sourcewhen you convey object code over a network. For instance, when...
Both versions of the GPL require you to provide all the source necessary tobuild the software, including supporting libraries, compilation scripts,and so on. They also draw the line at System Libraries: you're notrequired to provide the source for certain core components of the operatingsystem, such as the C library. GPLv3 has adjusted the definiti...
GPLv2 talks about “distribution” a lot—when youshare the program with someone else, you're distributing it. Thelicense never says what distribution is, because the term was borrowedfrom United States copyright law. We expected that judges would lookthere for the definition. However, we later found out that copyrightlaws in other countries use the s...
Under GPLv2, if you violated the license in any way, your rights wereautomatically and permanently lost. The only way to get them back was topetition the copyright holder. While a strong defense against violationsis valuable, this policy could cause a lot of headache when someoneaccidentally ran afoul of the rules. Asking all the copyright holders ...
A Quick Guide to GPLv3. Why Upgrade to GPLv3. Frequently Asked Questions about the GNU licenses. How to use GNU licenses for your own software. Translations of the GPL. The GPL in other formats: plain text , Texinfo , LaTeX , standalone HTML , ODF , Docbook v4 or v5 , reStructuredText , Markdown, and RTF . GPLv3 logos to use with your project.
GNU Lesser General Public License. The GNU Lesser General Public License ( LGPL) is a free-software license published by the Free Software Foundation (FSF). The license allows developers and companies to use and integrate a software component released under the LGPL into their own (even proprietary) software without being required by ...
29 apr. 2024 · By publishing the GNU Affero GPLv3 as a separate license, with provisions in it and GPLv3 to allow code under these licenses to link to each other, we accomplish all of our original goals while making it easier to determine which code has the source publication requirement.
