No responsibility for any financial or other damage.
People contributing to the project are unpaid. It's an entirely volunteer effort. No money is made from this application currently (and there are no plans for this to change).
This application is Open Source Software. The software license is MIT.
- Read through the README File of the application.
- If things are unclear, please contact me at [email protected]
- Code reviews
- Check the issue list to see if there are any issues marked with help wanted
- Fork the repo (if you haven't already done so).
- Clone it to your computer. You can do it using
git clone url_name. - When you're ready to work on an issue, be sure you're on the master branch(Check using
git branch). From there, create a separate branch. You can do this usinggit checkout -b branch_namewhere branch_name (e.g. issue_32) is the name of a new branch that you create. - Make your changes. Save the file. Go to the command line and do
git add file_nameto add it to the staging area. - Commit your changes. Do this using
git commit -m "comment about the changes made". - Push the working branch (e.g. issue_32) to your remote fork. This is done using
git push origin branch_name. - Make the pull request (on the upstream master branch)
- Do not merge it with the master branch on your fork. That would result in multiple, or unrelated patches being included in a single PR.
- If any further changes need to be made, comments will be made on the pull request.
If you're unsure of some details while you're making edits, you can comment on the issue, or drop an email at [email protected] .
It's possible to work on two or more different patches (and therefore multiple branches) at one time, but it's recommended that beginners only work on one patch at a time.