id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc	parents
14	flesh out design decisions in docs	Will Kahn-Greene	Christopher Allan Webber	"{{{
#!rst
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



}}}"	defect	closed	minor	0.0.1	programming	FIXED