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

August Newsletter #5 #782

Closed
thulieblack opened this issue Jul 4, 2023 · 7 comments
Closed

August Newsletter #5 #782

thulieblack opened this issue Jul 4, 2023 · 7 comments

Comments

@thulieblack
Copy link
Member

Have suggestions or content to include in our upcoming Newsletter?

We would like to hear from you! Do you have ideas on :

Updates, videos, articles, and podcasts related to AsyncAPI: Please share any favorite resources that would benefit the community!
Events you would like community members to know: Are there any upcoming events/conferences/talks related to AsyncAPI that interest the community? We'd love to hear about them.
Appreciation to a community member: Is there someone who has gone above and beyond to help others or contribute to AsyncAPI? Let us know so we can give them a shoutout.
The submission deadline will be on the 28th of July, 2023

@derberg
Copy link
Member

derberg commented Jul 4, 2023

from spec perspective there will be 2 things to announce. 2 New bindings:

  • jms - already merged in bindings repo
  • sqs/sns - almost merged

writing this comment just to remember, I can later write a paragraph about it for newsletter and blog

@alequetzalli
Copy link
Member

@thulieblack
Copy link
Member Author

writing this comment just to remember I can later write a paragraph about it for the newsletter and blog

@derberg, it's time 👆🏿👆🏿

@AnimeshKumar923
Copy link
Contributor

I have a question. Does the August newsletter contains events happened in July?

@derberg
Copy link
Member

derberg commented Jul 26, 2023

Input for blog and newsletter:

Bindings for JMS, SQS and SNS are here

We released initial versions for three bindings that till now did not have any specification:

Huge thanks to large involvement of different community members in review of the incoming changes ❤️

@thulieblack
Copy link
Member Author

@AnimeshKumar923 yes it does

@thulieblack
Copy link
Member Author

Closing this issue as I'm working on the issue. see y'all in #824

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

No branches or pull requests

4 participants