Please create an account (it's free) and create your own personal fork of the project first
## 2. Checkout your own fork
Checkout your personal fork and modify the features/functions or add new ones.
## 3. Commit your code
Test your code in the experimental instance of VS and do a real deploy and test it under load.
Commit in your bug free tested code.
Create a new Branch and give it a nice name indicating your contribution.
Don't forget to add yourself as a Contributor and add your copyright notices as you seem fit. Remeber, you are not allowed to remove any copyrights or contributors, you are only allowed to add yourself as a contributor and only allowed copyrights on the original code that you write.
If you add code from other contributors or copyright holders, don't forget to add them as well.
## 4. Create a Merge Request
From your nice named branch into the correct branch in the main project.
Take a break and be a proud contributor.
## 5. Check your emails
In case the maintainer of the original project has questions or found problems.
If not, and your contribution is accepted, your code will be merged into the master project and you will live a happier life.
# Note on License
Please note that this code is under the MS-RL license. It requires all distributions of the software to also include the source code and it's license(s). This includes compiled DLL files, MSI Setup files or VSIX Packages, these are not allowed to be distributed without the source code and its license(s).
Please also note that the MS-RL allows for code to be added under a diffrent more strict license. However, you are not allowed to modify the license(s) of existing code.
If you wish to put your own contributions code under a diffrent license, please put the code in it's own file, and add a license note at the top as comments indicating under wich license(s) your code is governed. Failure to do so will put your code under the MS-RL license wich governs all files in this project unless stated otherwise in the file.
