Contribution Guide + Code of Conduct (#83)

Author: qianl15

CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Code of Conduct
+As contributors and maintainers of the DBOS Documentation project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.
+
+## Our Standards
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language.
+* Being respectful of differing viewpoints and experiences.
+* Gracefully accepting constructive criticism.
+* Focusing on what is best for the community.
+* Showing empathy towards other community members.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances.
+* Trolling, insulting/derogatory comments, and personal or political attacks.
+* Public or private harassment.
+* Publishing others' private information, such as physical or electronic addresses, without explicit permission.
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+Our Responsibilities.
+* Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at 
+[email protected]. All complaints will be reviewed and investigated promptly and fairly.
+
+All project team members are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+Project maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+* 1st offense: Verbal warning
+* 2nd offense: Written warning
+* 3rd offense: Temporary ban
+* 4th offense: Permanent ban
+
+## Attribution
+This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# Contributing to DBOS-Docs
+
+Thank you for considering contributing to the DBOS Documentation. We welcome contributions from everyone, including bug fixes, feature enhancements, documentation improvements, or any other form of contribution.
+
+## How to Contribute
+
+To get started with DBOS-Docs, please read the [README](README.md).
+
+You can contribute in many ways. Some simple ways are:
+* Open issues to report any bugs, questions, concern with the SDK, samples or documentation.
+* Respond to issues with advice or suggestions.
+* Participate in discussions in our [Discord](https://discord.gg/fMwQjeW5zg) channel.
+* Contribute fixes and improvement to code, samples or documentation.
+
+### To contribute code, please follow these steps:
+
+1. Fork this github repository to your own account.
+
+2. Clone the forked repository to your local machine.
+
+3. Create a branch.
+
+4. Make the necessary change to code, samples or documentation.
+
+5. Commit the changes to your forked repository.
+
+6. Submit a pull request to this repository.
+In the PR description please include:
+* Description of the fix/feature.
+* Brief description of implementation.
+
+By submitting a pull request, you represent that you have the right to license your contribution to DBOS and the community, and agree by submitting the patch that your contributions are licensed under the MIT license.
+
+## Requesting features
+
+If you have a feature request or an idea for an enhancement, feel free to open an issue on GitHub. Describe the feature or enhancement you'd like to see and why it would be valuable. Discuss it with the community on the [Discord](https://discord.gg/fMwQjeW5zg) channel.
+
+## Discuss with the community
+
+If you are stuck, need help, or wondering if a certain contribution will be welcome, please ask! You can reach out to us on  [Discord](https://discord.gg/fMwQjeW5zg) or Github discussions.
+
+## Code of conduct
+
+It is important to us that contributing to DBOS will be a pleasant experience, if necessary, please refer to our [code of conduct](CODE_OF_CONDUCT.md) for participation guidelines.