Skip to content

Instantly share code, notes, and snippets.

@moritz
Last active November 6, 2018 11:57
Show Gist options
  • Save moritz/6f06ec7153ce396ac2734c2616d8b075 to your computer and use it in GitHub Desktop.
Save moritz/6f06ec7153ce396ac2734c2616d8b075 to your computer and use it in GitHub Desktop.
Revival of the Perl 6 Coding Contest

In the good old times, I really enjoyed participating in Carl Mäsak's Perl 6 Coding Contest.

I'd like to revive this kind of contest, with a few small modifications.

Since running such a contest is a lot of work, I'd like to crowd-source parts of it. This is my idea of how it could work.

  • People can volunteer to be part of the group that crowd-sources the tasks. Of course, task creators cannot participate in the actual contest.
  • In parallel, we work on criteria to evaluate the submitted code. This can be a public discussion.
  • We (if nobody else does, I) announce the contest, the tasks and the deadlines.
  • After submission deadlines, all submissions are published.
  • There is a public commenting phase, in which we prompt everybody to respectfully comment on both positive and negative features of the code.
  • Based on the comments and my own opinions, I will award prizes to whom I consider the winners. (This is mostly to not provide incentives for participants to game the comment/rating phase). I will also encourage others to pledge their own prizes, and either award them independently, or delegate the awarding to somebody else.

What do you all think?

(If it turns out to fit, we could try to correlate this with the Diwali release of Perl 6).

@AlexDaniel
Copy link

Maybe we should do it instead of the squashathon, for example in December.

@hughsimpson
Copy link

This sounds like it could be fun

@pheix
Copy link

pheix commented Nov 6, 2018

Think it's good idea, but a very few comments on it. Anyway, to revival of this contest will be a good event in community life. About the prizes: subscription on Comma IDE will be a great prize.

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