My GSoC Experience with AsyncAPI
summary
Summer work as a GSoC contributor turns into co-maintaining the generator repository, handling issue triage, PR review, roadmap decisions and cross-team announcements. A feature request no override globs is opened Feb 22 and closed July 30 — five months mostly spent on design discussion, only days of coding. Reviewed a PR adding nonack filters, dug into changed JS to prevent regressions, and set up processes for who opens PRs and how marketing gets release notices. Technical JS skill, clear communication and reliable execution are required.
AI-written summary · about
chapters (7)
- 0:00GSoC and AsyncAPI intro
- 3:00Joining GSoC with AsyncAPI
- 4:49Life as AsyncAPI maintainer
- 9:26Maintainer responsibilities
- 11:37Open source success skills
- 13:44Get involved in AsyncAPI
- 15:11Q&A
related talks
22mHow Contributing to AsyncAPI Tools Inspired a Career in OSS- 22mHow Contributing to AsyncAPI Tools Inspired a Career in OSS
30mEmbracing uncertainties My Journey as an Open Source Contributor
18mGetting Started with Open-Source Contributions: A Beginner's Guide
25mFor the Love of Go: How to Contribute Really
26mFrom 9-to-5 to Pull Requests: Sustainable Open Source Contribution
46m503 days working full time on FOSS: lessons learned
24mLightning Talks Part Three