Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
Open Job Description is under active development. We're releasing this because we'd like your feedback and participation as we move forward, together, in defining and implementing a specification that solves the problems in the space. We know that, as currently specified, Open Job Description is not a cure-all for any and all workflows.
- Discussions: We encourage you to post about what you would like to see in future revisions of the specification, share, and brag about how you are using Open Job Description, and engage with us and the community.
- Request for Comment: This repository exists because we want your comments on the specification. Please consider submitting an RFC if you have thoughts on how the specification could be improved.
- Issues: We encourage you to use the GitHub issue tracker to report bugs.
- Pull Requests: We welcome pull requests to improve the wiki documentation and add sample templates. Simply make your changes in our GitHub Repository and post a pull request.
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.
We welcome you to use the GitHub issue tracker to report any issues that you encounter with the documentation provided in this repository. When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already reported the issue.
We have provided an RFC ("Request for Comment") process for proposing changes to the specification. RFCs can be created by anyone in the community, and is the process that the Open Job Description team uses to propose changes. If you have an idea, a kernel of an idea, a problem to solve, or want to provide your point of view on proposals then we encourage you to engage in this process.
See the RFC Process README for information on this process.
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
- You are working against the latest source on the mainline branch.
- You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
- You open an issue to discuss any significant work - we would hate for your time to be wasted.
To send us a pull request, please:
- Fork the repository.
- Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, then it will be hard for us to focus on your change.
- Commit to your fork using clear commit messages.
- Send us a pull request, answering any default questions in the pull request interface.
- Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
GitHub provides additional documentation on forking a repository and creating a pull request.
Looking at the existing issues is a great way to find something to contribute on.
This project has adopted the Amazon Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
We take all security reports seriously. When we receive such reports, we will investigate and subsequently address any potential vulnerabilities as quickly as possible. If you discover a potential security issue in this project, please notify AWS/Amazon Security via our vulnerability reporting page or directly via email to AWS Security. Please do not create a public GitHub issue in this project.
See the LICENSE file for our project's licensing. We will also ask you to confirm the licensing of your contribution.