id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	size
23	Handle multiple FYSM instances better	adehnert		Right now, we need to make code changes every summer to reflect the next Midway date (for example, see bd2bc21be18f81ecbfb7a). Also, if we mysteriously want to run multiple FYSMs in one year (*cough*), we have to deploy a new instance of the entire app. It'd be good to create a FYSMSeason model or some such with a field for letter (and maybe what the abbreviation stands for, if we want to support the latter use case...).	enhancement	new	normal	Summer 2013	FYSM					large