AsyncAPI open meeting, Tuesday Mar 16 2021 8AM UTC

[derberg]

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

Agenda

Don't wait for the meeting to discuss topics that already have issues. Feel free to comment on them earlier.

1. Q&A
2. Just some updates
3. Q&A

Notes

• Again some new faces joined the meeting 💪🏼
• There was a question on how to get along with bindings not requiring JSON Schema and therefore not being validated by the parser. We pointed to this issue from Maciej [RFC] Support JSON Schema for bindings spec#507 and explained that this project has to be simply driven forward and pushed into the spec as other changes. So far everyone agrees this is a very useful addition. First, we need to change the spec and then get tools (like parser) to adopt it.
• We discussed what are the next big changes that may trigger 3.0 release. First of all, we learned that Fran is going to have a baby and will go for parental leave for a couple of months (congrats mate!). There are 2 big issues with the spec that should be solved and will trigger 3.0 (dunno when), it is: channels reusability and semantics of publish/subscribe operation that is confusing to people. Once someone finds a good way how to accomplish this, we will release 3.0 for sure. Related issue [2.0.0 REVIEW] Reusing channel definitions across files is hard spec#415 and Add a View property to the info section to change the perspective of subscribe and publish operations. spec#390. We discussed in detail the current challenge with the spec.
• We updated the community with some things that happen currently:
  • proposal on how to introduce changes in the spec in organized way chore: improve contributing guidelines spec#511
  • discussion on release cadence Define a release cadence spec#513
  • asyncapi repo is now spec and stuff like this meeting agenda are now under community repo
  • blog post about February at AsyncAPI https://www.asyncapi.com/blog/february-2021-at-asyncapi
  • remember we wait for feedback on open governance until 23rd of March

Recording

https://youtu.be/r5hLFnqY8D4
tbd