Register
Submit a solution
The challenge is finished.

Challenge Overview

Welcome to Crowd Exchange - [Bug Bounty] Challenge! The goal of this challenge is to fix a number of reported open bugs for the CrowdExchange AngularJS Salesforce.com web application.

A [Bug Bounty] challenge is a program that will pay community members to fix bugs reported. Using Github issues you will assign issues to yourself.  In this [Bug Bounty] this issue vary widely in scope.  Some are small cosmetic changes that shouldn't require more than an hour to diagnose and fix.  And we have other changes that are more significiant.   

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 to yourself from our current list of issues. 

  • List your Github ID in the challenge forums.  The challenge administrator will add you to our private Github repository.
  • Browse the issues and decide which one you would like to tackle first.
  • Each member may only assign one issue to themselves at a time. Assign, work, create a pull request, look for the next issue. 
  • Please see the detailed instructions below in the submission guidelines for how this Bug Bounty will be managed.
  • Deployment instructions for the app can be found in the deployment.txt file in the root directory of the 

We have assigned prize values 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 prize though Jira privately.

Open Bugs shown here are in scope of this challenge and will be designed by the "Open for Pickup" tag. 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.

We'll be paying a $200 bonus to the member who resolves the largest number of "High" issues.  There is a minimum of 2 high issues required before the bonus will be paid.



Final Submission Guidelines

  • - Add your Github Id in the topcoder forums.  The challenge architect/copilot will add you to repository.  You will receive an invite from Github that will give you access to the repository and will allow you to browse the issues.
  • - Each issue in Github has a dollar value. Dollar values are based upon complexity and priority of issue.
  • - You can assign any unassigned issue to yourself with an "Open for Pickup" label (first come first serve).
  • - You can only assign ONE AT A TIME. The nature of it being assigned will indicate it is not available to anyone else.
  • - You will fix the ticket as a pull request to the "master" branch!  Documentation about pull requests can be found here
  • - Once a ticket is fixed, you should label it "Ready for Review" where it will then be verified. If something is still broken, the copilot/architect will comment on the ticket.
  • - After submitting and tagging "Ready for Review" you are eligible to accept another. You can do as many tickets as you want, as long as you follow the rules above.
  • - If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked "Accepted".
  • - When the ticket is closed, payment will be recorded, and ticket tagged "Paid".
  • - You should always pull from the main trunk at the start of the ticket to keep in sync.
  • - Once a fix is accepted, a corresponding payment will be created through JIRA and the ticket marked "Paid".
  • - If an assigned task is not done in 24 hours, you will need to explain why it is not completed as a comment otherwise your ticket will be opened up back to the community.
  • - You can ask questions directly on the ticket comments.

ANYONE NOT FOLLOWING THE RULES ABOVE WILL BE WARNED AND POTENTIALLY LOSE THEIR REPOSITORY ACCESS

ELIGIBLE EVENTS:

2016 TopCoder(R) Open

Review style

Final Review

Community Review Board

Approval

User Sign-Off

ID: 30051273