Recent changes to this wiki:

diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index 106b6ef..fecd2d4 100644
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -2,5 +2,7 @@ Hi,
 
 is it possible to include submodules in a repo-backup? I am trying to backup the repo supercollider, which makes heavy use of submodules.
 
+A second though: I backup an entire oranization with --no-forks, but somehow this doesn't work as expected. For some of the repos attempts are still made to backup forks too?
+
 Thanks
 Rainer

diff --git a/doc/todo/exclude_certain_repositories.mdwn b/doc/todo/exclude_certain_repositories.mdwn
new file mode 100644
index 0000000..c93a822
--- /dev/null
+++ b/doc/todo/exclude_certain_repositories.mdwn
@@ -0,0 +1 @@
+I'd like to suggest a configuration option be added to github-backup to allow for the exclusion of certain repositories. https://github.com/githubschool/open-enrollment-classes-introduction-to-github includes hundreds of forks/branches, and I'd rather not have them downloaded when running "github-backup tomhoover". At one time, I contributed to https://github.com/githubschool/open-enrollment-classes-introduction-to-github; however, it is neither "watched" nor "starred" at this time. 

diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
new file mode 100644
index 0000000..106b6ef
--- /dev/null
+++ b/doc/index/discussion.mdwn
@@ -0,0 +1,6 @@
+Hi,
+
+is it possible to include submodules in a repo-backup? I am trying to backup the repo supercollider, which makes heavy use of submodules.
+
+Thanks
+Rainer

remove install page accidentially copied from etckeeper
Nothing linked to this
diff --git a/doc/install.mdwn b/doc/install.mdwn
deleted file mode 100644
index 346082c..0000000
--- a/doc/install.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-etckeeper is available in git at `git://git.joeyh.name/etckeeper`, or
-[in gitweb](http://git.joeyh.name/?p=etckeeper.git). 
-
-It's packaged in Debian, Ubuntu, Fedora, etc.
-
-Or, you can install it by hand. Before running 'make install', you
-should edit etckeeper.conf and make sure it configured appropriately
-for your distribution.
-
-Distribution packagers may find it more convenient to set CONFFILE to point
-to a different etckeeper.conf that is preconfigured for your distribution.

better install instructions
diff --git a/doc/README.mdwn b/doc/README.mdwn
index 2367a7c..ad44b88 100644
--- a/doc/README.mdwn
+++ b/doc/README.mdwn
@@ -10,8 +10,10 @@ For example, on a Debian system:
 
 	sudo apt-get install haskell-stack
 
-Then to build and install github-backup, clone it, cd inside, and run:
+Then to build and install github-backup:
 
+	git clone https://git.joeyh.name/git/github-backup.git
+	cd github-backup
 	stack install
 
 There is also a Makefile, which uses cabal to build, and installs

new website
diff --git a/README.md b/README.md
deleted file mode 100644
index 2367a7c..0000000
--- a/README.md
+++ /dev/null
@@ -1,101 +0,0 @@
-github-backup is a simple tool you run in a git repository you cloned from
-GitHub. It backs up everything GitHub publishes about the repository,
-including branches, tags, other forks, issues, comments, wikis, milestones,
-pull requests, watchers, and stars.
-
-## Installation
-
-First install Haskell's [stack](http://haskellstack.org/) tool.
-For example, on a Debian system:
-
-	sudo apt-get install haskell-stack
-
-Then to build and install github-backup, clone it, cd inside, and run:
-
-	stack install
-
-There is also a Makefile, which uses cabal to build, and installs
-a man page, bash completion file, etc. This is recommended for use when
-making packages of github-backup.
-
-## Use
-
-  Run `github-backup` with no parameters, inside a git repository cloned
-  from GitHub to back up that repository.
-
-  Or, if you have a GitHub account, run `github-backup username`
-  to clone and back up your account's repositories, as well
-  as the repositories you're watching and have starred.
-
-## Why backup GitHub repositories
-
-There are a couple of reasons to want to back this stuff up:
-
-* In case something happens to GitHub. More generally because
-  keeping your data in the cloud *and* relying on the cloud to
-  back it up is foolish.
-
-* In case someone takes down a repository that you were interested in.
-  If you run github-backup with your username, it will back up all 
-  the repositories you have watched and starred.
-
-* So you can keep working on your repository while on a plane, or
-  on a remote beach or mountaintop. Just like Linus intended.
-
-## What to expect
-
-Each time you run github-backup, it will find any new forks on GitHub. It
-will add remotes to your repository for the forks, using names like
-`github_torvalds_subsurface`. It will fetch from every fork.
-
-It downloads metadata from each fork. This is stored
-into a branch named "github". Each fork gets a directory in there,
-like `torvalds_subsurface`. Inside the directory there will be some
-files, like `torvalds_subsurface/watchers`. There may be further
-directories, like for comments: `torvalds_subsurface/comments/1`.
-
-You can follow the commits to the github branch to see what information
-changed on GitHub over time.
-
-The format of the files in the github branch is currently Haskell
-serialized data types. This is plain text, and readable, if you squint.
-
-## Limitations
-
-github-backup is repository-focused. It does not try to back up other
-information from GitHub. In particular, social network stuff, like
-users who are following you, is not backed up.
-
-github-backup does not log into GitHub, so it cannot backup private
-repositories.
-
-Notes added to commits and lines of code don't get backed up yet.
-There is only recently API support for this.
-
-The labels that can be added to issues and milestones are not backed up.
-Neither are the hooks. They could be, but don't seem important
-enough for the extra work involved. Yell if you need them.
-
-github-backup re-downloads all issues, comments, and so on
-each time it's run. This may be slow if your repo has a lot of them,
-or even if it just has a lot of forks.
-
-Bear in mind that this uses the GitHub API; don't run it every 5 minutes.
-GitHub [rate limits](http://developer.github.com/v3/#rate-limiting) the
-API to some small number of requests per hour when used without
-authentication. To avoid this limit, you can set `GITHUB_USER` and
-`GITHUB_PASSWORD` (or `GITHUB_OAUTH_TOKEN` obtained from
-<https://github.com/settings/tokens>) in the environment and
-it will log in when making (most) API requests.
-
-Anyway, github-backup *does* do an incremental backup, picking up where it
-left off, so will complete the backup eventually even if it's rate limited.
-
-## Author
-
-github-backup was written by Joey Hess <id@joeyh.name>
-
-It is made possible thanks to:
-
-* Mike Burns's [haskell github library](http://hackage.haskell.org/package/github)
-* GitHub, for providing an API exposing this data. 
diff --git a/README.md b/README.md
new file mode 120000
index 0000000..75370e2
--- /dev/null
+++ b/README.md
@@ -0,0 +1 @@
+doc/README.mdwn
\ No newline at end of file
diff --git a/doc/README.mdwn b/doc/README.mdwn
new file mode 100644
index 0000000..2367a7c
--- /dev/null
+++ b/doc/README.mdwn
@@ -0,0 +1,101 @@
+github-backup is a simple tool you run in a git repository you cloned from
+GitHub. It backs up everything GitHub publishes about the repository,
+including branches, tags, other forks, issues, comments, wikis, milestones,
+pull requests, watchers, and stars.
+
+## Installation
+
+First install Haskell's [stack](http://haskellstack.org/) tool.
+For example, on a Debian system:
+
+	sudo apt-get install haskell-stack
+
+Then to build and install github-backup, clone it, cd inside, and run:
+
+	stack install
+
+There is also a Makefile, which uses cabal to build, and installs
+a man page, bash completion file, etc. This is recommended for use when
+making packages of github-backup.
+
+## Use
+
+  Run `github-backup` with no parameters, inside a git repository cloned
+  from GitHub to back up that repository.
+
+  Or, if you have a GitHub account, run `github-backup username`
+  to clone and back up your account's repositories, as well
+  as the repositories you're watching and have starred.
+
+## Why backup GitHub repositories
+
+There are a couple of reasons to want to back this stuff up:
+
+* In case something happens to GitHub. More generally because
+  keeping your data in the cloud *and* relying on the cloud to
+  back it up is foolish.
+
+* In case someone takes down a repository that you were interested in.
+  If you run github-backup with your username, it will back up all 
+  the repositories you have watched and starred.
+
+* So you can keep working on your repository while on a plane, or
+  on a remote beach or mountaintop. Just like Linus intended.
+
+## What to expect
+
+Each time you run github-backup, it will find any new forks on GitHub. It
+will add remotes to your repository for the forks, using names like
+`github_torvalds_subsurface`. It will fetch from every fork.
+
+It downloads metadata from each fork. This is stored
+into a branch named "github". Each fork gets a directory in there,
+like `torvalds_subsurface`. Inside the directory there will be some
+files, like `torvalds_subsurface/watchers`. There may be further
+directories, like for comments: `torvalds_subsurface/comments/1`.
+
+You can follow the commits to the github branch to see what information
+changed on GitHub over time.
+
+The format of the files in the github branch is currently Haskell
+serialized data types. This is plain text, and readable, if you squint.
+
+## Limitations
+
+github-backup is repository-focused. It does not try to back up other
+information from GitHub. In particular, social network stuff, like
+users who are following you, is not backed up.
+
+github-backup does not log into GitHub, so it cannot backup private
+repositories.
+
+Notes added to commits and lines of code don't get backed up yet.
+There is only recently API support for this.
+
+The labels that can be added to issues and milestones are not backed up.
+Neither are the hooks. They could be, but don't seem important
+enough for the extra work involved. Yell if you need them.
+
+github-backup re-downloads all issues, comments, and so on

(Diff truncated)