Deploy this for society events?

[matiasilva]

Stalls become a permanent presence for the event before, after and during. Domain would be something like events.srcf.net.

[dnlburgess]

A (non-exhaustive) list of things we might want to do:

• Rethink the current way we identify events / societies. This is currently based on the short_name field, which is, in retrospect, not ideal even for societies, let alone anything more general. Perhaps we should move towards using a random uid to identify the society instead?
• Extensive testing to ensure that there are no strings still referring to the 'Freshers' Fair' or 'societies'. Do we want societies to become groups or events or something else?
• Change the code to remove references to 'societies'? Not overly important but probably nice to do at some point.
• The option of requiring sign-in with Raven for some events? Perhaps event administrators can specify a list of approved CRSids "members" that can access an event?
• Slim down the users table so we only store CRSids and don't ask for other details.

Should the application on events.srcf.net be forked to a separate repo or are we continuing with LBT?

[sourtin]

Probably want to add another level of namespacing above societies/groups, so that a single instance can be responsible for different domains such as events.srcf.net, freshers.srcf.net, fair.mysociety.com with each having distinct groups and rooms. This would then imply adding functionality to control.srcf.net to allow binding a namespace to a domain.