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

Rate Challenge after Submission #224

Open
Bialogs opened this issue Feb 25, 2019 · 1 comment · May be fixed by #532
Open

Rate Challenge after Submission #224

Bialogs opened this issue Feb 25, 2019 · 1 comment · May be fixed by #532

Comments

@Bialogs
Copy link
Contributor

Bialogs commented Feb 25, 2019

Show a short survey after submission of a flag so we can get feedback on what competitors enjoy beyond what they message us.

We already have the code to "do things after successful submission"...

Considerations:

  • Like/dislike?
  • 1-5 Stars?
  • Comment included?
  • Only comment?
  • mandatory?
  • During the competition this is available to only those who solve the challenge?
  • After the competition rating can be opened up on all solved challenges?
@noraj
Copy link
Contributor

noraj commented Feb 25, 2019

My POV:

Maybe several 1-5 stars for:

  • difficulty
  • realism
  • interest/enjoy

+ an open comment

not mandatory

during the competition not after

@Bialogs Bialogs added this to the "In A Box" milestone Feb 21, 2020
camdenmoors added a commit to sesheikholeslam/ctf-scoreboard that referenced this issue Aug 10, 2020
camdenmoors added a commit to sesheikholeslam/ctf-scoreboard that referenced this issue Aug 11, 2020
camdenmoors added a commit to sesheikholeslam/ctf-scoreboard that referenced this issue Aug 11, 2020
camdenmoors added a commit to sesheikholeslam/ctf-scoreboard that referenced this issue Aug 17, 2020
camdenmoors added a commit to sesheikholeslam/ctf-scoreboard that referenced this issue Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants