flesh out contributing howto

[Will Kahn-Greene]

The documentation will have a howto on contributing. This is in
addition to the hacking howto. We decided last week that it was a
good idea to have two separate chapters so that we can more easily
focus on getting non-code contributors into the project.

For April 30th, the contributing howto should have the following
sections:


1. filing bugs
2. translating
3. hacking -- which refers to the hacking howto
4. theming -- which refers to the theming howto (which will be a
   stub for April 30th)
5. where to go when you get stuck

We should have a section for each kind of work we need help with.
What other sections should it have?

Adding everyone to the watch list on this one because it needs more
thought.

[Will Kahn-Greene]

Putting this in the 0.0.1 target.

[Will Kahn-Greene]

We did a contributor howto sprint party and it was moderately
successful. I think the document is good enough, though it'd do a
lot better if:


1. Deb did a pass on it
2. Matt did a pass on it
3. Rob did a pass on it

Can you three do a pass on the document in the next few days?

The current version is here:
`http://gitorious.org/mediagoblin/mediagoblin/blobs/master/docs/contributinghowto.rst <http://gitorious.org/mediagoblin/mediagoblin/blobs/master/docs/contributinghowto.rst>`_

[Will Kahn-Greene]

I got Asheesh to do a pass on it and I'm really happy with the
results. I'm going to close this one out.

[Will Kahn-Greene]

The original url for this bug was ​http://bugs.foocorp.net/issues/274 .