AsyncAPI v3 retrospective about spec HOT 1 CLOSED

Full video recording here: https://www.youtube.com/watch?v=lV6t-S2C5Yo

Here are the core points from the retrospective:

1. More maintainers are needed to push the effort both from the spec side and tooling
2. Too much to coordinate for a single release coordinator, needs to be split up in some way
3. Lack of ownership in tools to update them to new major versions, similar to the first point
4. The learning curve for contributing to the spec is way too steep and needs mentoring or other form of support structure
5. Huge win that we actually released it in the end 🎉
6. We need to figure out a way for the release process NOT to stall such as changing the release process, smaller release cycle, etc.

If I missed anything @fmvilas @peter-rr @smoya @AceTheCreator please comment below so I can add it to the summary list 👍

Lastly, @fmvilas mentioned the possibility of a brand new release process for the spec, so this retrospective and introducing the changes are now up to you folks @fmvilas @derberg @dalelane @smoya @char0n @GreenRover whether to improve what is there or directly start the conversation about a new process. The GitHub issue is still TBDT.

from spec.