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.

Sign up for GitHub

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

Jump to bottom

Spec 3.0 Meeting, 16 UTC Wednesday February 2 2022 #250

Closed
asyncapi-bot opened this issue Jan 31, 2022 · 5 comments
Closed

Spec 3.0 Meeting, 16 UTC Wednesday February 2 2022 #250

asyncapi-bot opened this issue Jan 31, 2022 · 5 comments
Labels
meeting

Comments

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Jan 31, 2022 •
edited by derberg
Loading

This is the meeting for community member involved in works related to 3.0 release of AsyncAPI Specification.

The meeting takes place bi-weekly on Wednesdays. First and third week every month until release. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 16 UTC

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar. You can also check AsyncAPI Calendar.

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 on Introduce Schema Versioning spec#697 - @damaru-inc
  3. Update on Work on 3.0 release spec#691 - @jonaslagoni
  4. Update on Increase frequency of Spec 3.0 meeting from biweekly to weekly spec#690, Use Version 3 milestone to triage potential inclusions in AsyncAPI version 3 spec#692, and Introduce data format bindings spec#694 - @jessemenning
  5. Starting branches - @magicmatatjahu
  6. How to start engaging in discussion around The many meanings of an AsyncAPI file spec#628 and Defining a collection of applications  spec#658 - @jonaslagoni
  7. Place for your topic
  8. Q&A

Notes

  1. Question about pub/sub confusion and status from @anandsunderraman (discussed later)
  2. Questions about how to handle schema version
    • Should be compliant with existing schema registries (adding it to the issue) - @fmvilas
    • How do you handle reusability for versions? (adding it to the issue) - Abir
    • Under schema name you could do something like [email protected] - @fmvilas
  3. No questions
  4. No questions
  5. We need to create new branches for next-major for spec-json-schema, spec, parser-js, generator. @derberg will handle it in a couple of days.
  6. Points to keep in mind for a discussion:
    • Ping people directly.
    • Search through slack to find the people that are interested.
    • Wait for a response and then make a decision.
    • Ping @derberg for social media.
    • Prepare keypoints/topics to spark discussions.
    • Make similar to contributor first discussions.
  7. Other questions:

Chat

17:06:49 From Abir | @imabptweets : sorry cannot turn on the camera... I am actually out of station for this week..in a hotel..
17:10:00 From Abir | @imabptweets : yeah the second picture of versioning is not so maintainable. I feel
17:15:23 From Fran Méndez : Noted on the issue already.
17:16:06 From Abir | @imabptweets : having bit connection issues... I wanted to say... the schema should be more integrable and maintainable... probably need to think from that perspective..
17:16:19 From Lukasz Gornicki To Jonas Lagoni(privately) : I know how to do live stream next time! Yay!
17:17:50 From Jonas Lagoni To Lukasz Gornicki(privately) : Cool! xD
17:18:34 From Jonas Lagoni : Abir, do you mind adding your thoughts about the schema reusability between versions in the issue?
17:18:52 From Abir | @imabptweets : Sure I will add it.
17:23:42 From Fran Méndez : I’m writing down my thoughts in the issue
17:24:22 From Jonas Lagoni : asyncapi/spec#691
17:26:11 From Jonas Lagoni : asyncapi/spec#694
17:29:04 From Michael Davis : I’ve got to leave now, bye!
17:45:10 From Jesse Menning : Anand, where did you get the photo of GoT?
17:45:38 From Anand Sunderraman : I used to work for HBO, so they had a throne in the office !!
17:48:15 From Jonas Lagoni : https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md

Recording

tbd
@derberg
Copy link
Member

derberg commented Jan 31, 2022

Zoom link to join -> https://us02web.zoom.us/j/9840447370

@jonaslagoni
Copy link
Member

jonaslagoni commented Jan 31, 2022 •
edited
Loading

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 on Introduce Schema Versioning spec#697 - @damaru-inc
  3. Update on Work on 3.0 release spec#691 - @jonaslagoni
  4. Update on Increase frequency of Spec 3.0 meeting from biweekly to weekly spec#690, Use Version 3 milestone to triage potential inclusions in AsyncAPI version 3 spec#692, and Introduce data format bindings spec#694 - @jessemenning
  5. Starting branches - @magicmatatjahu
  6. How to start engaging in discussion around The many meanings of an AsyncAPI file spec#628 and Defining a collection of applications  spec#658 - @jonaslagoni
  7. Place for your topic
  8. Q&A

Notes

  1. Question about pub/sub confusion and status from @anandsunderraman (discussed later)
  2. Questions about how to handle schema version
    • Should be compliant with existing schema registries (adding it to the issue) - @fmvilas
    • How do you handle reusability for versions? (adding it to the issue) - Abir
    • Under schema name you could do something like [email protected] - @fmvilas
  3. No questions
  4. No questions
  5. We need to create new branches for next-major for spec-json-schema, spec, parser-js, generator. @derberg will handle it in a couple of days.
  6. Points to keep in mind for a discussion:
    • Ping people directly.
    • Search through slack to find the people that are interested.
    • Wait for a response and then make a decision.
    • Ping @derberg for social media.
    • Prepare keypoints/topics to spark discussions.
    • Make similar to contributor first discussions.
  7. Other questions:

Recording

https://youtu.be/sK5eAJtScAo

@jonaslagoni jonaslagoni mentioned this issue Feb 2, 2022
Closed
@jonaslagoni
Copy link
Member

jonaslagoni commented Feb 2, 2022 •
edited
Loading

I would like to give a recap of what I did after the last meeting (asyncapi/spec#691)

@jessemenning do you want to quickly mention asyncapi/spec#690, asyncapi/spec#692, and asyncapi/spec#694 or do you want me to do it?

@damaru-inc do you want to quickly mention asyncapi/spec#697 or do you want me to do it?

After updates, I would like to get some thoughts about how to set up a discussion around asyncapi/spec#628 and asyncapi/spec#658.

@jessemenning
Copy link

jessemenning commented Feb 2, 2022 via email

@magicmatatjahu
Copy link
Member

I will come to the meeting, but from my side I have nothing new, only that I gave a suggestion to create a separate branch on the repository @asyncapi/spec for example next-major and start creating PRs with the changes and start discussion there and not on issues because I noticed that on issues sometimes there is no activity.

When we will have a branch I will create PRs with changes for my two topics regarding Scheme Object.

@jonaslagoni jonaslagoni mentioned this issue Feb 2, 2022
Closed
@derberg derberg closed this as completed Feb 3, 2022
@jonaslagoni jonaslagoni mentioned this issue Feb 3, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@derberg @jonaslagoni @magicmatatjahu @asyncapi-bot @jessemenning