Appendix G GNU General Public License

Why This Matters

The GNU General Public License (GPL) is a fundamental component of open-source software development, particularly in C programming. It guarantees users' freedom to share, modify, and distribute software while preserving the rights of the original authors. By understanding GPL, you can navigate the world of open-source projects effectively, avoid legal issues, and contribute meaningfully to the community.

Prerequisites

To fully grasp the concepts discussed in this lesson, it's essential to have a basic understanding of:

1. Open-source software and its importance in the programming world
2. The concept of copyright and how it applies to software
3. Basic knowledge about C programming syntax and common practices
4. Familiarity with the structure and components of open-source licenses, particularly the GPL

Core Concept

The GNU General Public License (GPL) is a free, copyleft license for software and other works. It ensures that users have the freedom to share, modify, and distribute software while preserving the rights of the original authors. Here's a breakdown of the key components:

1. Freedom 0 (Free Distribution): Users can copy, distribute, and/or modify the program in any way they see fit, as long as they provide the source code along with the compiled binary. This freedom ensures that the software remains accessible to all users and encourages collaboration.
2. Freedom 1 (Right to Run): Users have the right to run the program for any purpose, including commercial use, without facing restrictions or additional fees.
3. Freedom 2 (Right to Study and Change): Users can access the source code of the program, understand it, modify it, and combine it with other software. This freedom allows users to learn from existing codebases, improve upon them, and create new projects based on their modifications.
4. Freedom 3 (Right to Distribute Copies): If users distribute copies of the program, they must provide the source code so that others can exercise their freedoms as well. This freedom ensures that the software remains open-source and encourages collaboration among developers.
5. Freedom 4 (Integrity of the Author's Source Code): Users cannot remove or alter any notices that are intended to ensure the free distribution and retainment of the GPL license. This freedom preserves the integrity of the original authors' work and ensures that users understand the terms under which they can use the software.

Worked Example

Let's consider a simple C program licensed under GPL:

#include <stdio.h>

void greet(char *name) {
printf("Hello, %s!\n", name);
}

int main() {
greet("World");
return 0;
}

If you wish to modify this program and distribute your changes, you must:

1. Include the GPL license in any copies of the source code or compiled binaries you distribute. You can find a copy of the GPL license at .
2. Provide the modified source code if someone requests it, along with a clear explanation of your modifications. This transparency allows other developers to understand how your changes affect the software and encourages collaboration.
3. Clearly indicate that your modifications have been made by adding a notice or comment in the source code. This helps others identify your contributions and gives credit where it's due.

Common Mistakes

1. Failing to include the GPL license

If you don't include the GPL license with your software, users may not know they are allowed to share, modify, or distribute it. This oversight can lead to confusion and potential legal issues.

2. Not providing source code for compiled binaries

Under the GPL, if you distribute a compiled binary, you must also provide the corresponding source code. Failing to do so can result in your software being considered non-compliant with the GPL.

3. Not indicating modifications

If you make changes to a GPL-licensed program and don't clearly indicate your modifications, it may be difficult for others to understand how your changes affect the software. This lack of transparency can hinder collaboration and potentially lead to conflicts.

4. Adding proprietary code without proper attribution

If you add proprietary (non-open-source) code to a GPL-licensed program, you must ensure that the proprietary code is clearly separated from the open-source code and properly attributed. Failing to do so can result in your software being considered non-compliant with the GPL.

Practice Questions

1. What are the four freedoms guaranteed by the GNU General Public License?
2. If you find a bug in a GPL-licensed C program, and you fix it, what must you do before distributing your fixed version?
3. Can you distribute a proprietary (non-open-source) program that uses a function from a GPL-licensed library without violating the GPL?
4. If you create a new program that combines multiple open-source projects licensed under different licenses, what steps must you take to ensure compliance with all of those licenses?
5. If you distribute a modified version of a GPL-licensed program and someone else makes additional modifications, do they need to provide their changes back to you or the original author?
6. Can you use a function from a GPL-licensed library in a closed-source (proprietary) project without violating the GPL?
7. If you distribute a GPL-licensed program with additional non-GPL licensed software, what steps must you take to ensure compliance with both licenses?

FAQ

1. What happens if someone violates the terms of the GNU General Public License?

If someone violates the terms of the GPL, they may face legal consequences, as the license is enforceable by law. The Software Freedom Law Center (SFLC) provides legal assistance to open-source projects and can help enforce the GPL when necessary.

2. Can I use a GPL-licensed program in a commercial project?

Yes, you can use a GPL-licensed program in a commercial project, as long as you comply with the terms of the GPL (providing source code, attributing modifications, etc.). However, if you distribute your commercial project, it must also be licensed under the GPL.

3. If I create a new program that uses functions from multiple GPL-licensed libraries, do I need to include each library's license?

Yes, if your program uses functions from multiple GPL-licensed libraries, you must include the licenses for all of those libraries in your distributed copies of the source code. This ensures compliance with all relevant open-source licenses and encourages collaboration among developers.

4. If I distribute a modified version of a GPL-licensed program and someone else makes additional modifications, do they need to provide their changes back to me or the original author?

No, under the terms of the GPL, users are not required to provide their modifications back to the original author or you. However, it's good practice to encourage collaboration and transparency by asking for contributions and providing a mechanism for others to contribute back to the project.

5. Can I use a function from a GPL-licensed library in a closed-source (proprietary) project without violating the GPL?

No, using a function from a GPL-licensed library in a closed-source project without providing the source code for that function would violate the terms of the GPL. If you wish to use a GPL-licensed library in a proprietary project, you should consider using a compatible license or negotiating with the original authors to obtain a separate license that allows for proprietary use.

6. If I distribute a GPL-licensed program with additional non-GPL licensed software, what steps must I take to ensure compliance with both licenses?

When distributing software that includes both GPL-licensed and non-GPL licensed components, you should provide separate copies of the source code for each component, along with clear instructions on how to combine them. This ensures that users can comply with the terms of both licenses and encourages collaboration among developers.