The php.internals vote on April 4 approved moving PHP 9.0 to the permissive 3‑clause BSD license, replacing the dual PHP v3.01 and Zend Engine licenses, and the article explains the historical reasons, legal benefits, comparisons with other BSD variants, PostgreSQL’s approach, and broader open‑source licensing trends.
The article explains that China’s large‑scale migration from Windows to Linux in state‑owned and central enterprises is driven by security independence, massive licensing cost savings, ecosystem development, and strategic preparation for potential sanctions, offering both challenges and new opportunities for the tech workforce.
China’s push to replace Windows PCs in state‑owned enterprises with Linux is driven by security concerns after the Huawei sanctions, massive software licensing costs, the need to build a domestic ecosystem, and the strategic goal of achieving autonomous, controllable IT infrastructure.
The recent AI‑driven rewrite of the Python encoding detector chardet sparked a heated debate over licensing, clean‑room development, and whether a completely new implementation can legitimately switch from LGPL to MIT, highlighting the broader challenges of AI‑generated open‑source software.
The article explains how Microsoft deliberately allows widespread Windows piracy to maintain market dominance, detailing the role of KMS activation, the recent KMS38 deprecation in Windows 11, and why this “soft‑kill, hard‑gain” approach benefits the company in the long run.
This proposal argues for replacing the PHP License 3.01 with the permissive MIT license to eliminate compatibility hurdles, reduce legal uncertainty for businesses, and align the PHP ecosystem with mainstream open‑source projects, while outlining the scope, specific changes, community concerns, and long‑term impact.
The article explains why some companies prohibit IntelliJ IDEA, citing copyright risks, security vulnerabilities, efficiency losses from activation prompts, collaboration challenges, and the high cost of commercial licenses, while emphasizing the need to follow unified tool policies.
The article examines CPython issue gh‑126133 where Hugo van Kemenade proposed simplifying the project's copyright notice by keeping only the first publication year, discusses legal feedback from the PSF, compares practices of major open‑source projects, and concludes with the accepted change merged into the main branch.
The brief, turbulent open‑source episode of Winamp—its source code upload, swift removal, restrictive Winamp Collaboration License, community backlash, and subsequent license tweaks—offers a cautionary look at how legacy software, mixed‑code bundles, and licensing choices affect true open‑source viability.
Switzerland’s new EMBAG law forces all public sector agencies to release the source code of software they develop or commission, barring third‑party copyright or security concerns, marking a bold shift toward open‑source, digital sovereignty and greater transparency that could inspire similar moves worldwide.
A recent Azul survey of 663 Java professionals shows that 86% of Oracle Java users are migrating to OpenJDK due to high costs, licensing uncertainty, audit risks, and a preference for open‑source alternatives, with most migrations completing within a year and delivering significant cost savings.
This comprehensive guide explains what open source is, distinguishes permissive and copyleft licenses, details common licenses such as MIT, Apache‑2.0, GPL, LGPL, AGPL, and MPL, shows how to apply a license in a project, and highlights a Chinese GPL infringement case.
The article explains why many companies prohibit IntelliJ IDEA, covering legal copyright risks, security concerns, efficiency losses, collaboration challenges, and the high cost of commercial licenses, and advises developers to follow company‑mandated tools while understanding the financial and legal implications.
Oracle’s newly released Java SE Universal Subscription price list introduces tiered per‑employee fees that can dramatically increase costs for companies with large staff but few Java users, while offering unchanged terms for existing subscribers and no impact for OpenJDK users.
This article explains why Zabbix, an open‑source monitoring platform released under GPLv2, remains freely usable worldwide—including China—by detailing its licensing, public‑domain status under EU export rules, global availability, and extensibility, assuring users of its legal compliance and autonomy.
The article examines the rise of GitHub Copilot as an AI‑powered coding assistant, outlines the collective lawsuit filed against Microsoft, GitHub, and OpenAI over alleged copyright violations, and discusses the broader legal and ethical implications for open‑source licensing and AI development.
A viral screenshot reveals a paid version of Microsoft’s free VS Code editor that uses deceptive pricing, a fake Google link, and questionable licensing, prompting an analysis of whether repackaging the official executable violates the MIT license and copyright.
This article examines the relationship between open‑source licenses and patents through a real case of a GPL‑2.0 project, explains legal distinctions between copyright and patent rights, and offers practical guidance for developers on protecting their work and handling potential patent conflicts.
The article examines three recent incidents where Microsoft allegedly appropriated community‑maintained open‑source projects without proper attribution, explains the legal framework of open‑source licenses, and offers guidance for developers on protecting their rights and respecting licensing obligations.
The article outlines three software licensing models—company‑wide purchase, individual purchase with reimbursement, and individual purchase without reimbursement—examining their pros, cons, and compliance implications, and advises firms to match each approach to budget, usage context, and ownership considerations.
The Chinese smartphone maker UMIDIGI sparked international controversy by refusing to release Android kernel source code under GPLv2, demanding developers collect it in person, a move that exposed broader compliance issues and ignited heated discussion across Reddit and Twitter.
This article introduces several widely used open source licenses—including BSD, Apache License 2.0, GPL, LGPL, MIT, MPL, and EPL—explaining their main permissions, obligations, and suitability for commercial software development.
An independent developer's X browser used an open‑source ad‑blocking rule that blocked Youku pre‑roll ads, prompting a 1 million‑yuan lawsuit and highlighting the legal risks of using third‑party plugins without professional counsel, proper disclosure, or proactive settlement efforts.
The article explains that GitHub’s user agreement and the Apache Software Foundation’s policies include U.S. export‑control clauses, but legal experts clarify that publicly available open‑source code without encryption is generally exempt from EAR restrictions, while enterprises may still need licenses for certain uses.
This article explains why selling free software is perfectly legitimate, clarifies common misconceptions about price and freedom, outlines the GNU GPL’s stance on charging for distribution, and shows how revenue from open‑source sales can sustainably support the community.
The article examines the dispute between Microsoft and open‑source developer Keivan Beigi over alleged plagiarism of the AppGet Windows package manager in Microsoft's WinGet, discusses similar accusations involving Lerna and Rush, and highlights legal implications of violating open‑source licenses.
This article explores how the rapid growth of information technology has reshaped the economy, using open source software as a prime example to examine its definition, historical milestones, licensing models, and the unique collaborative mechanisms that enable millions of volunteers worldwide to create high‑quality, publicly shared software.
The Beijing High People’s Court’s landmark 2019 ruling in Digital Heaven v. Yuzu, China’s first GPL‑related lawsuit, rejected Yuzu’s claim that three HBuilder plugins were GPL‑bound derivatives, ordered RMB 710,000 damages, and highlighted both growing judicial recognition of the GPL and the need for companies to isolate, analyze, and manage open‑source components to avoid copyleft liability.
A recent Tidelift and The New Stack survey reveals that 86% of developers consider an acceptable open‑source license the most critical factor when choosing a project, outweighing code quality, security, and documentation, while also highlighting trends in license popularity and emerging new licenses.
The article examines Google's suspension of Huawei support, explains why Android uses the Apache License instead of GPL, outlines common open‑source licenses, discusses licensing implications for Node.js and mobile ecosystems, and highlights recent licensing controversies affecting developers.
From Confluent’s move to a Community License to InfluxData’s blend of MIT and commercial terms, the article examines how major open‑source projects are altering licenses to protect revenue against cloud providers, analyzes the resulting community backlash, and argues that a balanced hybrid model is the most sustainable path.
The article argues that, despite common advocacy for open‑source, closed‑source solutions can sometimes be preferable because they relieve users from bug‑fixing, licensing complexities, overwhelming choices, and the need to hunt for documentation or support, relying instead on vendor assistance.
