"Review" is ambiguously used for both feedback and the process of accepting talk submissions

[MikkCZ]

Problem and impact

The term review is used in pretalx in two places - to describe the feedback process from the attendees/visitors to speakers, but also in the context of accepting/rejecting talk proposal submissions by the organization team.

The ambiguity is especially notable during localization process, and given how gettext works, there might even be the same string used for both feature, which is limiting the flexibility for locales to translate the terms differently. Which is Czech for example there is no single words that would fit in both contexts without actually increasing the ambiguity even compared to English.

Expected behaviour

I am not a native English speaker, but it would be nice to have two different terms for these two contexts. One solution that I think would be acceptable is to just go with feedback/to provide feedback instead of review in the context of giving a post-event feedback from attendees to the speakers.

Steps to reproduce

Screenshots

No response

Link

No response

Browser (software, desktop or mobile?) and version

No response

Operating system, dependency versions

No response

Version

No response

[rixx]

I'd be happy to use clearer wording here – however, "feedback" would be just as ambiguous, as pretalx supports post-event feedback under that name.

Maybe we ought to rename the page to "preview"? As that's what it is, in the end.

[rixx]

If I'm not mistaken, the double meaning was only in a single place (I hope?), because I really tried to make sure that it's always "review" for organiser reviewers and "feedback" for attendees. Your issue reads like that's not the case in general, but I'm pretty sure it is?