Creating a challenge

1. Challenge author creates a challenge repository.
2. Added the new challenge to gochallange repository. Commit the change.
3. Deploy the change. We can cut this step by using GitHub commit hook (TBD).

Participating in a challenge

Via http://golang-challenge.com/

TBD

Via CLI

TBD

Submission review process

1. Every participant has only one valid submission, which is the latest one.
2. Submissions are immutable - e.g. when the submission is received, it can not be edited or removed.
3. Participant can submit multiple solutions, in which case the later one take precedence.
4. Hash of the latest received solution is available to the participant (TBD: on the website, or via CLI tool), and is the source of truth regarding the latest submitted version of the code.
5. When a re-submission is received on top of a solution that is already reviewed, the participant is flagged for another review, which may happen only after the challenge is closed (up to the team of evaluators to decide).