recurring spec meeting
- Dominant language
- JavaScript
- Stars
- 5.3k
- Forks
- 382
- Avg merge
- 7m
- Merged PRs (30d)
- 4
Description
@dalelane @char0n @fmvilas @GreenRover
Hey folks, how about we start doing a monthly triage meeting to start working on the spec on a regular basis? One hour, once a month, to triage issues and push for new releases.
We could start in November - I can be the organizer to make sure it takes place, gets recorded, and stuff like that. Like doing a chair job.
We could push for https://github.com/asyncapi/spec/pull/1109 release in next window - January 2026
Contributor guide
Research direction
No source file, test, or implementation entry point is named. Read the issue discussion and the referenced spec release PR, then confirm that the recurring triage process, recording arrangement, and release planning have been established.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100