How to contribute to AsyncAPI specification
summary
Contribution follows explicit stages — strawman, proposal, draft and accept — with required reference implementations in the AsyncAPI JSON Schema and the parser; changes often take months (one proposal moves from April to September). The project favors favor no change and simplicity, asks for concrete use cases and prefers pull requests over issues; every RFC needs a champion to drive reviews, address comments and coordinate tool updates. Releases happen quarterly and release coordination is volunteer-run.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:45Why you should contribute
- 5:58Contribution Guide
- 9:21Request for Change
- 12:24Strowman
- 14:48Real life
- 17:03Community engagement
- 18:37Release
related talks
08mMy Journey from Contributor to a TSC Member at AsyncAPI
27mAsyncAPI & The future of API specs- 08mMy Journey from Contributor to a TSC Member at AsyncAPI
13mEverything You Wish To Know About The AsyncAPI Community
22mHow Contributing to AsyncAPI Tools Inspired a Career in OSS
25mEverything You Wish To Know About The AsyncAPI Comunity
25mThe State of AsyncAPI Initiative
26mPast, Present, and Future of AsyncAPI