-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spec 3.0 Meeting, 16:00 UTC Wednesday June 22nd 2022 #394
Comments
I can't make it to the meeting tomorrow. I know that my proposal is important so I would not wait with it until the next 3.0 meeting but make another one on Friday, or possibly next week. |
@magicmatatjahu we can take a poke at it tomorrow, and take it up again at the next meeting if you find it necessary, how does that sound? Creating another 3.0 meeting with that short notice might not make much sense, and if we are talking next week, then we are already close to the original next meeting date anyway 🙂 |
You can see the PR, but I can't present it tomorrow. We can also move it to the next meeting and you will have time to discuss about another topics. |
yes, we should not schedule meetings for the same week as there is not time for community to prepare |
Recording is out: https://www.youtube.com/watch?v=wKoibKtaiqU |
Alright, created the issue so you can give feedback: asyncapi/spec#811. I'm updating the notes above too. |
Agenda
Notes
chore: extend Schema Object to allow defining custom formats spec#797
schemaFormat
on v2.x once we have 3.0.0 out.customSchema
needed?AsyncAPI Domain Specification
OpenAPI support at AsyncAPI
The text was updated successfully, but these errors were encountered: