Essential building blocks for AsyncAPI, 20:00 UTC Tuesday March 12th 2024

[asyncapi-bot]

Meeting Info	Details
Purpose	Initial call with to create alignment about creating essential building blocks for AsyncAPI
Time	20:00 UTC | Translate to your time zone with the time zone converter.
Meeting Place	Link
Zoom	Join live.
YouTube	Watch live and interact through live chat.
Twitch	Watch live.
Twitter	Watch live.
LinkedIn	Watch live.
More Info	Details
Meeting Recordings	YouTube Playlist.
AsyncAPI Initiative Calendar	Public URL.
iCal File	Add to your calendar.
Newsletter	Subscribe to get weekly updates on upcoming meetings.

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. Introduction
3. Figure out our goal for the working group
4. Figure out how we wanna structure the working group
5. Place for your topic
6. Q&A

Notes

Add notes here after the meeting.

[jonaslagoni]

Thanks for a great meeting @m-wild @lorenzsimon @VisualBean @Pakisan @Souvikns ✌️

The recording can be found here: https://www.youtube.com/watch?v=fic5PKFGG28

Recap from the meeting

Our understanding of what we are trying to do:

• Solving it together
• Similar tooling interface as when coming from OpenAPI
• Similar tooling experience across languages

Our understanding of fundamental building blocks:

• JSON Schema and validation is the same across languages
• Libraries that act as base cornerstones of implementation for other languages
• Editing and creating AsyncAPI documents, especially through Visual editors
• Enabling the same functionality for references across languages and generally working with references
• Serialization and deserialization of documents in languages
• Integration into frameworks
• Same quality for bindings

Things to consider going forward:

• Reaching out to consumers of building blocks such as for example backstage to get perspective and depth of problems currently being phased.

Questions to think about:

• How would it look like if we had no existing tooling what would the best developer experience look like? Which tooling would be available and where?

Agreements we had in the meeting:

• Using GitHub projects as our main tool for coordinating
• @jonaslagoni will act as chairman at least in the beginning
• Suggesting to move the meeting to 7 pm GMT+1 (or 6 pm)

Actionable items

• Using GitHub projects as our main tool for coordinating
• Suggesting to move the meeting a bit to 7 pm GMT+1 every week (at least here in the beginning).
• @jonaslagoni will act as chairman at least in the beginning
• @jonaslagoni is gonna create the initial official working group proposal
• @jonaslagoni is gonna set up the next meeting once we agree on a time and date as above.

Did I miss anything 🤔?

[jonaslagoni]

Suggesting to move the meeting a bit to 7 pm GMT+1 every week (at least here in the beginning).

@m-wild @lorenzsimon @VisualBean @Pakisan @Souvikns please have a look at the suggested meeting change and whether it fits everyone ✌️ I will create the next meeting as soon as we are aligned there.

As well as all the other actionable items to make sure you still agree with them 🤙

Regarding the next meeting, I would suggest that we discuss the following:

• Come up with a plan going forward for what specific problems we want to focus on first and have in mind for later.
• How do we figure out if what we do matters and improve things? Can we measure it somehow?

[jonaslagoni]

Created the initial working group suggestion #1098 please have a look when you get a spare minute.