The goal of this challenge is to fix a number of issues in the HPE WCS Android app, Admin Tool and the backend.

A [Bug Bash] challenge is a program that will pay community members to fix bugs reported.

Using Github 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.

Challenge Scope

This challenge will remain open until all bugs are closed/solved. This will remain open for 7 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 Github issues.

- Access request in forums to the repo

- Browse the issues labeled ‘ready for bug bash round 2’ + 'Enhancement Round 2' 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 the app can be found in the README file in the repo.

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 20 pts ($100)

The competitor can select any open bug to work on. Once you have the fixed the bug, please submit link to pull request and assign it to ‘nithyaasworld’

Open Bugs shown here are in scope of this challenge and will be designed by the "ready for bug bash round 2" + 'Enhancement Round 2' 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 $100 bonus to the member who collect the largest number of points.

Bug Bash Instructions

 

- Each issue in Github 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 "ready for bug bash round 2" (first come first serve). Update label to “In Progress”, and remove “ready for bug bash round 2” 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.

- 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”

- If an assigned task is not done in 8 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.