AsyncAPI open meeting, Tuesday Mar 2 2021 4PM 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 4PM 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. Update from @dalelane about:
   • Describing schema usage in Kafka
     • docs: update Kafka bindings to describe schema usage bindings#55
     • examples
   • Defining security parameters for Kafka
     • docs: add essential Kafka client security parameters to bindings bindings#56
     • feat: add SASL security scheme types for use by Kafka specs #502
3. Vision of the project on PR by @fmvilas
4. Update on governance model by @derberg
5. Some updates in the templates world from @derberg (PHP and Go templates)
6. Q&A

Notes

• We got update from Dale on efforts:

  • to provide security schemes in the spec that are relevant for Kafka
  • to add server binding for Kafka

  (above, in the agenda you have links to PRs and examples)

• We had a discussion brought by Ian on the idea of bindings on a server in general. The current state is that spec describes the app and should have things that are necessary to identify how to connect to the app. In the case of the server, binding is to keep details about the broker needed for the app to connect, not the configuration details of the server so it can be used for infrastructure setup. This is a state for now, but nothing blocks us from changing it and we can discuss it in the asyncapi repo issues

• We also had a discussion brought by Lorna about the security details that should be in the spec. The current approach is that credentials should not be there. Through spec you should know that to connect to a broker you need user name and password, but you should not know what is the user name and password.

• Fran showed an initial preview of the project vision and roadmap. Have a look and share your feedback in the PR feat: add vision, goals, and roadmap website#189

• Lukasz shared that we finished working on the open governance model last week already. We are just waiting on the foundation's feedback and a green light if we can share it already with the community and work with the community and foundation in parallel on fixes in the charter. We will share charter as a PR to asyncapi repo + a blog post with the motivation behind it. The community will have 2 weeks to provide feedback.

• Lukasz shared that we have new template, PHP one, underdevelopment, donated by Emiliano that wants to work on it with the community

• Lukasz shared the work on Go continues after few months of stale. Jacob cannot continue but we merged his PR and Takumi with Emiliano want to continue with it forward.

Recording

https://youtu.be/NITAyTedR5c

[dalelane]

If there's interest in giving an update on the progress of these items, I'd be happy to give a quick summary:

• Describing schema usage in Kafka
  • docs: update Kafka bindings to describe schema usage bindings#55
  • examples
• Defining security parameters for Kafka
  • docs: add essential Kafka client security parameters to bindings bindings#56
  • feat: add SASL security scheme types for use by Kafka specs #502

[derberg]

@dalelane sure thing, this meeting is for the community, so if you only have time to do it then please do. I'll add it to the agenda!