Repository navigation
Add presentation uploads for talk speakers - #803
KainatJamal wants to merge 3 commits into
Conversation
| ] | ||
|
|
||
| operations = [ | ||
| migrations.AddField( |
There was a problem hiding this comment.
A single presentation field isn't the right solution.
Conferences will want to do things like have the pdf presentation and a link to supporting info like code samples as separate downloads, or potentially multiple downloads (presentation, article, supporting materiel).
| verbose_name=_('presentation'), | ||
| ), | ||
| ), | ||
| ] |
There was a problem hiding this comment.
We already have the File model used for pages and sponsors, which allows multiple items and descriptions for iterms - anything here should be closer to that.
| </ul> | ||
| {% endif %} | ||
|
|
||
| {% if object.presentation %} |
There was a problem hiding this comment.
Presentation visibility needs to be more controlled.
Conferences may want to allow speakers to upload stuff earlier for review, but not make the presentation or article visible to the public until after the conference (or at all), for example.
|
Thank you for reviewing my contribution and explaining these design considerations. @drnlm I understand that a single presentation field would be too restrictive and that the existing File model would be a better starting point for supporting multiple attachments. I also understand the need for configurable visibility so that uploaded files can remain private for review and only become publicly accessible when the conference organizers decide. I'll investigate how the existing File model is used for pages and sponsors, and revise my implementation to follow the project's existing approach. Could you also clarify what visibility controls you would expect for talk attachments? For example, should visibility be managed individually for each file by conference administrators? |
|
Hi @drnlm |
Summary
This change adds a presentation and file attachment upload system for talks in Wafer.
It allows talk speakers and conference administrators to upload and manage multiple attachments associated with a talk, rather than relying on a single presentation file.
Features
The implementation uses a dedicated
TalkFilemodel and reuses Wafer's existing permission and administration patterns.Testing
wafer.talkstest suite: 139 tests passed.git diff --checkpassed.Related Work
The corresponding DebConf-specific template integration is submitted separately:
Debian Salsa: [wafer-debconf MR !362 — Display talk attachments on DebConf talk pages](https://salsa.debian.org/debconf-team/public/websites/wafer-debconf/-/merge_requests/362)
Related issue: [wafer-debconf #94](https://salsa.debian.org/debconf-team/public/websites/wafer-debconf/-/issues/94)