Welcome to the AsyncAPI Initiative! Our mission is to improve the current state of Event-Driven Architectures (EDAs) and the tooling ecosystem around them. Join us in shaping the future of how you work with Event-Driven Architectures.
We set annual community goals that guide our growth and initiatives every year. Join us as we enhance maintainers' support, simplify onboarding, and establish structured community initiatives and programs.
Find all the resources you need to start contributing to our organization.
-
Follow the Code of Conduct and help keep the community inclusive and respectful.
-
Read the Contribution Guide and learn how to contribute effectively.
-
Explore the Community Contribution Onboarding Docs, a step-by-step guide for new contributors.
-
Follow the AsyncAPI Style Guide to ensure consistency across all docs.
Our community is steered by a transparent governance board. You can learn more about our Community Governance and the AsyncAPI Charter, which outlines the decision-making process, structure, responsibilities, and procedures for contributions and oversight of the AsyncAPI open project.
The TSC is a group of maintainers and Ambassadors responsible for the maintenance and decision-making of the AsyncAPI Initiative. It was formed to ensure open governance and neutrality.
- Read the requirements and responsibilities on becoming a TSC Member or watch our YouTube video on how to become a TSC member.
- Or explore if you meet the requirements of becoming an AsyncAPI Ambassador.
If you have any questions or need guidance, please reach out through our GitHub Discussions page or via Slack.
We invite you to join our Events & Meetings, and we hope to see you at one of the AsyncAPI Conferences.
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
The AsyncAPI Community repository includes extensive automation powered by custom scripts. To ensure these scripts function correctly, proper testing is essential. This section explains how to run existing tests and how to add new ones.
We use Jest for testing automation scripts. To run the tests locally, follow these steps:
- Install dependencies:
npm install
- Run all tests:
npm test
If you are contributing new automation scripts, ensure they are covered by tests. To add a new test:
- Create or update the relevant test file in the
test/
directory. - Follow the existing Jest structure for consistency.
- Ensure your test covers edge cases and different scenarios.
- Run the tests locally before pushing your changes.
All contributions to automation should include proper test coverage to maintain reliability.