Lightning talks have become popular recently, and HackerTracker doesn't have an effective way to represent them. (Thunder talks are like lightning, but are slower-paced / have longer talk duration.)
This will require something to the effect of a single scheduled event being associated with multiple content entries. For example, there could be a lightning session from 13:00 - 14:00 with 8-10 talks scheduled to happen during that event (ordered or unordered). I.e.,
Lightning talks
Saturday, 17:00 - 17:30
JimBob's recipe for homemade BBQ
Hacking into pacemakers
Support your local library
The effect of COVID19 on the hackerspace's sourdough
A plea for assistance with the city's open-data project
or
Thunder talks
Saturday, 18:00 - 18:45
Nikita talks about the new book club
Linda thanks everyone for attending the final event of the day
Jeff presents an abridged post-mortem of the media-server failure
PyOhio 2020 used thunder talks as their sole scheduling mechanism this year; they scheduled a block of time (i.e., 45 minutes) and during that block they presented 2-3 talks. If you wanted to see only the second talk, you had to pay attention to the first (or at least part of it) in order to not miss it. There is no guaranteed slot-timing for content entries within a lightning/thunder event. Using the existing event-description for all of the various content in an entire lightning talk event isn't feasible; there is frequently links (to slides or videos), speaker information, info about how to get involved, etc.
Lightning talks have become popular recently, and HackerTracker doesn't have an effective way to represent them. (Thunder talks are like lightning, but are slower-paced / have longer talk duration.)
This will require something to the effect of a single scheduled event being associated with multiple content entries. For example, there could be a lightning session from 13:00 - 14:00 with 8-10 talks scheduled to happen during that event (ordered or unordered). I.e.,
Lightning talks Saturday, 17:00 - 17:30
or
Thunder talks Saturday, 18:00 - 18:45
PyOhio 2020 used thunder talks as their sole scheduling mechanism this year; they scheduled a block of time (i.e., 45 minutes) and during that block they presented 2-3 talks. If you wanted to see only the second talk, you had to pay attention to the first (or at least part of it) in order to not miss it. There is no guaranteed slot-timing for content entries within a lightning/thunder event. Using the existing event-description for all of the various content in an entire lightning talk event isn't feasible; there is frequently links (to slides or videos), speaker information, info about how to get involved, etc.