Step 1 - View the issue
View the issue by clicking on the issue description. Login to Jira using your TopCoder handle and password. You will not see all the functionality available if you are not logged in.
The payment amount is displayed in the description. Please note the due date of the issue prior to deciding to work on it.
You can subscribe to the RSS feed using any RSS reader to get updates when new issues are posted. The title in the table is the link to the RSS feed.
Step 2 - Register to fix the issue
From the detail page of the issue click Vote (located in the left nav). This will be how you register to work on the issue. Multiple people can register (vote) for the same issue. The first person to attach a correct solution for the issue will win the prize amount.
The concept of voting in Jira is being used as a temporary registration process until a full registration process is integrated. When you "vote" on a issue we will assume you are registering to work on the issue and submit a fix. If you do not intend on submitting a fix please do not vote on the issue.
Step 3 - Download the source code
- The issue details will direct you to the appropriate source code and documentation to download.
- If the issue is found in a component in our catalog you will find a link to the specific component in the catalog.
Step 4 - Work on the issue
Work on the issue in your local environment. Follow the guidelines for designing and developing components to ensure the integrity of the component is maintained.
- The fix must include updated test cases and documentation in accordance with the component design and development rules. Include a description of your fix as a comment when attaching your file.
Step 5 - Ask questions
Ask questions by posting comments on the details page of the specific issue you are working on.
Step 6 - Submit your solution
Use the Attach File link in the left nav of the issue tracking system to submit your fix. Create a zip file of the entire source distribution that the fix involves. For example, if the fix is for a component then submit a zip of the entire component distribution in the same format you downloaded. Note: Attachments are visible to anybody viewing the issue.
Step 7 - Review
Reviews will be completed by members or TopCoder staff (or both). If a member review is to be done, the issue description will include a prize payment for not only the issue fixer but also for the reviewer. The review payment will go to the reviewer of the first submission to pass. Once a passing review is completed, the Bug Race™ Competition is over (unless re-opened by TC staff).
Member reviews must follow the format described below.
- Submissions must be reviewed in the order they are received. If a reviewer has already submitted a review for the first submission, it is acceptable for another reviewer to begin reviewing the second submission without looking at the first one.
- Reviewers should leave a comment on the issue when they begin a review to notify others that they are reviewing the fixes.
- The reviewer must download and apply the fix, rebuild the code, run the tests and complete a simple README file to document whether documentation, diagrams, comments, etc. were appropriately updated (until Online Review can be used and we can use an actual scorecard).
- The reviewer will zip up the following review deliverables and post a comment with the zip file attached to submit the review: a successful build log, a successful test-run log, the rebuilt component/code binary (jar, dll) and the README file containing Yes/No answers with short explanations to the questions listed below.
- The first complete review submission that ends the Bug Race Competition (a passing review) will receive the reviewer payment. Fraudulent review submissions may subject the member to penalties including loss of payment or temporary or permanent ban.
Include the following text in the review README along with Yes, No or n/a answers as well as brief descriptions justifying the answer.
- The submission compiles successfully.
- The submission passes all tests successfully.
- The submission corrects all of the issues indicated in the issue description.
- The changes adhere to the TopCoder development guidelines.
- Code comments are updated appropriately.
- Design documentation is updated appropriately.
- Design diagrams are updated appropriately.
- The submission passes review. ("Yes" if and only if all other questions are "Yes" or "n/a")
Step 8 - Receive Payment
Payment will be awarded for first place. The payment amount is noted in the issue description. Review payments are also noted in the issue description if applicable.