Skip to content
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, 15:00 UTC Thursday April 13th 2023 #649

Closed
asyncapi-bot opened this issue Mar 30, 2023 · 2 comments
Closed

Spec 3.0 Meeting, 15:00 UTC Thursday April 13th 2023 #649

asyncapi-bot opened this issue Mar 30, 2023 · 2 comments
Labels

Comments

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Mar 30, 2023

Meeting Info Details
Purpose This is the meeting for community member involved in works related to 3.0 release of AsyncAPI Specification.
Time 15: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. feat: new schema reference object to enable nonjson refs in future spec#917 - @derberg
  3. feat: allow defining schema format other than default spec#910 @GreenRover
  4. [3.0.0] Should we have messageId and name fields in Message Object? spec#862 Message id - @fmvilas
  5. Place for your topic
  6. Q&A

Notes

Add notes here after the meeting.

@derberg
Copy link
Member

derberg commented Apr 11, 2023

we need to talk about asyncapi/spec#917

@jonaslagoni
Copy link
Sponsor Member

@fmvilas want to move asyncapi/spec#862 to next meeting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants