I want to introduce the Community Oriented Development Extravaganza, Requiring Extreme Vigor Inciting Extraordinary Winners (or CODE REVIEW) 2017 Challenge. Traditionally our Community Challenges are non-competitive, this challenge aims to change that just a bit.
We usually have these challenges run for a month, and we announce them a month in advance except in certain situations where we want to boost participation. This time I'm going to run the announcement for three (3) months and run the challenge another three (3) months. At the end of the 6-month period, I will award a 500 reputation bounty to the winner of the challenge.
Major dates for the challenge are below:
- Thursday, 1 June 2017: Challenge begins accepting suggestions
- Thursday, 31 August 2017 23:59:59 UTC+0000: Challenge finishes accepting suggestions
- Friday, 1 September 2017 00:00:00 UTC+0000: Challenge begins
- Thursday, 30 November 2017 23:59:59 UTC+0000: Challenge ends
- Friday, 1 December 2017: Winner is announced from entries
How does one win?
In order to support the idea of a winner, we have to make sure that there is something to 'win'. Each challenge suggestion must have a detailed list of possible points to be awarded, and the participants are graded based on how many total points they earned (out of possible points).
The exact details of the awards will be announced later in the season, but at a minimum the following will be awarded:
- The first-place winner will receive a 500-reputation bounty;
- In the case of multiple first-place winners then each winner will receive a 250-reputation bounty;
If participation is high (left to the discretion of the members of the community who are offering the rewards) then an additional tiered reward system may be put in place.
How should suggestions differ from normal?
The only difference that suggestions require from traditional community-challenge questions is that they must detail specific features that require implementation and the total point-count for each feature. Challenge suggestions may mark features as 'optional' or 'required', and if a participant fails to implement all 'required' features then they are disqualified.
You may not reuse any previous community challenge selections as normally required, but you may re-suggestion un-selected challenges, and suggest challenges that are somewhat large in scope.
How does one enter as a participant?
A question with the entry requirements (also included below) and a list of all entries will be posted on Friday, 1 September 2017.
Participating is easy, and simply requires one to meet all criteria below:
- Complete all required portions of the selected challenge;
- Post the implementation of the challenge as a question on the main-site tagged community-challenge;
- Post an answer to the entry question posted here on meta;
- Include a link to the entry question in the answer to the entry form;
You may update your entry at any time (which means you may post iterative reviews as well), all entries will be judged at the end of the challenge season (Thursday, 30 November 2017). Entries may make as many revisions as possible, but the question linked in the entry form at 23:59:59 UTC+0000 on Thursday, 30 November 2017.
Make sure you post the suggestions you have for this extravaganza in this question, the most upvoted answer at the end of the day on 31 August 2017 will become the challenge for this three-month extraordinaire!