In hopes of speeding up MW development, I'm going to start offering EX bounties for fixing smaller bugs while the development team tackles things like feature additions.
Send me a PM with your coding credentials and email address. You don't have to be a coding wizard, but you will need at least a basic understanding of Git, along with HTML, CSS, PHP, and/or JavaScript, depending on the task. If you can demonstrate knowledge of one or more of these languages, I'll add you to the GitLab development team, allowing you access to the codebase.
1. Never commit or merge code to the master branch. This branch is synced with the server, meaning any commits to it go live immediately. Instead, make a new branch when starting a fix - once it's tested working, I'll merge it to master.
2. Never make code changes that are unrelated to the bug at hand. I will monitor each committed file for unauthorized changes.
3. Do not start working on a fix without first claiming it in this thread. Whoever is the first to claim a bug will be the only one who is eligible to claim the bounty, unless they give up.
4. If you spend longer than 14 days trying to fix a bug and you can't show any evidence of progress, the bug will be reopened for someone else to claim.
5. If you successfully fix a bug, but the awarded bounty pushes you past the 10,000 EX limit, you may claim the remainder at any later date.
Rules 1 and 2 are the most important by far. If you break one of those and it wasn't an honest mistake, you will no longer be eligible for this offer. These guidelines have to be more strict than our behavioral rules, since this is the codebase we're talking about.
See the below post for the list of completed, in-progress, and open bugs.
HOW TO APPLY
Send me a PM with your coding credentials and email address. You don't have to be a coding wizard, but you will need at least a basic understanding of Git, along with HTML, CSS, PHP, and/or JavaScript, depending on the task. If you can demonstrate knowledge of one or more of these languages, I'll add you to the GitLab development team, allowing you access to the codebase.
RULES
1. Never commit or merge code to the master branch. This branch is synced with the server, meaning any commits to it go live immediately. Instead, make a new branch when starting a fix - once it's tested working, I'll merge it to master.
2. Never make code changes that are unrelated to the bug at hand. I will monitor each committed file for unauthorized changes.
3. Do not start working on a fix without first claiming it in this thread. Whoever is the first to claim a bug will be the only one who is eligible to claim the bounty, unless they give up.
4. If you spend longer than 14 days trying to fix a bug and you can't show any evidence of progress, the bug will be reopened for someone else to claim.
5. If you successfully fix a bug, but the awarded bounty pushes you past the 10,000 EX limit, you may claim the remainder at any later date.
Rules 1 and 2 are the most important by far. If you break one of those and it wasn't an honest mistake, you will no longer be eligible for this offer. These guidelines have to be more strict than our behavioral rules, since this is the codebase we're talking about.
See the below post for the list of completed, in-progress, and open bugs.
![[Image: supercorrect.png]](https://i.ibb.co/g3J0P4F/supercorrect.png)
