README.md: Add license info and MIT-0 license

Just to clarify things for other packagers.

Signed-off-by: Hector Martin <marcan@marcan.st>

MIT-0

@@ -0,0 +1,7 @@
+MIT No Attribution
+
+Copyright The Asahi Linux Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

README.md

@@ -1,6 +1,21 @@
 # AsahiLinux-PKGBUILD
 
-This repository holds PKGBUILD files for the AsahiLinux Arch Linux Arm
-distribution. This will hold packages which are required to run Arch
-Linux Arm on Apple Silicon based computers, starting with patched Linux
-Kernel builds with hardware support.
+This repository holds PKGBUILD files for the Asahi Linux Arch Linux ARM
+derivative distribution. This will hold packages which are required to
+run Arch Linux ARM on Apple Silicon based computers, starting with
+patched Linux Kernel builds with hardware support.
+
+# License
+
+The PKGBUILDs and associated config files / metadata that were created
+for the Asahi Linux project, to the extent to which they may be eligible
+for copyright protection at all, are licensed as MIT-0. This includes
+all packages *beginning* with `asahi`, and also `m1n1`. Feel free to use
+them as reference or directly incorporate their contents into packaging
+for other distributions without any attribution requirements.
+
+The remaining PKGBUILDs are derivative works of Arch Linux ARM or upstream
+Arch Linux PKGBUILDs and subject to their respective upstream licenses.
+
+Patch files inherit the license of the upstream project that is being
+patched.