ico-arrow-big-left

Community App - Experimental Bug Bash

Key Information

Register
Submit
The challenge is finished.
Show Deadlines

Challenge Overview

Hey Top Coders! Our Community App needs various fixes and improvements, thus the Bug Bash. Experimental it is to add extra F2F flavour, and, hopefully, to make the format more fun and efficient. In a few words: in this Bug Bash we won’t lock the issues exclusively for the competitors who picked them up first, instead you can pick any ticket still open and try to make it faster than other people. Here are the rules:
  1. You can work on any of the issue tickets marked by the label Bug Bash - OPEN FOR PICKUP; any discussion related to a specific ticket should be done in the ticket itself; you should still watch the challenge forum for any global announcements/disscussion.
  2. Once your solution is ready, create Pull Request (PR) against the develop branch, clearly referencing the issue it relates to the in the PR; then leave a comment in the original issue ticket referencing the PR ready for review, and the hash of the latest commit in the PR. It is very important: as it is possible to push new changes into existing PRs, we’ll review submitted code in the order of comments in the original issue ticket (in case of multiple PRs from different competitors for the same issue)!
    Note that once you have created a PR, it will be visible to other competitors as well, which has both some pros and cons!
  3. The review will be done directly on the submitted PR, and along with the comments on code, if any, will have one of three possible outcomes:
    1. PR is accepted as it is;
    2. PR is accepted, but demands final fixes - it means that your submission generally solves the issue in the correct way, but lack some (most probably code style) clean-up, or additional fixes for some corner cases. We’ll expect you to make such final fixes in your PR before the end of the Bug Bash (i.e. the issue is locked exclusively for you from that moment). If you decide to not provide requested final fixes in time, we’ll reduces the issue payment by 30% (i.e. you’ll be paid the 70% of the original ticket value);
    3. PR is rejected. The ticket stays open for you, and everybody else to work on it.
  4. To get paid smoothly, you should submit a placeholder submission to the original Bug Bash challenge in Topcoder platform. Ideally (but not obligatory), you should submit there a text file with your own record of the issues you have solved and the money your should be paid. Of course, we keep our own records, but such form of submission will allow to easily double-check and avoid any mistakes early.
P.S.: Feel free to discuss the format of this Bug Bash and suggest any improvements for the future Bug Bashes in the challenge forum.


Final Submission Guidelines

See instructions above

Payments

Topcoder will compensate members in accordance with our standard payment policies, unless otherwise specified in this challenge. For information on payment policies, setting up your profile to receive payments, and general payment questions, please refer to ‌Payment Policies and Instructions.

ELIGIBLE EVENTS:

2018 Topcoder(R) Open

REVIEW STYLE:

Final Review:

Community Review Board
?

Approval:

User Sign-Off
?

ID: 30060801