Challenge Overview
Challenge Objectives
Fix a bunch of bugs/issues found during the bug hunt challenge
���Note: 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 following days so it's a good time to join this challenge!
Rules and How it works
1. You need to be registered GitLab
2. Request access to the repository in the forum
3. Go to the GitLab repo: https://gitlab.com/topcoderinc/marketing-site-3.0.git, please work on the dev branch. This challenge itself is created for outreach purposes only. All actions will be coordinated through this repo.
4. Copy the repo and set up a local environment of the wordpress site for your development
5. Select an issue labeled as _OPEN FOR PICKUP to work on from the repo. Don't pick-up multiple issues at the same time!
6. Self-assign yourself to the issue, remove the _OPEN FOR PICKUP, and add the _IN PROGRESS label (if you don't have enough permissions to do this, ask in the issue ticket itself).
7. Fork any repositories related to the issue, follow the instructions in the ticket, work from the latest commit in the develop branch. Provide access to quesks to your forked repos.
8. Once ready, create a merge request, and label the original issue ticket with the _READY FOR REVIEW label.
9. From this moment you may pick-up the next issue and start working on it, but if any problems are detected with your previous pull request, fixing them will be the top priority.
10. Don't hold an issue ticket for too much time if you can't fix it in 24 hours. If an issue demands more time to be fixed, comment in the ticket, otherwise un-assign yourself from the ticket and label it back with the _OPEN FOR PICKUP label.
11. If you have any questions regarding a ticket, comment in the ticket itself and don’t use the challenge forums. Use the challenge forum only for generic questions or to ask for access to the repos.
12. If changes in the backend are required to fix a ticket, please comment on the ticket and make sure to mention the copilot (@quesks)
Payment
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.
Final Submission Guidelines
Submissions will be done in the form of pull requests to the relevant repositories. Please clearly mention in the title of your commits and MRs the ID of issues they are fixing, and briefly tell in body of commit/MR comments, what exactly have been done, and how it can be tested.
IMPORTANT NOTE: In order for your fixes to be counted, you must upload a dummy submission to this challenge. Please submit a zipped up txt file that contains your Gitlab username.