diff --git a/INSTALL b/INSTALL
new file mode 100644
index 00000000..42b9f3d0
--- /dev/null
+++ b/INSTALL
@@ -0,0 +1,49 @@
+===================================================
+
+Requirements (tools, headers and libraries):
+
+ * You need gcc for C and C++ (4.2.2 should work)
+ * You need dbus (1.2.16 should work)
+ * You need libuuid from e2fsprogs (1.40.2 should work)
+ * You need the expat XML parser (2.0.1 should work)
+ * You need glib (2.20.3 should work)
+ * You need dbus-glib (0.74 should work)
+ * You need gtk+ (2.12.1 should work)
+ * You need libglade (2.6.2 should work)
+ * You need flowcanvas (svn revision 2186 or later should work, included in tarball)
+ * Python (for ladish_control and LADI Tools)
+
+===================================================
+
+The tarball contains sources for suitable flowcanvas library and
+sources of suitable LADI Tools. Check the docs in corresponding
+flowcanvas/ and laditools/ subdirectories.
+
+===================================================
+
+= Configure it =
+
+./waf configure
+
+This will configure for installation to /usr/local prefix.
+If you want to use other prefix, use --prefix option:
+
+./waf configure --prefix=/usr
+
+For full list of options, run:
+
+./waf configure --help
+
+= Build it =
+
+./waf
+
+You can use -j option to enable building on more than one CPU:
+
+./waf -j 4
+
+= Install it =
+
+./waf install
+
+You probably want to run later as superuser to install system-wide
diff --git a/NEWS b/NEWS
new file mode 100644
index 00000000..fe362cfe
--- /dev/null
+++ b/NEWS
@@ -0,0 +1,3 @@
+= Version 0.1 "preview 1" on 2009-09-01 =
+ * JACK multiconfig (Save/restore jack settings by saving and then
+   loading and activating studios)
diff --git a/README b/README
new file mode 100644
index 00000000..ea73297f
--- /dev/null
+++ b/README
@@ -0,0 +1,54 @@
+========================
+  LADI Session Handler 
+========================
+
+http://ladish.org/
+
+LADI Session Handler or simply ladish is a session management system
+for JACK applications on GNU/Linux. Its aim is to allow you to have
+many different audio programs running at once, to save their setup,
+close them down and then easily reload the setup at some other
+time. ladish doesn't deal with any kind of audio or MIDI data itself;
+it just runs programs, deals with saving/loading (arbitrary) data and
+connects JACK ports together. It can also be used to move entire
+sessions between computers, or post sessions on the Internet for
+download.
+
+ladish has GUI frontend, gladish, based on lpatchage (LADI Patchage)
+and the ladish_control command line app for headless operation. LADI
+Tools is set of apps that interface with ladish, JACK server and
+a2jmidid
+
+ladish requires D-Bus and JACK compiled with D-Bus support.
+
+LADI Session Handler is rewrite of LASH.
+
+Project goals:
+ * Save and restore sets of JACK (audio and MIDI) enabled
+   applications.
+ * Provide JACK clients with virtual hardware ports, so projects can
+   be transfered (or backups restored) between computers running
+   different hardware and backups. 
+ * Don't require session handling library to be used. There is no need
+   of such library for restoring connections between JACK clients.
+ * Flow canvas based GUI. Positions of elements on the canvas are
+   saved/restored.
+ * Allow clients to use external storage to save its state. This
+   includes storing internal state to non-filesystem place like memory
+   of a hardware synth. This also includes storing client internal
+   state (client project data) in a way that is not directly bound to
+   ladish project. 
+ * Import/export operations, as opposed to save/load. Save/load
+   operate in current system and may cause saving data outside of
+   project itself (external storage). Import/export uses/produces
+   "tarball" suitable for transferring session data over network to
+   other computer or storing it in a backup archive.
+ * Hierarchical or tag-based organization of projects.
+ * List of JACK applications. Applications are always started through
+   ladish to have restored runtime environment closer to one existed
+   before project save.
+ * Distributed studio - network connected computers. Netjack
+   configuration is part of the studio and thus is saved/restored.
+ * Collaborate with the X11 window manager so window properties like
+   window position, virtual desktop and screen (multimonitor) are
+   saved/restored.