Skip to content
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

Feature Request: "Deferred" Submission Status #1265

Open
SamsaraTAS opened this issue May 1, 2022 · 4 comments
Open

Feature Request: "Deferred" Submission Status #1265

SamsaraTAS opened this issue May 1, 2022 · 4 comments

Comments

@SamsaraTAS
Copy link
Collaborator

"Deferred" or "Holding" or some other name that essentially means "we'll take a look at it later", really.

Basically, this status would serve as a counterpart to Rejected, tagging submissions that are explicitly not being rejected for optimization reasons, i.e submissions that could become acceptable in the future with changes to the site. It would alleviate the stigma of having outright rejections on one's account, something which I've seen members of the community worry about, while also allowing for an extremely easy way to tag and find potentially acceptable runs in the future.

In terms of code, I imagine it'd just be 100% identical to Rejected but with the different name. Status logic would just be Judging Underway > Deferred and Rejected > Deferred.

@vadosnaprimer
Copy link
Collaborator

Yeah unless it's something that we can't even sync or something sloppy, this decision is "we'll look into it again if it becomes legitimately acceptable". In a way, rejected would become stuff that can't theoretically fit even into playground.

In terms for forum, rejected, canceled, and deferred would go to the same subforum.

@adelikat
Copy link
Collaborator

adelikat commented May 8, 2022

With my "quick fix" hat on, I'm wondering if this could just be a rejection reason, which is super easy to add

@SamsaraTAS
Copy link
Collaborator Author

As far as I'm aware, the only thing that tracks rejection reasons is the RejectedSubmissions page, which doesn't have sorting and is just a long list of every single rejection. A separate status would allow for workbench filtering to easily bring up a condensed list of just Deferred submissions. Plus, a rejection reason doesn't really address the other issue, which is people being put off by the term "Rejected" itself.

@meshuggahtas
Copy link
Collaborator

Saw the discussion thread on TASVideos forum, here's my personal opinions:

  • Rejected/Rejection is probably the best term to use, used widely in many areas and communities like research, science, school, etc.
  • If the staff wants to help submitters avoid extra emotional effect (as any is nearly impossible in an online community) when their submission gets rejected: Life is hard and there will be times where you get a no despite all of your efforts. That's why there are judgement notes with elaborated reasons, that consists of more than a single word explaining what is the problem and how to improve or what to do in order to get accepted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants