Challenge Overview
Welcome to the IBM Castle - AngularJS Responsive UI [Bug Bounty] Challenge
The goal of this challenge is to fix a number of User Interface and Responsive (Mobile, Tablet, Desktop) issues for the IBM Castle UI Prototype.
This Bug Bounty can contain updates to AngularJS, HTML, CSS, Images with a key focus on fixing Responsive Issues.
A [Bug Bounty] Challenge is a task-based challenge format that will pay Topcoder Community Members to fix reported UI and Responsive bugs within our ongoing development GitLab repository. A [Bug Bounty] Challenge is different then aFirst2Finish Challenge in that you use GitLab Issues to assign issues to yourself.
In this [Bug Bounty] the issues vary widely in scope. Some are small cosmetic changes that shouldn't require more than an hour to diagnose while others require more extensive testing across mobile, tablet and desktop environments.
Challenge Scope
We need to update and fix UI/Responsive issues within our Castle AngularJS Application. We have a list of UI/Responsive Issues in GitLab and will continue adding issues over the next week. This challenge will remain open until all bugs are closed/solved, or we announce the challenge is closed in the Challenge Forum.
Multiple ways to win money!
- Claim an issue and fix it! (win the prize money associated with that issue)
- Fix the most issues (win the overall Bug Bounty Challenge)
- As part of winning a placement in the Bug Bounty you will also earn more money as part of the IBM Castle Blitz Program (works similar to the old Topcoder Digital Run)
- We have 3 winner placement for this challenge!
GitLab Links
- AngularJS Application Repository as base updates for this [Bug Bounty]: https://gitlab.com/ibm-castle/api/issues (Use angular-upgrade branch)
- AngularJS Application [Bug Bounty] Isssues List: https://gitlab.com/ibm-castle/api/issues?scope=all&sort=id_desc&state=opened&utf8=%E2%9C%93&milestone_title=Responsive+UI&label_name[]=RESPONSIVE+BOUNTY+ (Milestone: "Responsive UI" and label "RESPONSIVE BOUNTY" )
- UI Prototype Repository as reference for correct look and feel: https://gitlab.com/ibm-castle/ui/tree/develop
- You can deploy the application locally. Please find the instructions here or READ of the GitLab Repo.
Issues/Bugs
- Open Bugs shown here are in scope of this challenge and will be designated by the "BUG BASH - Open for Pickup" tag.
- The bug list will be updated frequently, we will be adding new bugs and closing bugs that you and other competitors fix. Make sure to keep watching the GitLab list.
- The winner(s) of the challenge will be the members who resolve the largest number of issues.
Bug Bounty Instructions
- Post your GitLab username in the challenge forum if you do not have access to our code yet.
- Each issue in Gitlab issue has a dollar value in the title. Dollar values are based upon complexity and priority of issue.
- You can assign any unassigned issue to yourself as long as it has the "BUG BASH - Open for Pickup" label (first come first serve).
- DO NOT taken ticket if already assigned to other user.
- You can only assign yourself ONE AT A TIME. The nature of it being assigned will indicate it is not available to anyone else.
- Change Label from “BUG BASH - Open for Pickup" to "BUG BASH - In Progress" once you assign yourself. If you want to drop an issue, comment as to why in the comment, then re-add the “BUG BASH - Open for Pickup”, remove "BUG BASH - In Progress" and unassign yourself.
- You can only assign yourself ONE AT A TIME. The nature of it being assigned will indicate it is not available to anyone else.
- After submitting a merge request and labeling it "BUG BASH - 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 "BUG BASH - Solution Accepted".
- When the ticket is closed, payment will be recorded. When we issue the payment the tag will be updated to “Paid”. Payments will be paid in one lump at the end of the F2F.
- If you have issue with the amount of time expected or the dollar amount of an issue, please ask in the comments of that issue first, before claiming the issue.
- If an assigned task is not done within 24 hours of assignment, you will be unassigned from the ticket, and it will be opened back 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 ticket comments.
Gitlab Flow From Start to Submit
- First, make sure your "angular-upgrade" branch ALWAYS UPDATED! We keep push some updates in parallel.
- CREATE NEW BRANCH based on our latest "angular-upgrade" branch with this title format "responsive/YourTCUsername/XX" where XX is number of issue ticket. And then do the fixes based on the specified branch.
- DO NOT FORK into your own repo. you MUST create from our "angular-upgrade" branch. We'll reject your submission if you submit from your own repo.
- Start working your updates in that branch, commit and push to your working repo.
- Once you satisfied with your fixes, you should label it "BUG BASH - Ready for Review". Then you'll need send MERGE REQUEST to "angular-upgrade".
- Put Ticket url/Ticket # you working on Merge Request description.
- If something is still broken, the reviewer will comment on the ticket. We'll update the label into "BUG BASH - In Progress" and you do more fixes based on feedback.
CODE RULES
- DO NOT make INDENTATION AND SPACE changes. Please focus on completing challenge Tasks. We need your code easy to see the differences.
- DO NOT DELETE EXISTING FILES/LIBRARY. Confirm with us if needed.
- RE-TEST AND COMPARE ON DESKTOP/TABLET/MOBILE SCREEN SIZE before you submit.
- That you actually fixed the issue
- That you did not create any other apparent issues with your fix
- That you followed coding style, conventions, and best practices
The reviewer, copilot, or PM can reject a merge request, or unassign a member for any reason they see fit, although they will give reason in the comments.
When this Bug Bounty round is over, we will post in the forum. You will be expected to Upload a text file to Online Review with the link to the Gitlab merge request of issues that are Accepted.
The goal of this challenge is to fix a number of User Interface and Responsive (Mobile, Tablet, Desktop) issues for the IBM Castle UI Prototype.
This Bug Bounty can contain updates to AngularJS, HTML, CSS, Images with a key focus on fixing Responsive Issues.
A [Bug Bounty] Challenge is a task-based challenge format that will pay Topcoder Community Members to fix reported UI and Responsive bugs within our ongoing development GitLab repository. A [Bug Bounty] Challenge is different then aFirst2Finish Challenge in that you use GitLab Issues to assign issues to yourself.
In this [Bug Bounty] the issues vary widely in scope. Some are small cosmetic changes that shouldn't require more than an hour to diagnose while others require more extensive testing across mobile, tablet and desktop environments.
Challenge Scope
We need to update and fix UI/Responsive issues within our Castle AngularJS Application. We have a list of UI/Responsive Issues in GitLab and will continue adding issues over the next week. This challenge will remain open until all bugs are closed/solved, or we announce the challenge is closed in the Challenge Forum.
Multiple ways to win money!
- Claim an issue and fix it! (win the prize money associated with that issue)
- Fix the most issues (win the overall Bug Bounty Challenge)
- As part of winning a placement in the Bug Bounty you will also earn more money as part of the IBM Castle Blitz Program (works similar to the old Topcoder Digital Run)
- We have 3 winner placement for this challenge!
GitLab Links
- AngularJS Application Repository as base updates for this [Bug Bounty]: https://gitlab.com/ibm-castle/api/issues (Use angular-upgrade branch)
- AngularJS Application [Bug Bounty] Isssues List: https://gitlab.com/ibm-castle/api/issues?scope=all&sort=id_desc&state=opened&utf8=%E2%9C%93&milestone_title=Responsive+UI&label_name[]=RESPONSIVE+BOUNTY+ (Milestone: "Responsive UI" and label "RESPONSIVE BOUNTY" )
- UI Prototype Repository as reference for correct look and feel: https://gitlab.com/ibm-castle/ui/tree/develop
- You can deploy the application locally. Please find the instructions here or READ of the GitLab Repo.
Issues/Bugs
- Open Bugs shown here are in scope of this challenge and will be designated by the "BUG BASH - Open for Pickup" tag.
- The bug list will be updated frequently, we will be adding new bugs and closing bugs that you and other competitors fix. Make sure to keep watching the GitLab list.
- The winner(s) of the challenge will be the members who resolve the largest number of issues.
Bug Bounty Instructions
- Post your GitLab username in the challenge forum if you do not have access to our code yet.
- Each issue in Gitlab issue has a dollar value in the title. Dollar values are based upon complexity and priority of issue.
- You can assign any unassigned issue to yourself as long as it has the "BUG BASH - Open for Pickup" label (first come first serve).
- DO NOT taken ticket if already assigned to other user.
- You can only assign yourself ONE AT A TIME. The nature of it being assigned will indicate it is not available to anyone else.
- Change Label from “BUG BASH - Open for Pickup" to "BUG BASH - In Progress" once you assign yourself. If you want to drop an issue, comment as to why in the comment, then re-add the “BUG BASH - Open for Pickup”, remove "BUG BASH - In Progress" and unassign yourself.
- You can only assign yourself ONE AT A TIME. The nature of it being assigned will indicate it is not available to anyone else.
- After submitting a merge request and labeling it "BUG BASH - 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 "BUG BASH - Solution Accepted".
- When the ticket is closed, payment will be recorded. When we issue the payment the tag will be updated to “Paid”. Payments will be paid in one lump at the end of the F2F.
- If you have issue with the amount of time expected or the dollar amount of an issue, please ask in the comments of that issue first, before claiming the issue.
- If an assigned task is not done within 24 hours of assignment, you will be unassigned from the ticket, and it will be opened back 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 ticket comments.
Gitlab Flow From Start to Submit
- First, make sure your "angular-upgrade" branch ALWAYS UPDATED! We keep push some updates in parallel.
- CREATE NEW BRANCH based on our latest "angular-upgrade" branch with this title format "responsive/YourTCUsername/XX" where XX is number of issue ticket. And then do the fixes based on the specified branch.
- DO NOT FORK into your own repo. you MUST create from our "angular-upgrade" branch. We'll reject your submission if you submit from your own repo.
- Start working your updates in that branch, commit and push to your working repo.
- Once you satisfied with your fixes, you should label it "BUG BASH - Ready for Review". Then you'll need send MERGE REQUEST to "angular-upgrade".
- Put Ticket url/Ticket # you working on Merge Request description.
- If something is still broken, the reviewer will comment on the ticket. We'll update the label into "BUG BASH - In Progress" and you do more fixes based on feedback.
CODE RULES
- DO NOT make INDENTATION AND SPACE changes. Please focus on completing challenge Tasks. We need your code easy to see the differences.
- DO NOT DELETE EXISTING FILES/LIBRARY. Confirm with us if needed.
- RE-TEST AND COMPARE ON DESKTOP/TABLET/MOBILE SCREEN SIZE before you submit.
Final Submission Guidelines
We will have a reviewer reviewing merge requests. They will be reviewing:- That you actually fixed the issue
- That you did not create any other apparent issues with your fix
- That you followed coding style, conventions, and best practices
The reviewer, copilot, or PM can reject a merge request, or unassign a member for any reason they see fit, although they will give reason in the comments.
When this Bug Bounty round is over, we will post in the forum. You will be expected to Upload a text file to Online Review with the link to the Gitlab merge request of issues that are Accepted.