Guideline for Reviewer
The Reviewer is responsible for advising the Editor and the Problem Setter, checking the documents prepared by the Editor and the contest problems assembled by the Problem Setter.
Reviewing the editor:
3 weeks before the lecture day, the Editor (document writer) should already have prepared the outline of the document, and sent it to the Reviewer for a detailed check.
2 weeks before the lecture day, the Editor (document writer) should already have prepared the first draft of the document, and sent it to the Reviewer for a detailed check.
1 week before the lecture day, the document should be finalized and published on inzva’s discord channel.
The Reviewer should warn the editor about these topics:
Any blurred point
Additions if needed
Additional explanations if needed
Any missing subjects
Grammar mistakes and typos
Wrong LaTEX usage
Reviewing the problem setter:
2 weeks before the contest day, the Problem Setter should have already prepared the contests (online and onsite contests).
1 week before the contest day, the review of the practice problems should be finished.
2 days before the contest, the review of the contest problems should be finished.
The Reviewer should check and warn the Problem Setter about these topics:
Problem topics and difficulties
Test case qualities
Review should not only give feedbacks but also track and warn the preparers about related deadlines.
The Problem setter and the Editor must make the imperative adjustments declared by the Reviewer.
The Reviewer should check the problems chosen by the Problem Setter and the Editor to avoid using the same problems.