-
Notifications
You must be signed in to change notification settings - Fork 3
Including handle in the submission #46
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
Comments
It makes no sense. Because if a competitor and a reviewer want to hack the rules, the competitor can just privately email the ID of his submission to the reviewer. Thus, you may close any other ways for a reviewer to figure out the identity of competitors, but you'll never be able to prevent this simple way to hack the system. The only way to deal with this is: if a review is not fair, other competitors should bring it up to the co-pilots/managers/community, the issue should be considered in public, and all involved in cheating and/or unfair judgement should be strictly punished. |
Totally agree with @birdofpreyru ! |
It's not related to cheating because we can't prevent it. See last post https://apps.topcoder.com/forums/?module=Thread&threadID=623369&start=0&mc=8#1021109
|
Anyway, I don't like this because:
These demands some changes to the codebase, i.e. $$ to be paid and work to be done. Thus, needs efforts from all parts, while the impact is not obvious for me, I believe in 95% of cases, any initial bias does not change the outcome of reviews, while the rest 5% are probably closer to cheating, and won't be prevented by these efforts. |
We need to discuss a way for us to create a process/rules/policy to keep anonymity |
The review process is anonymous by default, and members shouldn't reveal
their identity anywhere.
However, members can be recognized in an easy way by:
The text was updated successfully, but these errors were encountered: