chore: relicense from AGPL-3.0-or-later to MIT

.devin/wiki.json

@@ -17,7 +17,7 @@
       "author": "Marko Vejnovic"
     },
     {
-      "content": "Canonical operator documentation lives in docs/cookbook/ (especially install.md for host provisioning: KVM, device-mapper thin pools, the setuid helper) and is published to https://hexdocs.pm/hypervm/. Prefer citing those guides for installation and configuration rather than inferring procedures from code. The package is published on Hex as `hypervm`. License is AGPL-3.0-or-later.",
+      "content": "Canonical operator documentation lives in docs/cookbook/ (especially install.md for host provisioning: KVM, device-mapper thin pools, the setuid helper) and is published to https://hexdocs.pm/hypervm/. Prefer citing those guides for installation and configuration rather than inferring procedures from code. The package is published on Hex as `hypervm`. License is MIT.",
       "author": "Marko Vejnovic"
     }
   ]

CONTRIBUTING.md

@@ -6,45 +6,16 @@ bar and a few non-obvious requirements.
 
 ## Before you start
 
-By submitting a contribution (a pull request, patch, or commit) you agree to
-the [Contributor License Agreement](CLA.md). In short: **you assign copyright
-in your contribution to the project owner**, who keeps the copyright
-consolidated so Hyper can be relicensed or dual-licensed in the future. You
-retain a perpetual license to your own work. If you are contributing on company
-time, make sure you have permission to do so. If you do not agree with the CLA,
-please do not submit a contribution.
+Hyper is licensed under the MIT License. By submitting a contribution (a pull
+request, patch, or commit) you agree that it is licensed to the project under
+those same terms; you retain the copyright to your own work. There is no
+separate contributor license agreement to sign. If you are contributing on
+company time, make sure you have permission to do so.
 
 For anything beyond a small fix, **open an issue first** and describe what you
 intend to do. Hyper is opinionated and moves fast; a quick discussion avoids
 wasted work on a PR that does not fit the direction of the project.
 
-### Why a CLA?
-
-Hyper is released under the AGPL, but it is also the commercial backbone of
-[harmont.dev](https://harmont.dev). The CLA exists to keep those two facts
-compatible.
-
-Under the AGPL, every contributor owns the copyright to their own patches. That
-sounds nice, but it means the license can never be changed without tracking down
-and getting agreement from every person who ever contributed -- the same reason
-Linux can never move off GPLv2. Consolidating copyright under a single owner
-avoids that trap and lets Hyper:
-
-- **Relicense in the future** if the AGPL stops serving the project.
-- **Offer commercial licenses** to organizations that cannot use AGPL code,
-  which is how development gets funded. You can only sell what you wholly own.
-- **Enforce the license** against infringers without coordinating dozens of
-  copyright holders.
-
-Yes, this is asymmetric: the owner reserves the right to license Hyper
-proprietarily, which the AGPL denies everyone else. That is the deal open-core
-projects make, and we would rather state it plainly than bury it. In exchange,
-the CLA grants you a perpetual license to keep using your own contributions for
-any purpose (CLA §3) -- you never lose the right to the work you authored.
-
-If assigning copyright is not something you are willing to do, that is a
-completely reasonable position -- but please do not submit a contribution.
-
 ## What we are looking for
 
 - **Bug fixes** with a clear reproduction.