This is kind of a hand-wavy issue in that it's hard to discern when it's "completed". I vote we can use a gut feeling to decide one way or the other.

Thus this bug is for helping to figure out what goes into the Hacking HOWTO and making sure it gets there.

For April 30th, we want a Hacking HOWTO chapter in the documentation that covers the following:

1. how to build a working development environment for GNU MediaGoblin
2. how to run GNU MediaGoblin in a development environment (the deployment howto covers how to run it in a production environment)
3. how to contribute patches
4. where to look for things to work on
5. where to look for help when you're stuck

The document is in the mediagoblin repository in docs/hackinghowto.rst .

Chris is tentatively calling the stack we're using Beardomatic. This stack needs some documentation to make it a lot easier to work with for existing and new contributors. This documentation would include the following:

1. the components in the software stack
2. how to create a new view
3. how to add something to the database
4. ...

Adding Chris to the watcher list so he can expound on the above list.

We currently have a "softwarestack" chapter. I think we should rework that into a Beardomatic chapter and cover all the other things in there.

Specifically, link to: https://gitorious.org/mediagoblin/