JOINDIN-749: Remove the ability to add or delete speaker when start date of the talk has been reached
Opened this issue · 3 comments
Jira issue originally created by user wim.godden:
Apparently some people have started deleting themselves from talks when they receive bad feedback, probably to avoid not being selected for other conferences. This defeats the whole purpose of Joind.In if they consistently do this (which some are doing).
Others seem to delete themselves even before the conference, quite possibly for the same reason, with the goal of adding (or asking) themselves when they get good feedback.
I would suggest making it impossible to add or delete speaker(s) if the start date of the talk has been reached.
I'd be happy to implement this, but would like to receive feedback on this proposal first.
Comment created by heiglandreas:
Personally I think it's a good idea. There should be no reason to remove a speaker after a talk has been held. And there should be no reason for the speaker to remove himself after the talk was claimed and that claim was approved. We should though leave the possibility to remove a speaker to the event-admin(s).
And if someone thinks they don't want to be associated with a badly rated talk the still can contact the organizer of the event or the joint.in-team to be removed.
So from my side: Go ahead Wim.
Implementation-Details:
I'd implement this in the API as well so that removal will not be possible regardless of what UI you are using. And I'd completely remove the functionality to remove a speaker from the legacy-website with a reference that users can do that using the web2-interface…
Comment created by wim.godden:
Web2 implementation done and sent PR.
Will look at the legacy and API tomorrow. Need to find out how that code is written first ;-)
This issue has been hanging around a bit too long, if needed please update or comment.