Challenge Overview
We’re building a modern and intuitive web application that helps to provide a platform which enables users to:
-
Select a factory
-
View factory dashboards with KPIs
-
View project summaries
-
View project dashboards
The goal of this challenge is to fix a number of issues in the Angular frontend and Java backend.
So far, we have leveraged the Topcoder community and launched multiple challenges to build the Angular app and the Java backend earlier this year. We now need to speed up the remaining development and fix the issues identified in both the Angular app and the Java backend.
A [Bug Bash] challenge is a program that will pay community members to fix bugs reported.
Using Gitlab issues you will assign issues to yourself. In this [Bug Bash] this issue vary widely in scope. Some are small cosmetic changes that shouldn't require more 5 minutes to diagnose and fix. And we have other changes that are more significant. Some fixes may require both frontend and backend changes - in that case you will need to raise pull requests for both repos.
Challenge Scope
This challenge will remain open until all bugs are closed/solved. For this challenge, you will assign a bug that has corresponding complexity level (each level has corresponding point value as outlined below) to yourself from our current list of Gitlab issues.
- Access request in forums to the frontend and backend repos
- Browse the issues labeled ‘Open for Pickup’ 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 Bash will be managed.
- Deployment instructions for both frontend and backend can be found in respective repos. Additional backend information is available in the docs folder including Swagger file, original architecture documents, API to screen mapping documents etc.
BUG VALUES
Weight: 1pt = $5
Each issue will have a weight assigned, the weight represents the prize of the bug where 1pt = $5. Issues have weights from 1 pt ($5) to 100 pts ($500)
The competitor can select any open bug to work on. Once you have the fixed the bug, please submit a pull request to develop branch (for app or backend repo) and assign it to talesforce.
Open Bugs shown here are in scope of this challenge and will be designed by the "Open for Pickup"tags. 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 bonus of $400 and $200 respectively to the top two submitters (most number of points for issues fixed). The bonus will only be paid if the top two submitters have fixed bugs at least worth 100 points, else they’ll get only the payment for only bug value fixed.
Bug Bash Instructions
- Each issue in Gitlab issue has a weight value. Weight values are based upon complexity and priority of issue.
- You can assign any unassigned issue to yourself with a "Open for Pickup" (first come first serve). Update label to “In Progress”, and remove “Open for Pickup” label.
- 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 develop branch!
- 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 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 "Fix Accepted".
- If the ticket is rejected, it should be your first priority to fix the issue.
- When the ticket is closed, payment will be recorded, and ticket tagged "Payment Required", when we issue the payment the tag will be updated to “Paid”
- If an assigned task is not done in 12 hours, you will be unassigned from the ticket, and it will be open up to the community.
- You can ask questions directly on the ticket comments. We have a QA resource - Nithya who'll be able to help reproduce any issues.