Overhauls TOC of manual

This work is based on discussion and etherpadding (is that a verb) on
April 14th between Deb, Greg, Karen, Will, and Chris.

It was an epic collaborative sprint.

1 files changed, 58 insertions, 0 deletions

diff --git a/docs/contributinghowto.rst b/docs/contributinghowto.rst
new file mode 100644
index 00000000..1b34badc
--- /dev/null
+++ b/docs/contributinghowto.rst
@@ -0,0 +1,58 @@
+====================
+ Contributing HOWTO
+====================
+
+We're super glad you want to contribute!
+
+There are a variety of ways you can help us and become part of the
+team.  We're not just looking for coders!  We're also looking for
+documentation writers, users, testers, evangelists, painters, bakers,
+candle-stick makers...
+
+However, if you are a coder and you're looking to code, check out the
+:ref:`hacking-howto`.
+
+The rest of this chapter talks about different things we need your
+help with.
+
+**File bugs**
+
+    Filing bugs is an important part of any project.  For more
+    information on filing bugs, see :ref:`filing-bugs`.
+
+
+**Translate GNU MediaGoblin**
+
+    Knowing more than one language is an important skill.  If you are
+    multi-lingual and are interested in translating GNU MediaGoblin,
+    see :ref:`translating`.
+
+FIXME - add additional things here
+
+
+.. _filing-bugs:
+
+File bugs
+=========
+
+GNU MediaGoblin uses a bug tracker called `Redmine
+<http://www.redmine.org>`.
+
+The bug tracker is at http://bugs.foocorp.net/ and bugs go in the
+``GNU mediagoblin`` project.
+
+FIXME - how to file a good bug report
+
+
+.. _translating:
+
+Translate GNU MediaGoblin
+=========================
+
+FIXME - need to write this
+
+
+Where to go when you get stuck
+==============================
+
+FIXME - need to write this