Skip to content

feat: update contributing guidelines #1802

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

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

feat: update contributing guidelines #1802

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
95582d7
feat: update contributing guidelines
Souvikns Jun 15, 2025
abd454b
chore: add changeset for PR #1802
Jun 15, 2025
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
9 changes: 9 additions & 0 deletions .changeset/1802.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
'@asyncapi/cli': minor
---

feat: update contributing guidelines

- 95582d7: feat: update contributing guidelines


28 changes: 27 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,4 +76,30 @@ Happy contributing :heart:
When you submit changes, your submissions are understood to be under the same [Apache 2.0 License](https://github.com/asyncapi/asyncapi/blob/master/LICENSE) that covers the project. Feel free to [contact the maintainers](https://www.asyncapi.com/slack-invite) if that's a concern.

## References
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md).
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md).


## Maintainers

Maintainers are responsible for overseeing the project’s overall health and progress. Their duties include managing and assigning issues, reviewing pull requests, and ensuring consistent development.

The project is organized into distinct scopes, whith each maintainer assigned to one or more scopes they are resposible for managing and overseeing.

During triaging, maintainers are responsible for assigning scope labels to issues, ensuring they are directed to the appropriate maintainer for further investigation and action.

Maintainers are encouraged to hold weekly or bi-weekly meetings to engage with contributors and the community, providing updates on ongoing work and fostering collaboration around open issues.

As of now we are diving the project scope to:

- core
- commands
- docs
- server-api
- GitHub Actions
- ci/cd


## Contributors

If a contributor is assigned to an issue but doesn't start work or provide any updates within a week, they may be unassigned so the issue can be made available to others. While we don't expect contributors to complete the work within a week, claiming an issue and then going inactive without communication can hinder project progress.