Challenge Overview
Welcome to the Project Bauern Salesforce.com Lightning Prototype build. We're running this project via git repo tickets so register to gain repo access and pick up a ticket! We're going to be building this one super fast! So expect some good prizes on the tickets.
REPOSITORY RULES (PLEASE NOTE THE BRANCH REQUIREMENT!)
Each ticket in GitLab has a dollar value. Dollar values are based upon complexity and priority of issue.
You can assign any unassigned issue to yourself with an "_OPEN FOR PICKUP" label (first come first serve). Remove the "_OPEN FOR PICKUP" label once you have done so.
You can only assign ONE AT A TIME.
Create a new branch in your forked repository for each ticket and do a merge request against the "develop" branch when ready for review. Be sure to pull the latest updates from the upstream develop branch before working on your changes! Grant harrywynn Reporter access to your fork.
Once a ticket is fixed, you should label it "_READY FOR REVIEW" where it will then be verified. If something is still broken, the copilot/architect will comment on the ticket.
After submitting and tagging "_READY FOR REVIEW" you are eligible to accept another. You can do as many tickets as you want, as long as you follow the rules above.
If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked "_ACCEPTED".
When the ticket is closed, payment will be recorded, and ticket tagged "_PAID".
You should always pull from the main trunk at the start of the ticket to keep in sync.
Once a fix is accepted, a corresponding payment will be created through Topcoder Direct Tasks and ticket marked "_PAID".
If an assigned task is not done in 24 hours, you will need to explain why it is not completed as a comment otherwise your ticket will be opened up back to the community.
You can ask questions directly on the ticket comments.
ANYONE NOT FOLLOWING THE RULES ABOVE WILL BE WARNED AND POTENTIALLY LOSE THEIR REPOSITORY ACCESS
Final Submission Guidelines
Submissions will be accepted as merge requests on the repositoryREPOSITORY RULES (PLEASE NOTE THE BRANCH REQUIREMENT!)
Each ticket in GitLab has a dollar value. Dollar values are based upon complexity and priority of issue.
You can assign any unassigned issue to yourself with an "_OPEN FOR PICKUP" label (first come first serve). Remove the "_OPEN FOR PICKUP" label once you have done so.
You can only assign ONE AT A TIME.
Create a new branch in your forked repository for each ticket and do a merge request against the "develop" branch when ready for review. Be sure to pull the latest updates from the upstream develop branch before working on your changes! Grant harrywynn Reporter access to your fork.
Once a ticket is fixed, you should label it "_READY FOR REVIEW" where it will then be verified. If something is still broken, the copilot/architect will comment on the ticket.
After submitting and tagging "_READY FOR REVIEW" you are eligible to accept another. You can do as many tickets as you want, as long as you follow the rules above.
If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked "_ACCEPTED".
When the ticket is closed, payment will be recorded, and ticket tagged "_PAID".
You should always pull from the main trunk at the start of the ticket to keep in sync.
Once a fix is accepted, a corresponding payment will be created through Topcoder Direct Tasks and ticket marked "_PAID".
If an assigned task is not done in 24 hours, you will need to explain why it is not completed as a comment otherwise your ticket will be opened up back to the community.
You can ask questions directly on the ticket comments.
ANYONE NOT FOLLOWING THE RULES ABOVE WILL BE WARNED AND POTENTIALLY LOSE THEIR REPOSITORY ACCESS