[Bug Bounty] - Arena Applet PAY PER BUG FIX Challenge

Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Welcome to [Bug Bounty] - Arena Applet PAY PER BUG FIX Challenge! The goal of this challenge is to fix a number of reported open bugs for arena applet, which is the main tool for SRMs now.

Bug Bounty is a program that will pay community members to fix bugs reported in previous challenges or by other members. This code fix challenge will have member assigns themselves to an issue. The bugs will be very small fast fixes that shouldn't take more than a few hours to fix.

Challenge Scope

This challenge will have a long time frame which is different than the usual code challenge. 

For this challenge, you will assign a bug that has corresponding dollar amount and labeled "fix me" to yourself from our current queueHowever you are not able to really assign the issue to yourself, instead you should just comment on the issue saying you're working on it, the 1st member to comment on an issue is considered the assignee. You should also follow the rules below:

  • Each member may only assign one issue to themselves at a time. Assign, work, submit to OR, look for the next issue. 
  • If a member is no longer working on an issue they should delete the assignment comment from the issue. 
  • If a member commented that they are working on the issue and the issue isn't closed in two days, we will remove the comment so other members can work on the issue.

We assigned prize for each open bugs which are waiting for be fixed. The competitor can select any open bug to work on. Once you have the fixed the bug, please submit your code and the corresponding bug number to OR, we will review it and pay you the bug prizes though online review after challenge is closed.

All Open Bugs are are shown here but please only check the ones with a label "fix me". The bug list will be updated frequently, new bugs will be shown and old bugs may be fixed by the other competitors, so keep watching the bug list.

If you are the assignee of an issue and found out it's already fixed, you can report in your comment saying the issue can be closed and you'll also be paid $25 for verifying the fix.

How to Test

Each competitor will be assign a Arena VM to work on, where you can setup your own data. But you can also test against production for easily problem reproduce. How to do that? You can repalce the tc.cloud.topcoder.com with www.topcoder.com in arena.sh/arena.bat.

Review Scoring

Since this is not a normal challenge, review scores don't mean any thing. The reviewer will score your submission based on the number of bugs you fixed. Scorecards are only needed to complete the challenge process. 

Submiting Fixes

All fixes must be submitted as pull requests toward the bugbounty-1 branch, all requests NOT done to this branch will be rejected.

You should also submit a text file to OR listing the fixes you made and your github username so we can assign payments to you in the system.

Resources and Guidelines

About Code Base

For the code under /home/apps/dev directory, some are hosted in internal svn repositories, some are hosted in private repositories in github.

You can check this wiki for details.

For SVN Access, please send request to support@topcoder.com, For github access, please post your github account in forum to ask PM to grant you access.

Arena VM

Before asking your own VM, you need to have a public key on your profile before asking for the VM.

You can find more details on how to generate a key here and how to connect using it here.

To use the Arena VM, please follow instructions here.

 

 



Final Submission Guidelines

Submission Deliverables

  • The code
  • Simple deployment guide / verification guide and the list of issues you fixed
  • The list of your pull requests covering all fixes

Final Submission

For each member, the final submission should be uploaded via the challenge detail page on topcoder.com

ELIGIBLE EVENTS:

2015 topcoder Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30046992