AsyncAPI open meeting, Tuesday Jan 19 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. (Leave a comment below to add your item to the agenda)
3. Google Summer of Code (@derberg )
4. Q&A

Notes

agenda

• main coding focus for the next cycle is data model generation as a feature in the AsyncAPI generator to speed up and ease templates development (Fran Mendez)
• we want to apply for Google Summer of Code. We have 2 mentors that are willing to support people that will be accepted (and of course if we will be accepted).
  We work on the list of ideas that participants could work on. What kind of cool tools they could build for AsyncAPI community. And of course, we would love to work on the list of ideas with you. This google doc is opened for edit for anyone with the link, please feel free to suggest anything, and put your name so we know how to contact you in case we need to ask more questions to actually understand the idea.
  We need to have the list completed by the end of this month, so there is still a lot of time. Thanks in advance (Lukasz Gornicki)

general discussion

• is it spec or tools project? (Clemens Vasters)
• it is both because we want to have reference implementation vendor-independent (Lukasz Gornicki)
• FM we do a lot of code but not much on spec. But thanks to Postman partnership we can now work on both on a good level. We will have 2 separate committees, one for spec, another for tools (Fran Mendez)
• I asks because of licensing, that specs should be licensed differently than code (Clemens Vasters)
• said OASIS seems better than LF because of ready processes. Better to become ISO standard (Clemens Vasters)
• ISO is not a hard requirement atm (Fran Mendez)
• what is the feedback from others, what do you need from AsyncAPI (Fran Mendez)
• I want more corporate diversity and technology diversity because of the complexity of AsyncAPI (Lorna Mitchell)
• I want clearance of the status of the project, where the project is, what licenses are, clear all legal concerns. In private it is not important, but for production for companies, it is crucial. We need a clear process and roadmap not only for code but spec too. Make it transparent and remove concerns that it is just Postman thingy. (Zoltan Simon)
• my main priority atm is AsyncAPI in the foundation (Fran Mendez)
• my main priority atm is research on the best open governance model for AsyncAPI (Lukasz Gornicki)
• I recommend community folder in cloud events as a reference for the good governance model (Clemens Vasters)

Chat dump
00:06:25 Fran Méndez: brb
00:09:45 Lukasz Gornicki: #432
00:18:52 Maciej Urbańczyk: https://github.com/asyncapi/shape-up-process/issues there are issues in current cycle :)
00:19:08 Fran Méndez: https://shapeup.asyncapi.io/cycles/6301193
00:22:45 Lukasz Gornicki: https://docs.google.com/document/d/11g0ezAvrZGRYhe5NEV4fOq4zAnLQPmOow0egxgSokUs/edit?usp=sharing
00:57:30 Fran Méndez: https://github.com/cloudevents/spec/blob/v1.0.1/community/GOVERNANCE.md
01:00:04 Clemens Vasters: https://github.com/cloudevents/spec/blob/v1.0.1/primer.md#qualifying-protocols-and-encodings
01:04:26 Lukasz Gornicki: asyncapi/shape-up-process#38

Recording

https://youtu.be/14I-l-TCgI4