-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schedule Items needs to track more metadata #384
Comments
In DebConf's experience, venues need to have a video flag. Then being videoed becomes the default for a talks in a venue. Possibly the flag should be on slots, not venues. We've had conferences in the past where we moved equipment between rooms during the conference. Of course, this doesn't guarantee that events will be recorded. You need volunteers to make video happen. So some sort of "request video", "granted video" workflow. |
Based on the recent online portions from PyConZA, it would also be useful to be able to add indicators like "don't have the bot announce this" |
Although maybe the scheduleitem is the wrong level because they can often be deleted when the schedule is updated - perhaps we need to attach the metadata to the schedulable items? |
I think @rhonda would probably appreciate that too |
There are a few existing django lbraries for adding arbitary tags which can probably solve most of this - django-taggit seems to be the most actively maintained of those I've looked at, but I haven't done a complete trawl yet, |
For integration with the video tools, we need to be able to track which items will / are being recorded.
We may actual want to have a few fields here:
video
streamed
etc.
which starts looking more like a list of tags than just an extra field, so we need to think about the exact requirements here a bit.
The text was updated successfully, but these errors were encountered: