Add LICENCE, NOTICE, and README.md reflecting the new licence terms and conditions

LICENSE

@@ -0,0 +1,21 @@
+Copyright Venue (Wayne Booth Marci, Estate of John Sybalsky) and Interlisp contributers.
+
+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, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+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.
+

NOTICE

@@ -0,0 +1,5 @@
+Many thanks to Wayne Booth Marci, who inherited the rights of Venue,
+including the copyright of works identified as Copyright Venue.
+
+Permission to release these files with the open source MIT License
+has been granted.

README.md

@@ -0,0 +1,17 @@
+# Maiko
+
+This is the emulator for the Interlisp-D virtual machine, for a
+byte-coded Lisp instruction set and some low-level functions for
+connecting witih Lisp for access to display and disk etc.
+
+There’s a complex system of make files that include all the flags and
+variables you have to set for each hardware/OS target.
+
+You need to be in the "bin" directory, you need to have "." on your
+path, you need to do "./makeright x" in order for it to detect the
+correct OS and then put together the makefile parts that it needs.  It
+will build it in ../<osname>.<cputype>-x (for the .o files) and
+../<osname>.<cputype> for the executables.
+
+
+