Challenge Overview
Detailed Requirements
Welcome to Lets App - NodeJS Lambda [Bug Bounty] Challenge!
The goal of this challenge is to fix a number of issues in the AWS Backend.
A [Bug Bounty] 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 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 significant.
Challenge Scope
This challenge will remain open until all bugs are closed/solved. This will remain open for 30 days.
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.
- 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 file in the repo.
Bug values
1pt = $25
Each bug will have a point value in the title, the point represents the prize of the bug where 1pt = $25.
The competitor can select any open bug to work on. Once you have the fixed the bug, please submit link to pull request and the corresponding issue number to Online Review, we will review it and pay you the total points you earned when the F2F challenge ends in Online Review.
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 $100 bonus to the member who collect the largest number of points.
Bug Bounty Instructions
- You can get access to the Gitlab repo group by a tool posted in forums.
- You can view list of issues here https://gitlab.com/lets-platform/aws-backend/issues
- Issues valid for this project are labeled with Open For Pickup.
- Issue that are not labeled with OPEN FOR PICKUP are not eligible for the bug bounty.
- Each issue in Gitlab issue has a point value. Point values are based upon complexity and priority of issue.
- You can assign any unassigned issue to yourself with an "Open for Pickup" (first come first serve). Update label to “In Progress”, and remove the “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 "master" 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.
- If your solution is broken, fixing the ticket should be your HIGH priority, you are not allowed to take any other tickets.
- 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 "Solution Accepted".
- When the ticket is closed, payment will be recorded, and processed in Online Review when F2F is finished.
- You should always pull from the latest version of the 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.
- You can ask questions directly on the ticket comments.
Submission Deliverable
For each ticket you fix, upload text file with link to Gitlab pull request to Online Review.