Opened 14 years ago

Last modified 12 years ago

#23 new enhancement

Handle multiple FYSM instances better

Reported by: adehnert Owned by:
Priority: normal Milestone: Summer 2013
Component: FYSM Version:
Keywords: Cc:
Size: large

Description

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...).

Change History (1)

comment:1 Changed 12 years ago by adehnert

  • Size set to large

In ASA-#242, we killed FYSM slides for this year's FYSM. When this ticket gets fixed, it would be nice to link FYSM slides from years when they existed.

Note: See TracTickets for help on using tickets.