
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sat, 16 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/osi/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-open-source-license-shifts-2026-bsl-wave-elastic-redis-hashicorp-sentry-valkey-opentofu-deep-dive.en</guid>
    <title>The 2026 Open Source License Shift — A Deep Dive on the BSL Wave: Elastic, Redis, HashiCorp, Sentry, Valkey, OpenTofu</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-open-source-license-shifts-2026-bsl-wave-elastic-redis-hashicorp-sentry-valkey-opentofu-deep-dive.en</link>
    <description>Since MongoDB moved to SSPL in 2018, Elastic in 2021, HashiCorp in 2023, and Redis in 2024 have all left Apache/MIT for non-OSI licenses like BSL, SSPL, and RSALv2. The result has been a stream of community forks (OpenSearch, Valkey, OpenTofu, OpenBao) and, in August 2024, Elastic returning to AGPL. This deep dive walks through seven years of the BSL wave, the OSI definition versus &quot;source-available&quot; debate, how much of the AWS strip-mining narrative is real, the Sustainable Use License and Fair Source movement, where Korean and Japanese companies stand, and a decision framework for migrating off a relicensed OSS — or relicensing your own.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>open-source</category><category>license</category><category>bsl</category><category>sspl</category><category>agpl</category><category>fsl</category><category>elv2</category><category>rsalv2</category><category>elastic</category><category>redis</category><category>hashicorp</category><category>mongodb</category><category>sentry</category><category>valkey</category><category>opentofu</category><category>fair-source</category><category>osi</category><category>2026</category><category>deep-dive</category><category>english</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-open-source-license-shifts-2026-bsl-wave-elastic-redis-hashicorp-sentry-valkey-opentofu-deep-dive.ja</guid>
    <title>オープンソースライセンス大転換 2026 — BSLの波: Elastic / Redis / HashiCorp / Sentry / Valkey / OpenTofu 徹底解説</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-open-source-license-shifts-2026-bsl-wave-elastic-redis-hashicorp-sentry-valkey-opentofu-deep-dive.ja</link>
    <description>2018年のMongoDBのSSPL移行を皮切りに、2021年Elastic、2023年HashiCorp、2024年RedisがApache/MITを離れ、BSL・SSPL・RSALv2 といった非-OSIライセンスへと移行した。その結果、OpenSearch・Valkey・OpenTofu・OpenBaoといったコミュニティフォークが次々と誕生し、2024年8月にはElasticがAGPLへと戻った。本記事ではBSLの波の7年史を整理し、OSI定義と「source-available」論争、AWS「strip-mining」言説の真偽、Sustainable Use License / Fair Source 運動、そして韓国・日本企業のスタンス、自社がライセンスを変える/マイグレーションする際の意思決定フレームを深く掘り下げる。</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>open-source</category><category>license</category><category>bsl</category><category>sspl</category><category>agpl</category><category>fsl</category><category>elv2</category><category>rsalv2</category><category>elastic</category><category>redis</category><category>hashicorp</category><category>mongodb</category><category>sentry</category><category>valkey</category><category>opentofu</category><category>fair-source</category><category>osi</category><category>2026</category><category>deep-dive</category><category>日本語</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-open-source-license-shifts-2026-bsl-wave-elastic-redis-hashicorp-sentry-valkey-opentofu-deep-dive</guid>
    <title>오픈소스 라이선스 대전환 2026 — BSL 물결: Elastic / Redis / HashiCorp / Sentry / Valkey / OpenTofu 심층 정리</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-open-source-license-shifts-2026-bsl-wave-elastic-redis-hashicorp-sentry-valkey-opentofu-deep-dive</link>
    <description>2018년 MongoDB의 SSPL 전환을 시작으로, 2021년 Elastic, 2023년 HashiCorp, 2024년 Redis가 차례로 Apache/MIT를 떠나 BSL·SSPL·RSALv2 같은 비-OSI 라이선스로 갔다. 그 결과 OpenSearch·Valkey·OpenTofu·OpenBao 같은 커뮤니티 포크가 줄지어 태어났고, 2024년 8월 Elastic은 AGPL로 돌아왔다. 이 글은 BSL 물결의 7년사를 정리하고, OSI 정의와 &quot;source-available&quot; 논쟁, AWS &quot;strip-mining&quot; 내러티브의 진위, Sustainable Use License / Fair Source 운동, 그리고 한국·일본 기업의 입장과 우리 회사가 라이선스를 바꾸거나 마이그레이션할 때 고려할 의사결정 프레임을 깊게 들여다본다.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>open-source</category><category>license</category><category>bsl</category><category>sspl</category><category>agpl</category><category>fsl</category><category>elv2</category><category>rsalv2</category><category>elastic</category><category>redis</category><category>hashicorp</category><category>mongodb</category><category>sentry</category><category>valkey</category><category>opentofu</category><category>fair-source</category><category>osi</category><category>2026</category><category>deep-dive</category>
  </item>

    </channel>
  </rss>
