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
##Code of Conduct ObjectTalk has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy! Great bug reports tend to have:
- A quick summary and/or background
- Steps to reproduce (be specific and give sample code if you can)
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
master. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
All contributions must be in the same style as the rest of ObjectTalk.
By contributing, you agree that your contributions will be licensed under its MIT License.