Challenge Overview
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IMPORTANT ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Once assigned issues have to be completed and PR provided during 12 HOURS in this Bug Bash
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Context
Project Context
Topcode Connect is the client-facing application of Topcoder. Customers may create Topcoder projects there and Topcoder managers and copilots pick it up from there.
You may check out how the Topcoder Connect App looks like at https://connect.topcoder-dev.com using the demo users provided on the forum.
Challenge Context
We have some issues in Topcoder Connect App itself and in some other services related to Connect App like Project Service, Notification Service, Accounts App which we would like to fix.
In this challenge, you can pick up issues listed on GitHub and accomplish them during 12 hours to get the prizes that are mentioned in the issues titles. To participate in this challenge you would need to have an account on Topcoder and GitHub.
Expected Outcome
Fix issues we have in GitHub repository which are included in this challenge, see below.
Challenge Details
Technology Stack
-
ReactJs
-
Redux
-
CSS Modules
Individual requirements
Bug Bash Rules
In this challenge, we would use an experimental GitHub bot “@bug-bash-helper” that would help us to assign/unassign issues. If you have any issues with the bot, please, report on the “Challenge Forum”.
Pick Up Issue
You can pick up any open issue in the list below which has a label “Open for Pickup”:
-
to pick up an issue comment it with the next command for the bot:
“@bug-bash-helper assign” -
the bot should reply to you and assign you to the issue. If you didn’t get the reply in a few seconds, reload the page to make sure that bot assigned you to the issue
-
you can work only on one issue at a time
-
If you don’t want to finish the issue you may unassign the issue by adding the next comment
“@bug-bash-helper unassign”
Raise a Pull Request
Once assigned you have 12 hours to complete the issue and raise a pull request.
-
as soon as you’ve created a pull request add the next comment so the bot would mark the issue as “Ready for Review”:
“@bug-bash-helper <link to pull request> is ready for review” -
once the issue is marked for review you may pick up another issue. You don’t have to wait for the review to complete.
-
you'll be required to fix any merge conflicts before the pull request is reviewed and merged
-
if you need more time to complete the issue, create a Pull Request with name "[WIP] issue #<number of issue>" showing the work in progress and comment with a reason for time extension with link to the pull request, otherwise, you may be unassigned from the ticket and the ticket marked as open for pickup.
Address Feedback
If some issues are found in your pull request, the ticket would be marked with the label “Feedback” and review would be provided with an explanation of why the pull request has been rejected. If a fix is rejected, that ticket is your priority. You should not assign yourself any more tickets until you complete the required additional fixes!
Acceptance and Payment
If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked as "ACCEPTED". After the challenge is finished, payment will be recorded, and ticket tagged "PAID".
List of issues
See the list of the issues that are included in this challenge:
https://github.com/appirio-tech/connect-app/issues?q=is%3Aopen+is%3Aissue+label%3ACF
Pull Requests
Most issues should be fixed inside Connect App repository https://github.com/appirio-tech/connect-app/tree/cf-22 (branch "cf-22") or Project Service repository https://github.com/topcoder-platform/tc-project-service/tree/cf-22 (branch "cf-22").
-
For the Connect App and Project Service create pull requests against branch “cf-22”.
-
If pull request should be created for some other repository, we would mention which branch to use in the ticket description.
General requirements
For all the repositories:
-
Follow general code best practices.
-
Lint should pass (don’t disable eslint rules).
-
Existent unit tests should pass.
If you have any questions or issues with Bug Bash Bot, please, ask a question on the challenge forum.
Prizes
Please ignore the prize shown in this challenge, that is just the estimated purse from all the tickets.
For this Bug Bash, we will be paying per accepted fix based on the prize amount noted in each issues' title.
Scorecard Aid
-
Each of the fix would be reviwed by the reviwer or copilot.
-
Please, ask any question regarding the issues by commenting on the issues.
-
We expect that the root cause of the issue would be fixed instead of adding "hacky" code.
Final Submission Guidelines
-
Create pull requests to all the repositories which are required to fix the issue. Note, that you would have to fork the repository for creating a pull request. See how to create a pull request from a fork.
-
If you solved at least one issue, submit a text file with your Topcoder and GitHub user handle to process the payment.