Challenge Overview
Detailed Requirements
Welcome to Thunderbird [Bug Bounty] Challenge!
The goal of this challenge is to fix a number of issues in the iOS app and a java 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.
Challenge Scope
This challenge will remain open until all bugs are closed/solved. This will remain open until we fix all issues.
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 (information in forums).
- 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
Bug Severity : Bug Hunt Value
------------------------------------------
P1 - Blocker : $ 200
P2 - Critical : $100
P3 - Major : $50
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.
How to Join
1. Go to This Tool and enter your GitLab username to join the project group (you should have done this already to see this page)
2. Once you are added, you will receive an email to confirm you joined the project group.
3. iPad app gitlab repo is (use develop branch) : https://gitlab.com/tc-thunderbird/frontend
4. java app backend repo is (use develop branch): https://gitlab.com/tc-thunderbird/backend
Bug Bounty Instructions
- You can view list of issues here https://gitlab.com/tc-thunderbird/frontend/issues
- Issues valid for this project are labeled with OPEN FOR PICKUP
- 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 “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 and push your fix in a new branch (name it after the issue ticket number i.e. Issue_1) and then create merge 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 "Solution 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”
- You should always pull from the develop 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.