Current Development Branch:  dev
mtwomey edited this page on Dec 24, 2014 · 12 revisions

Rules for Fixing Bugs (Issues)

IE11 is the primary browser used for the application. Please make sure to test all fixes against this browser.

  1. All eligible tasks / issues will be labeled “Up For Grabs” You can assign any unassigned issues with this label to yourself (first come first serve)
  2. You can only assign yourself ONE issue at a time. We will monitor this and take away tasks if you do not comply
  3. If you cannot complete the task within 24 hours, add a comment to it as to why, or it will go back to unassigned
  4. Each task / issue will have points allocated to it which will translate to prizes

Process for Resolving Bugs (Issues)

  1. Remove the "Up For Grabs" label from the Issue and assign it to yourself
  2. Create a branch off the Current Development Branch (see the top of this page)
  3. git checkout -b [YOUR-USERNAME]-issue-[ISSUE#] [CURRENT DEVELOPMENT BRANCH]
  4. for example git checkout -b mtwomey-issue-22 dev
  5. Please make sure you are branching off the correct development branch and not master!
  6. Do your work on this branch
  7. Do frequent pulls of the Current Development Branch if you're working the issue for more than a few hours
  8. git pull --rebase origin [CURRENT DEVELOPMENT BRANCH]
  9. Once you finish the task
  10. Commit your changes
  11. Do a final git pull --rebase origin [CURRENT DEVELOPMENT BRANCH] to make sure nothing has changed that affects your fixes
  12. Push your branch to GitHub
  13. git push origin [BRANCH NAME]
  14. Add the "Ready for Review" label to the Issue
  15. Create a pull request for your branch to the Current Development Branch
  16. Start your next issue!

Tips

Point System

1 point = $25 and will be paid weekly

The tasks are geared to be small in scope and completed quickly. Some may take longer than others but in general should be less than a day.