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.
Within 48 hours of Cursor’s Composer 2 launch, a developer uncovered the hidden Kimi K2.5 model ID, sparking a public dispute over Modified MIT license compliance that ended in a public reconciliation and raised broader questions about open‑source AI attribution.
Microsoft’s latest Visual Studio update adds code citation for GitHub Copilot, letting developers see the public source, license details, and repository links for AI‑generated suggestions, thereby improving transparency and helping manage open‑source licensing risks.
The article recounts Stefano Marinelli’s EuroBSDcon 2024 talk about a ten‑year‑old FreeBSD server that runs flawlessly, explores BSD’s licensing advantages, contrasts its predictable stability with Linux’s frequent updates, and argues that such reliability makes BSD an attractive choice for long‑term server deployments.
The article analyzes Elasticsearch’s shift from Apache 2.0 to a dual ELv2 + SSPL/AGPL licensing model, explains the competitive pressure from AWS, and offers guidance on choosing appropriate open‑source licenses for different types of foundational software.
GitHub Copilot, the AI‑powered code completion tool launched by Microsoft and OpenAI, is now embroiled in a massive $9 billion class‑action lawsuit alleging unauthorized use of open‑source code, copyright violations, and breaches of licensing, DMCA, and privacy laws, sparking a broader debate over AI training ethics.
A Texas A&M professor alleges that GitHub Copilot frequently suggests copyrighted code without attribution, sparking debate over AI‑generated code licensing, open‑source license compliance, and the effectiveness of Copilot’s public code filter, while GitHub engineers defend the tool and call for scalable solutions.
GitHub’s decision to charge $10 per month for Copilot has triggered strong community opposition, with the Software Freedom Conservancy quitting GitHub, developers warning of potential copyright infringement, and widespread debate over the ethics of monetizing AI trained on open‑source code.
This article uses the 2021 Log4j vulnerability as a lens to explore the nature of open‑source software, its licensing, governance, security implications, and the benefits and responsibilities for individuals and enterprises participating in the open‑source world.
Elastic's recent client‑library changes restrict connections to AWS‑hosted OpenSearch and older Elasticsearch versions, prompting AWS to fork multiple official clients and sparking a heated debate over open‑source licensing and developer freedom.
The article examines GitHub Copilot’s AI‑driven code generation, its training on billions of GPL‑licensed lines from GitHub, the ensuing controversy over turning the tool into a paid product, and how this debate intersects with GPL principles and landmark legal cases such as Oracle v. Google.
The article explains Elastic's switch to SSPL/Elastic License for Elasticsearch and Kibana, Logz.io's criticism, AWS's fork under Apache 2.0, and the broader open‑source licensing battle between cloud providers and the original vendor.
The article explains open source’s core principles of openness, sharing, equality and collaboration, advises selecting projects with strong community and multi‑company backing, highlights China’s rapid growth in Apache projects, and encourages developers to contribute through code, documentation, translation and other community activities.
