-
-
Notifications
You must be signed in to change notification settings - Fork 100
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 UTC Wednesday February 2 2022 #250
Comments
Zoom link to join -> https://us02web.zoom.us/j/9840447370 |
Agenda
Notes
Recording |
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. |
Thanks for the heads up, Jonas, I can quickly mention the issues that I am championing.
[photo]
Jesse Menning
CTO Architect
Phone: (734) 717-9147
Solace.com<https://solace.com/>
From: Jonas Lagoni ***@***.***>
Sent: Wednesday, February 2, 2022 3:42 AM
To: asyncapi/community ***@***.***>
Cc: Jesse Menning ***@***.***>; Mention ***@***.***>
Subject: Re: [asyncapi/community] Spec 3.0 Meeting, 16 UTC Wednesday February 2 2022 (Issue #250)
Warning – this email originated outside of Solace. Please think before you click or open any links or attachments. If this email is suspicious, report it to ***@***.******@***.***>
…________________________________
I would like to start off the meeting with a recap of what I did after the last meeting (asyncapi/spec#691<asyncapi/spec#691>)
@jessemenning<https://github.com/jessemenning> do you want to quickly mention asyncapi/spec#690<asyncapi/spec#690>, asyncapi/spec#692<asyncapi/spec#692>, and asyncapi/spec#694<asyncapi/spec#694> or do you want me to do it?
@damaru-inc<https://github.com/damaru-inc> do you want to quickly mention asyncapi/spec#697<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<asyncapi/spec#628> and asyncapi/spec#658<asyncapi/spec#658>.
—
Reply to this email directly, view it on GitHub<#250 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOZ3J4JTLR5QCNAIGNM7OYDUZDU5JANCNFSM5NGVFQIA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
________________________________
Confidentiality notice
This e-mail message and any attachment hereto contain confidential information which may be privileged and which is intended for the exclusive use of its addressee(s). If you receive this message in error, please inform sender immediately and destroy any copy thereof. Furthermore, any disclosure, distribution or copying of this message and/or any attachment hereto without the consent of the sender is strictly prohibited. Thank you.
|
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 When we will have a branch I will create PRs with changes for my two topics regarding Scheme Object. |
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
Notes
person@1.0.0
- @fmvilasneed-champion
label etc.- Make an issue on the website for kicking it off.
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
The text was updated successfully, but these errors were encountered: