To design, build, and test a database engine for reporting, tracking, and analyzing roller derby bout scores. It's good to see this longtime goal of finally nearing fruition, and it's a great first step on the lengthy road to the real holy grail of derby data mangling: skater-by-skater, jam-by-jam records of scoring, penalties, and assists. You have to crawl before you walk, but it's good to finally be crawling. ~Hurt Reynolds

Test out a theory of web development. A simple observation that CS always thinks about encapsulation, and web development so often screws this up. I think every single piece of this project should be a "self" rendering encapsulated component. Every major table, every display, should be in a well behaved div that you can cram into anything with a reasonable set of parameters. They should be generated and styled dynamically so that somebody can call components that return functional namespace "objects." You should be able to call a component and render it in a generic layout, or return HTML & Javascript via ajax. If you cannot, obviously you broke encapsulation. Plus I think it will really help us not step on each others toes if you don't have to worry about somebody constantly screwing with the "main" layout page. ~Justin