*This is a first draft for review, please submit any feedback =) *
We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
Reporting a bug
Discussing the current state of the code
Submitting a fix
Proposing new features
Becoming a maintainer
We use CODESYS Forge to host code, to track issues & feature requests.
Since CODESYS IDE is currently only using SVN, Pull Requests (PR's) are a bit of an issue currently.
Every code should be checked before submission:
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
We use Tickets to track public bugs. Report a bug by opening a new ticket; it's that easy!
Great Bug Reports tend to have:
By contributing, you agree that your contributions will be licensed under its MIT License.
This document was adapted from briandk's excellent contribution guidelines template.
Diff:
Diff:
Diff:
License agreement appears twice under "License" and "Any contributions you make will be under the MIT Software License"
"Unhook" might need to be Untick.
How does someone without SVN write access submit their code? as attachment in the forge ticket?
Should they have further questions about contribution, are we actually really excited about answering such questions? and if so how should they ask?
Other than these questions, I think it is very good and may encourage some contributors.
Diff:
Sold
See root of SVN Repo