Deployability is a big deal. We should research doing deployment via Silver Lining which looks like it would make deployment fairly easy and also looks very easily compatible with the tools we already have. Currently Rackspace Cloud seems to be the only reasonable option there, but that doesn't seem any more terrible than shared hosting, and more local hosting looks possible.

Trying to make a Silver Lining deployment option anyway can't be anything but a good/useful idea.

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.

We need a script that a contributor could use to wipe their buildout environment and the mongodb database.

This would be useful for:

1. testing clean-slate installs
2. development of initial startup stuff
3. fixing a development environment that's fux0rd due to bugs
4. some fourth thing

Adding Chris as a watcher because he asked me to make the bug.