Skip to content
TheChatArchiveThe Chat Archive
gpt-4o-2024-11-20· OpenAIAi2 WildChat-4.8M (AI2)

hey

  1. User

    hey

  2. Assistant

    Hey! How can I help you today? 😊

  3. User

    u there?

  4. Assistant

    I'm right here! 😊 What's on your mind?

  5. User

    give me examples of illegal forks of some copyleft license based open source projects

  6. Assistant

    The concept of "illegal forks" in open-source projects generally arises when individuals or organizations violate the terms of the open-source license under which the project is distributed. Open-source licenses—particularly those with copyleft provisions (like the GNU General Public License, or GPL)—usually place clear obligations on how the code can be used, modified, and redistributed. When these obligations are ignored, it can lead to license violations. Let me explain further and highlight a few real-world examples of what "illegal forks" might look like (though keep in mind that violation cases are often resolved, and my focus is on illustrative examples).


    Context: Copyleft Licenses

    Copyleft licenses like the GPL require that:

    1. Modified versions of the software must be distributed under the same license.
    2. The downstream recipient must also be granted the same freedoms as the original (e.g., access to the source code, the right to modify or redistribute it, etc.).
    3. Any redistribution (and sometimes usage, in some cases) of the software must comply with obligations outlined in the license (e.g., inclusion of a copy of the license, copyright notices, etc.).

    When these requirements aren't followed, the fork becomes a license violation ("illegal").


    Examples of License Violations / Illegal Forks

    1. Linksys (WRT54G Routers)

    • What Happened: Linksys (owned by Cisco at the time) used GNU GPL-licensed code in the firmware of their popular WRT54G series routers but failed to release the modified source code, as required by the GPL.
    • Violation: By failing to provide access to the source code, Linksys violated the copyleft requirements of the GPL.
    • Resolution: The Free Software Foundation and open-source advocates pressured the company, and eventually, Linksys complied by releasing the source code.

    2. VMware and BusyBox

    • What Happened: VMware allegedly incorporated BusyBox, a GPL-licensed utility, as part of its ESXi hypervisor but did not release the corresponding source code or provide the required license materials.
    • Violation: VMware's redistribution of the modified software without fulfilling GPL obligations constituted a license violation.
    • Resolution: The case went to court, with the Software Freedom Conservancy (SFC) filing a lawsuit against VMware. The case later settled, but it drew significant attention to compliance with the GPL in commercial software.

    3. Grsecurity Kernel Patches

    • What Happened: Grsecurity is a set of security patches for the Linux kernel, distributed under the GPL. However, they allegedly attempted to enforce legal agreements that discourage redistribution of their patches by downstream users (a "no-redistribution" policy for patches).
    • Violation: While not a traditional "fork," Grsecurity's actions were seen as violating the core spirit and obligations of the GNU GPL by trying to restrict redistribution. This raised concerns among open-source advocates that their practices were incompatible with copyleft principles.
    • Resolution: To date, this controversy remains unresolved, and the Free Software Foundation (FSF) has criticized Grsecurity's approach.

    4. Artifex vs. Hancom (Ghostscript Case)

    • What Happened: Hancom, a Korean software company, was accused of violating the GPL for Ghostscript, an open-source software suite for processing PDFs. Hancom allegedly embedded Ghostscript in their proprietary software without adhering to GPL requirements (e.g., releasing the source code).
    • Violation: The proprietary use of Ghostscript without meeting the license's requirements (e.g., sharing changes under the same license) violated the copyleft provisions.
    • Resolution: Artifex, the commercial maintainer of Ghostscript, filed a lawsuit in the U.S., leading to a settlement.

    5. Skirting Android GPL Rules

    • What Happened: Some Android device manufacturers have been accused of violating open-source licenses (primarily the GPL and LGPL) by failing to release the source code for the Linux kernel modifications made to their devices. Examples involve numerous smaller companies shipping Android phones with modified kernels but not providing source code.
    • Violation: Failing to release modifications to the Linux kernel under the GPL directly violates the copyleft clauses.
    • Resolution: Advocacy groups like the Software Freedom Conservancy often intervene to enforce compliance.

    Key Takeaways

    The term "illegal fork" stems from license violations, usually due to failing to comply with redistributive obligations of the GPL (or other copyleft licenses). Open-source license enforcement organizations like the Free Software Foundation (FSF) and Software Freedom Conservancy (SFC) often work to ensure compliance and protect open-source licenses.

    Would you like to dive deeper into any of these examples, or explore how compliance works in open-source licensing? 😊

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.