Challenge Overview
Welcome to FAYA Bug Bash Sprint 2 Challenge!
We have a Java API backend, and Angular 2.0 App frontend. The goal of this challenge is to do API-UI integration and di Fixes to the API or Frontend code.
A [Bug Bash] challenge is a program that will pay community members to fix issues 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 than an hour to diagnose and fix. And we have other changes that are more significant.
For this challenge, you will assign an issue that has corresponding complexity level (each level has corresponding money amount as outlined below) to yourself from our current list of Gitlab issues.
- Add yourself to the gitlab repo.
- 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 README in the repo.
The competitor can select any open issue to work on. For your challenge submission, you need to create a text file that includes your gitlab username and submit it to Online Review. You don't need to submit the links to the issues you fixed, we have a script to track them.
Open issues shown here are in scope of this challenge and will be designed by the "Open for Pickup" and "bug-bash-sprints" tags. The issue list will be updated frequently, new issues will be shown and old issues may be fixed by the other competitors, some issues depend on other issues, so we will also open them once the dependencies are resolved. So keep watching the issues list.
- You can view list of issues here https://gitlab.com/sancus-community/backend/issues
- Each issue in Gitlab issue 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).
- Change Label from “Open for Pickup” to "In Progress" once you assign yourself. If you want to back away change the label to “Open for Pickup” and unassign yourself.
- 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 merge request to the "bug-bash-sprints" 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, and change it back to "In Progress" and add "Final Fixes" label.
- 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 merge request will be merged in, and the ticket will be marked "Solution Accepted".
- You should always pull from the bug-bash-sprints branch at the start of the ticket to keep in sync.
- If an assigned task is not done in 24 hours, you will be unassigned from the ticket, and it will be open up to the community. If you need more time than 24hrs make sure to post a comment in the ticket otherwise you will lose your right to complete the ticket.
- You can ask questions directly on the issue comments section.
- AngularJS 2.0
- Oracle 11g express
- Tomcat
- Spring
Backend : https://gitlab.com/sancus-community/backend
Frontend: https://gitlab.com/sancus-community/frontend
We have a Java API backend, and Angular 2.0 App frontend. The goal of this challenge is to do API-UI integration and di Fixes to the API or Frontend code.
A [Bug Bash] challenge is a program that will pay community members to fix issues 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 than an hour to diagnose and fix. And we have other changes that are more significant.
Prize Note
Prizes shown in the challenge details is just a placeholder, each member will be paid the total amount of $$ earned by that member for solving the gitlab issues.Challenge Scope
This challenge will last for 5 days, we may add more issues to the scope (we will stop including any new issues 24hrs prior to the challenge deadline), if we add more issues we will post in challenge forums to notify you.For this challenge, you will assign an issue that has corresponding complexity level (each level has corresponding money amount as outlined below) to yourself from our current list of Gitlab issues.
- Add yourself to the gitlab repo.
- 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 README in the repo.
Bug values
Each bug has a weight assigned to it, default weight value : 1 = $10, 2 = $20 .. 9 = $90. If the ticket has a price in square brackets it overrides the default prize.The competitor can select any open issue to work on. For your challenge submission, you need to create a text file that includes your gitlab username and submit it to Online Review. You don't need to submit the links to the issues you fixed, we have a script to track them.
Open issues shown here are in scope of this challenge and will be designed by the "Open for Pickup" and "bug-bash-sprints" tags. The issue list will be updated frequently, new issues will be shown and old issues may be fixed by the other competitors, some issues depend on other issues, so we will also open them once the dependencies are resolved. So keep watching the issues list.
Bug Bash Instructions
- You can get access to the Gitlab repo group from challenge forums.- You can view list of issues here https://gitlab.com/sancus-community/backend/issues
- Each issue in Gitlab issue 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).
- Change Label from “Open for Pickup” to "In Progress" once you assign yourself. If you want to back away change the label to “Open for Pickup” and unassign yourself.
- 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 merge request to the "bug-bash-sprints" 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, and change it back to "In Progress" and add "Final Fixes" label.
- 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 merge request will be merged in, and the ticket will be marked "Solution Accepted".
- You should always pull from the bug-bash-sprints branch at the start of the ticket to keep in sync.
- If an assigned task is not done in 24 hours, you will be unassigned from the ticket, and it will be open up to the community. If you need more time than 24hrs make sure to post a comment in the ticket otherwise you will lose your right to complete the ticket.
- You can ask questions directly on the issue comments section.
Platforms
- Java 8- AngularJS 2.0
- Oracle 11g express
- Tomcat
- Spring
Gitlab Repositories
(You get access to this from challenge forums)Backend : https://gitlab.com/sancus-community/backend
Frontend: https://gitlab.com/sancus-community/frontend