Preparing to have something concrete to show for dev-day

However, if you have remarks before the build day, don't
hesitate to send them my way.
Clarified lots of issues.

pep-0206.txt

@@ -94,9 +94,7 @@ Connection to Distutils
     will be easy enough to add other Python modules as user requests direct
     us.
     
-
-
-Software covered by the GNU Public License
+Software covered by the GNU General Public License
 
     While many Python modules rely on software distributed under the
     GNU General Public License and the GNU Lesser General Public
@@ -108,15 +106,24 @@ Software covered by the GNU Public License
     to make closed-source redistribution legal might cost more then
     the benefits.
 
+How It Is Implemented
+
+    Sumo-Python is basically be a set of scripts, which download
+    a Python source tarball, and source tarballs for all the modules.
+    Then it unpacks everything, modifies Setup.in (or whatever mechanism
+    will be in place by Python 2.1, and puts in a little
+    shell script which builds everything. Then it will repack it
+    into the huge tarball which will be a sumo-python-version.tar.gz,
+    which users can then download and install.
+
+    Inside the tarball, running the script
+
+    build-everything [--prefix ...]
+
+    Will compile and install a sumo interpreter into specified prefix.
 
 Open Issues
 
-    Where does all this source live? 
-
-    What should the build procedure look like?
-
-    How are the additional modules tested?
-
     ESR also mentioned libpng, but I don't know of a Python module
     that uses it.