<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>License on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/license/</link><description>Recent content in License on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Tue, 14 Jul 2026 09:00:00 +0800</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/license/rss.xml" rel="self" type="application/rss+xml"/><item><title>Mainstream Open Source Licenses: From MIT to AGPL, How Engineers Choose</title><link>https://blog.mickeyzzc.tech/en/posts/architecture/open-source-license-guide/</link><pubDate>Tue, 14 Jul 2026 09:00:00 +0800</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/architecture/open-source-license-guide/</guid><description>&lt;p&gt;In September 2017, React switched overnight from BSD+Patents to MIT. The reason: the Apache Software Foundation put React&amp;rsquo;s license on its &amp;ldquo;do not depend on&amp;rdquo; list, and Automattic (WordPress&amp;rsquo;s parent) immediately announced it would stop rewriting its UI on React. Facebook couldn&amp;rsquo;t withstand the ecosystem pressure and folded. Seven years later, in March 2024, Redis moved its core from BSD 3-Clause to a dual RSALv2+SSPL license — within a week AWS, Google, and Oracle jointly forked Valkey to replace it.&lt;/p&gt;</description></item></channel></rss>