diff --git a/PLAN b/PLAN
index d56f1cc0..550e9218 100644
--- a/PLAN
+++ b/PLAN
@@ -47,3 +47,18 @@ Making it all happen
   second tool takes packages from said repos and makes the install and CD set.
   Working on the second tool first makes sense, as it can be used today with
   existing Core and Extras repos.  Later, tool #1 can grow from #2.
+
+Contributing
+  Currently development discussion happens at fedora-buildsys-list@redhat.com.
+  The source is held via mercurial:
+  anon - http://linux.duke.edu/projects/pungi
+  auth - ssh://login.linux.duke.edu//home/groups/pungi/hg/pungi
+
+  To run pungi, currently you need root level access.  This is because it has
+  to create loopback devices for disk images.
+  
+    sudo ./__init__.py --comps tests/comps.xml \
+         --yumconf tests/yum.conf.x86_64 --destdir /srv/pungi \
+         --cachedir /srv/pungi/cache --arch x86_64
+
+  Of course, fill in some of your own values.
diff --git a/pungi.py b/pungi.py
index 55a28ab7..bea44636 100755
--- a/pungi.py
+++ b/pungi.py
@@ -19,7 +19,7 @@ class Pungi:
     def __init__(self, opts):
         self.opts = opts
         self.prodpath = 'Fedora' # Probably should be defined elsewhere
-        self.basedir = os.path.join(self.opts.topdir, self.opts.arch, self.prodpath, 'base') # Probably should be defined elsewhere
+        self.basedir = os.path.join(self.opts.destdir, self.opts.arch, self.prodpath, 'base') # Probably should be defined elsewhere
         os.mkdir(self.basedir)
         os.link(self.opts.comps, os.path.join(self.basedir, 'comps.xml'))