Ystari is developed and maintained by a global development team composed of volunteers. We welcome your help!
- Make sure you have a GitHub account
- We suggest this online course on contributing to OSS projects on GitHub
- Review the Code of Conduct
- Submit a ticket for your issue, assuming one does not already exist
- Fork the repository on GitHub
- Create a topic branch from where you want to base your work.
- This is usually based off the master branch.
- Only target release branches if you are certain your fix must be on that branch. Releases are typically in maintenance mode and accept only critical bug fixes. Check with the project owners before working on anything other than critical bug fixes.
- Create a branch in which to do your work. Please avoid working directly on the
masterbranch.
- Make commits of logical units.
- Make sure your commit messages are in the proper format.
#999 Make the example in CONTRIBUTING imperative and concrete
or
Fixes #999 Describe the change made in a concise manner
Closes #999 Describe the change made in a concise manner
- Make sure you have added the necessary tests for your changes.
- Print, sign, and email the contributor agreement document to Marimer LLC (rocky at lhotka dot net)
- We will not accept large changes without a signed contributor agreement, but we may accept small edits to the existing codebase
- By submitting a change, large or small, you grant ownership of the code and related IP to Marimer LLC, and you certify that you have the right to transfer such ownership
- Push your changes to a topic branch in your fork of the repository.
- Submit a pull request to the repository in the Marimer LLC organization.
- Update your GitHub issue to mark that you have submitted code and are ready for it to be reviewed.
- Include a link to the pull request in the ticket