Restrict timeslots in json export
Currently, the timeslot export works by using a uniform discretization of the time period [event.start, event.end], e.g. by dividing this evenly into 1h slots. This is undesirable as this schedules workshops at timeslots that conflict with other conference aspects, e.g. breaks or sleep time.
Furthermore, at import this assumes that all slots need to start a whole number of slot length after the event start. If for example the event starts at an whole hour and an AK slot is 1h, then only slots starting at XX:00 are considered.
We might want to restrict the json export to "default slots".
Edited by Felix Blanke