Challenge Overview
The prizes shown on the challenge page are only for reference. The actual payout will be based on bugs fixed and payments will be issued instantly when a fix is accepted.
Challenge Overview
Our Redis Manager is almost complete! We have a few more features we need to add, but first we need to knock out some bugs. This bug bash will be using our self-service assignment & payment tool. My magnificent crowd, there are so many (113!!) issues that are open! There are easy issues that are great for new developers to more complex issuess for our experienced folks!
Final Submission Guidelines
How It Works:
- You need to be registered Github
- Use this link to add yourself to the Github Team: https://x.topcoder.com/api/v1/github/teams/registration/00d48f1e-ac66-4a3c-8ed4-ada7b743c5e3-1545426953171
- After you use the link, be sure to check your email for the invitation to join the Github team -- You’ll need to do this before completing the steps below.
- Go to the appropriate GitHub repo: https://github.com/topcoderinc/tc-redis-manager
- Go to the issue list and find an issue you wish to work. They will be labeled with: tcx_OpenForPickup (Open for pickup). You can only work the issues with a label for “Open for pickup”.
- When you find an issue, assign the issue to yourself, and change the label to tcx_Assigned (Assigned).
- Dollar values are based on complexity and/or urgency.
- If you feel the issue amount is too low, please make a comment on the issue saying what you feel the dollar amount should be. If it's accepted by the copilot, upon review, the copilot will edit the issue to reflect the new amount.
- You can only self assign one issue at a time. The nature of it being assigned will indicate if it is not available to anyone else.
- You will submit the fix as a pull request to the master branch
- Work the issue as normal, when you are done, change the label to tcx_ReadyForReview (Ready for review)
- If the ticket is “tcx_Feedback”, it should be your first priority to fix the issue.
- When the ticket is closed, payment will be recorded, when we issue the payment the tag will be updated to “tcx_Paid”
- If an assigned task is not done in 24 hours, you will be unassigned from the ticket, and it will be opened back up to the community.
- You can ask questions directly on the ticket comments.
- Bug Bashes are different than Bug Hunts - please make sure to check the contest type in the contest name when registering.
- If you do not mark the issue as “Ready for review” within 24 hours, the issue will fall back to “Open for pickup” and anyone can pick the issue back up.
- If you need more time to work on an issue, leave a comment on the issue you want to work.
Submission Flow
- First, make sure your "develop" branch is ALWAYS UPDATED! We will be pushing new code updates in parallel.
- Fork our repository
- Once you are satisfied with your fixes, you should label it "tcx_ReadyForReview.
- Add the issue number you were working on in the Merge Request description.
- If something is still broken, the Reviewer will comment on the ticket. We will update the label as " tcx_Feedback" and you can complete the fixes based on the feedback.
Final Submission Guidelines
Send merge requests for the fixed bugs
Technology Stack
Frontend
- Angular 7
- Angular Material https://material.angular.io/
- Material Icons https://material.io/tools/icons/?style=baseline
- ioredis https://github.com/luin/ioredis
- Hapi.js
- NodeJS