Challenge Overview
Challenge Overview
The prizes shown on the challenge page are only for reference. The actual payout will be based on bugs fixed and payments will be issued instantly when a fix is accepted. We are expecting to add issues on a daily basis for the next one week so it's a good time to join this challenge!
Reliability Care is an Asset Reliability Centered business performance tool, specifically designed for Power grids and Substations asset reliability management. The aim of this project is to develop the Mobile application (iOS and Android) using Xamarin framework.
Now we have finished almost all functionalities requirements, there are some remaining issues, we need to clean them up in this challenge.
How It Works:
1. You need to be registered GitLab
2. Go to the GitLab repo: https://gitlab.com/abb-mobile-xamarin/abb-mobile.git, please work on the dev branch.
4. Please read this GitLab ticket rule. That's VERY Important for attending this bug bash challenge.
- Please use the following link to grant yourself access to the GitLab repo
- Please visit https://gitlab.com/abb-mobile-xamarin/abb-mobile/issues to pick up any issues.
5. Go to the issue list and find an issue you wish to work on. They will be labeled with tcx_OpenForPickup (Open for pickup). You can only work the issues with a label for "Open for pickup".
6. When you find an issue, assign the issue to yourself, and change the label to tcx_Assigned (Assigned). If you feel the issue amount is too low, please make a comment on the issue saying what you feel the dollar amount should be. If it's accepted by the copilot, upon review, the copilot will edit the issue to reflect the new amount.
7. Work the issue as normal, when you are done, change the label to tcx_ReadyForReview (Ready for review)
8. Once you mark the issue "Ready for review", a copilot will review the issue and change it's status appropriately. Once the issue is marked as tcx_FixAccepted (Fix accepted), the system will automatically pay you the dollar amount specified in the issue title.
Note to developers:
-
To start working on an issue ask in comments to assign the issue to you.
+ Start working on the issue without waiting to be assigned, your comment with an intention to work on the issue is enough. But make sure by reloading the page, that nobody asked to assign the issue before you.
+ After you've asked for the assignment time starts and the issue has to be completed and MR provided during 12 hours.
+ If you need more time to complete the issue, post a comment about the reason for it, otherwise, the ticket could be marked as open for pickup. -
If you don't want to finish the issue, please ask in the comments to unassign you from the issue.
+ Note, if some participants asked to unassign him from the issue, another participant can ask to assign the issue to him in comments and directly start working on it without waiting to be assigned. Also, in this case, it doesn't matter if the issue has label OPEN FOR PICK UP or not. -
You can work only on one issue at a time.
-
If you do not mark the issue as "Ready for review" within 24 hours, the issue will fall back to "Open for pickup" and anyone can pick the issue back up.
-
If you need more time to work on an issue, leave a comment on the issue you want to work on.
-
You need to fork https://gitlab.com/abb-mobile-xamarin/abb-mobile.git before start working, You have to assign issues and create a merge request to https://gitlab.com/abb-mobile-xamarin/abb-mobile.git dev branch for resolving issues.
-
When you submit the merge request, make another comment at the issue like "It's done and ready for review" or similar and provide a link to the PR. Follow the issue for the possible comments from the project team. You can now start working on the next ticket (no need to wait for the review to finish).
-
You'll be required to fix any merge conflicts before the change is reviewed and merged.