Goals

The primary goal of ConMaster is to replace the critical functionality of the 4D version.

This means CRUD for Person & Event (along with their child tables Person_Section & Section), the ability to register people for events, print tickets & badges. Basic reports will also be included.

This initial version of ConMaster will have limited security, and basically assume that everyone working with it is trusted (and forgiving) convention staff.

I hope to have this basic version 110% ready for Ben Con in May of 2003.

Once this is done and very well tested in production, we can move on to the next phase.

The next phase will be to implement self-registration. This is a big deal, both in importance and complexity of implementation. Since we will be handling money with this phase, we need to do _extemely thorough_ testing.

Once this is done, we can move onto the final phase, which is implementing the exciting new features that open up with putting ConMaster on the Internet, such as user-submitted event reviews, sharing event and judge data between conventions, doing cross-convention reports, and essentially becoming an organized gaming nexus.

Throughout development, I want to focus on reliability and maintainability, as well as accessibility to novice developers. Because of this, I will suggest that any major technology change be a fork.

So, keep a tight focus on each phase, and together we can build something to really organize organized gaming!

Tally Ho!

Tim White
ConMaster Project Lead