One of the things we're adding to the manual is a chapter on design decisions. This is important for two reasons:

1. people new to the project can read it, learn what we've decided so far, and why
2. people new to the project can glean more about how we plan to do what we're doing
3. head off "why didn't you do xyz?" questions which the project team has discussed, decided, and moved on
4. gives us a good resource for re-evaluating decisions later on down the road when necessary
5. gives people working on other projects a good resource for working through these sorts of decisions more quickly for their project

For April 30th, we need to do the following:

1. format the question and answer sections in an appropriate way
2. add sections that should be covered that aren't yet
3. add a workflow bit at the bottom for how to add questions in the future

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.

The setup bits in the hacking howto don't work on Fedora 15.

Jef gets this when he runs python bootstrap.py && bin/buildout:

Develop: '/home/jef/mediagoblin/.'
Develop distribution: Paste 1.7.5.1
uses namespace packages but the distribution does not require setuptools.
Uninstalling make_user_dev_dirs.
Updating mediagoblin.
Develop distribution: Paste 1.7.5.1
uses namespace packages but the distribution does not require setuptools.
Installing make_user_dev_dirs.

curious schendje: is that the entire output from buildout? or just a snippet that's everything okay, yes, something's wrong then schendje: I'll look into this... I guess if you like, you can not worry about it and just design into a plain html file and I can incorporate it

What should happen is that running that command downloads all the requirements and builds an environment to run GNU MediaGoblin in.

Making this an issue for 0.0.2.