Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: update contributing #1998

Merged
merged 1 commit into from
Apr 14, 2023
Merged

docs: update contributing #1998

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,18 @@
# Contributing

Hello, welcome to the OpenDAL Community! This document will guide you on how to participate in our community and enjoy your time here.
Hello, welcome to the OpenDAL Community! Thanks for your interest in the Apache OpenDAL project! This document will guide you on how to participate in our community and enjoy your time here.

## Code of Conduct

We expect all community members to follow our [Code of Conduct](https://www.apache.org/foundation/policies/conduct.html).

## Communication

We use [GitHub Discussions](https://github.com/apache/incubator-opendal/discussions) for general discussions and questions. Please use the `Q&A` category for questions and the `General` category for general discussions.

We also use [GitHub Issues](https://github.com/apache/incubator-opendal/issues) for bug reports and feature requests.

Otherwise, you can join our [Discord Channel](https://discord.gg/XQy8yGR2dg) for real-time discussions.

## Taking Issues

Expand All @@ -14,6 +26,9 @@ By removing the assignment, we create space for other community members to take

## Sending PRs

If you find an issue you would like to fix, open a pull request. For code changes, please refer to the particular component's development guide.

We will try our best to review your PRs within 24 hours, and often within 8 hours.

If a PR does not receive a response within 24 hours, it will be converted to draft status. To indicate that you are ready for review, please mark the PR as `ready for review`.