asyncapi / community Goto Github PK

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. Q&A

Notes

Hackathon and Conference update

• Hackathon is almost over:
  • 5 submissions so far -> https://github.com/asyncapi/community/discussions/categories/asyncapi-hack-2021-submissions
  • you can still volunteer as a submissions reviewer -> #71
• Conference talks are selected:
  • email notifications to CfP submitters are out
  • schedule prep in the process - plan is to publish this week
  • sponsored marketing to kick off next week. Anyone that would like to be "actively" involved here, like linked in setup, texts for media - you are all welcomed
• Just join #events channel in Slack

Other topics

• We had an interesting discussion about the purpose of AsyncAPI file. If you are interested with just this one, skip first 15min

Chat

10:12:39 From Lukasz Gornicki : https://github.com/asyncapi/community/discussions/categories/asyncapi-hack-2021-submissions
10:12:59 From Lukasz Gornicki : #71
10:29:51 From Nic Townsend : Apologies, I have to drop. Will catch the rest of this discussion on the replay 🙂
10:31:17 From Sergio Moya : asyncapi/spec#618
10:32:53 From Fran Mendez : Collection
10:41:23 From Fran Mendez : asyncapi/spec#628
10:41:28 From David Boyne : thanks
10:45:30 From David Boyne : https://github.com/asyncapi/event-gateway
10:47:52 From Lukasz Gornicki : meeting
10:48:43 From George : Thank you all, consider my itch scratched ;)

Recording

https://youtu.be/91LxtkZAvCQ

The purpose of this meeting is to focus on contributors, focus on people that want to contribute to AsyncAPI Initiative but do not know how to do it. AsyncAPI Initiative is a large project, with lots of code, lots of docs, and many many other areas that need help, but it is not easy to start.

Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM 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.

This meatin is a live-stream that goes to the following social media:

• YouTube
• Twitch
• Twitter
• LinkedIn

To broadcast the live-stream, we are using Restream. You are invited to join us live on the call and not only interact through chats on YouTube and Twitch.

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. Q&A

Notes

The meeting was focused purely on AsyncAPI Hackathon and Conference organization. As a result:

• We start a discussion on the budget for the event #56
• We start a discussion on sponsor tiers #58
• We definitely want to do something that we did not do last year - event registration. The event is for free but we want to fix what was a problem last year, that we did not know how event marketing converted into an actual event participants list + had no way to follow up with folks afterward.
• We need to check if it is possible using Bevy platform to have RSVP for the event with a special "box" that lets people decide if they want to be engaged with (bothered 😄 ) by the conference sponsors after the event.
• We do testing of Bevy next three days starting from Wednesday:
  • Wednesday 5PM CEST
  • Thursday 4PM CEST
  • Friday 11AM CEST
  • Join the event. Help us with testing and share your experience -> https://community.linuxfoundation.org/events/details/lfhq-asyncapi-initiative-presents-coffee-with-asyncapi-community/

All other discussions can be found here -> https://github.com/asyncapi/community/discussions/categories/asyncapi-hack-conf-2021-organization

Chat

00:05:43 Lukasz Gornicki: https://www.asyncapi.com/blog/events2021
00:12:10 Lukasz Gornicki: https://community.linuxfoundation.org/events/details/lfhq-asyncapi-initiative-presents-coffee-with-asyncapi-community/
00:18:32 Sergio Moya Campaña: Related discussion about Marketing for the cons and hackaton: #47
00:18:46 Sergio Moya Campaña: conf*
00:24:43 _acebuild: Putting it publicly would be a great idea IMO
00:28:40 _acebuild: The conf is free right?
00:29:10 _acebuild: What about personal people that want to contribute, are they the tier one?
00:31:14 _acebuild: Sharing data is that really a good idea?
00:31:57 _acebuild: Or are you going to let them know before signing up?

Recording

https://youtu.be/QmBV-eiLgSM

As discussed in #33

• every meeting should end with notes from the meeting host on things that we could improve based on the questions from the participants

For this, we could use https://blog.otter.ai/zoom/ to automatically generate transcripts and save/paste them into the issue to refer to later.

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Just some updates
3. Q&A

Notes

• Again some new faces joined the meeting 💪🏼
• There was a question on how to get along with bindings not requiring JSON Schema and therefore not being validated by the parser. We pointed to this issue from Maciej asyncapi/spec#507 and explained that this project has to be simply driven forward and pushed into the spec as other changes. So far everyone agrees this is a very useful addition. First, we need to change the spec and then get tools (like parser) to adopt it.
• We discussed what are the next big changes that may trigger 3.0 release. First of all, we learned that Fran is going to have a baby and will go for parental leave for a couple of months (congrats mate!). There are 2 big issues with the spec that should be solved and will trigger 3.0 (dunno when), it is: channels reusability and semantics of publish/subscribe operation that is confusing to people. Once someone finds a good way how to accomplish this, we will release 3.0 for sure. Related issue asyncapi/spec#415 and asyncapi/spec#390. We discussed in detail the current challenge with the spec.
• We updated the community with some things that happen currently:
  • proposal on how to introduce changes in the spec in organized way asyncapi/spec#511
  • discussion on release cadence asyncapi/spec#513
  • asyncapi repo is now spec and stuff like this meeting agenda are now under community repo
  • blog post about February at AsyncAPI https://www.asyncapi.com/blog/february-2021-at-asyncapi
  • remember we wait for feedback on open governance until 23rd of March

Recording

https://youtu.be/r5hLFnqY8D4
tbd

Reason/Context

With more and more tools, we increase the attack surface that might be leveraged in unintended ways. We should provide a structure where code owners and maintainers can spare and help each other solve security issues.

The current security policy we have: https://github.com/asyncapi/community/security/policy (What happens when someone sends an email to this? I have no idea 🤷). Are we using the security advisory feature on GitHub on each repository?

Description

Therefore we should provide a clear structure for everyone evolved to know the entire process. From the reporter to the one fixing the issue.

• Does it make sense to create a security advisory group that can help solve the given issues together with the maintainers?
• Does LF dictate any process we must adhere to?

Reason/Context

With the specification, we define our channels with the RFC 6570 standard. However, from a tool perspective, this fact can easily be overlooked (at least I severely overlooked it) with ts-nats-template). This means, that once we want to realize the channel we must support different features of variable expansion, and other features of RFC 6570.

This is not something that all tooling providers can be expected to implement on their own.

Description

So how do we make it easily supported so the quality of tooling does not degrade based on which one you use? (In terms of channel realization)

I tried to look for already existing tools:

• https://github.com/LuvDaSun/rfc6570 - unmaintained and not a stable version
• https://github.com/grncdr/uri-template - might be maintained, and seem stable, not sure how easy this could be integrated?
• https://www.npmjs.com/package/urijs - maintained, not sure how well it works with RFC 6570

And if we use third-party tools - even help maintain them, how can we best help tool owners, be aware of this 🤔?

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. Roadmap - Where are we? - @fmvilas
4. Release 2.1 update - @derberg
5. AsyncAPI conference/hackathon - @derberg
6. Q&A

Notes

• Fran explained the structure and the purpose of AsyncAPI roadmap. He also shared current status and where is the main effort atm. Have a look yourself https://www.asyncapi.com/roadmap

• Lukasz shared the status for 2.1 release:

  • IBM MQ is merged in.
  • New props for the message example need some fixes.
  • AnypointMQ has some open questions, most probably will need to wait for September release as we want to release 2.1 this week.
  • Automation is ready in 95%. Just some final tunning from Aayush left.

  Have a look yourself asyncapi/spec#536

• Lukasz shared that we want to organize an AsyncAPI event this year, maybe a conference or a hackathon, but most probably it will be both as so far people have good opinions about both. If you want to be actively involved in events organization, join #07_events channel on AsyncAPI Slack -> https://www.asyncapi.com/slack-invite/

Recording

https://youtu.be/u83V2gIUGHU

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. AsyncAPI Workshop by @jpgough
4. 2.1 release by @derberg
5. Q&A

Notes

• Jim Gough provided a great presentation on how the workshop structure could look like. We now have a dedicated repository for AsyncAPI training and let us continue discussions there https://github.com/asyncapi/training/discussions
• Lukasz Gornicki gave an update on Google Summer of Code. That deadline to accept proposals is on 13th, Thursday. Then it will take some time once Google informs students. We cannot do this directly, this is the policy.
• Lukasz Gornicki started a discussion on the 2.1 release that will happen in June. There is a lot of work to do before the release. Any help is wanted so join us if you can help.

Recording

https://youtu.be/GmL0PCI8FLk

Reason/Context

Even though the AsyncAPI document itself is safe, in the context it is used it can become an attack surface. This is especially relevant in code generation aspects, where values from the AsyncAPI documents can be used as-is.

I would like to discuss at which "level" should this issue be handled so we can take the appropriate actions.

Scope of the issue

Use-cases/libraries where this is a problem:

• Generator, and all templates that do not manually handle this.
  • The nunjucks rendering engine is "safe" per default, as you have to use {{somevariable | safe}} to get around the escaping of values. It escapes the values based on simple regex and it would cover most cases I think. However, only as long as safe is not used.
  • The react rendering engine does not escape any values per default. Some templates might have their own sanitation.
• Modelina
  • As we generate models based on the AsyncAPI/JSON Schema definition, to multiple languages
• React components
  • As they are generally used to integrate into a website.
• Others?

Public related advisories:

• GHSA-xj6r-2jpm-qvxp
• GHSA-4jg2-84c2-pj95

Solutions

These are the following potential solutions we could take a look at (Thanks for brainstorming @magicmatatjahu @smoya):

1. Introducing sanitizing in parsers. This will solve it at a "global" level.
   • Example could be to introduce a safe configuration that the dependant libraries can use (even when they are not).
   • We are however not sure if we can sanitize values accurately for each language they are used in.
2. Acknowledging the problem is enough, and assume AsyncAPI documents will always be safe (even if they are not).
3. Warn user about potential code injection if found, can be done with something similar to static code analysis.
4. Let each library solve the sanitation problem on their own based on what they output to (HTML, Java, TS, etc).
5. Other?

Original file: https://linuxfoundation.smapply.io/prog/asyncapi_conference_2021/

Criteria:

• AsyncAPI Logo
• "Online Conference"
• "November 16-18, 2021"

Sizes:

• Header Image 2400 x 500
• Mobile image 1024 x 1024
• Mobile Header 1200 x 500

The purpose of this meeting is to focus on contributors, focus on people that want to contribute to AsyncAPI Initiative but do not know how to do it. AsyncAPI Initiative is a large project, with lots of code, lots of docs, and many many other areas that need help, but it is not easy to start.

Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM 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.

This meatin is a live-stream that goes to the following social media:

• YouTube
• Twitch
• Twitter
• LinkedIn

To broadcast the live-stream, we are using Restream. You are invited to join us live on the call and not only interact through chats on YouTube and Twitch.

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. Next steps for extensions catalog - @jonaslagoni
4. Q&A

Notes

We talked mainly about the extensions catalog:

• About things that need to be done to make the extension catalog useful for the community (availability and tooling support)
• About https://github.com/RepreZen/Semoasa#semoasa adoption/inspiration for extension catalog data format
• After all the discussion Jonas created a set of issues for things that need to be done -> https://github.com/asyncapi/extensions-catalog/issues/created_by/jonaslagoni.

Nobody from current maintainers is working on the topic so if you wanna help, join and take ownership of something - this is the right candidate

Other topics were

• request from Fran to contact him if someone wants to play with his mysterious framework
• Mike asked about the Diff library that is part of GSoC efforts
• Tomorrow, Wednesday, we host our first Contributor-first meeting at 1PM UTC that is for existing or new contributors that need support in the first steps in the constellation of AsyncAPI repositories and tools. Details in the calendar: https://calendar.google.com/calendar/embed?src=tbrbfq4de5bcngt8okvev4lstk%40group.calendar.google.com&ctz=Europe%2FWarsaw
  We want it to be a regular meeting.

Lukasz's knee took over the meeting 🙈

Recording

https://youtu.be/pO9bcs7l3fQ

Is your feature request related to a problem? Please describe.
Not related.

Can't it be tackled using specification extensions?
No

Describe the solution you'd like
As with openAPI, it would helpfull to have a autocomplete plugin for intelliJ IDE.
This will allow us to write documentations and specifications without writing invalid asyncAPI files.
Additional, this will give us a chance to include code generators within the IDE (Would be good if this is another plugin to keep things simple).

Describe alternatives you've considered
Think there will be none.

Additional context

Hi is there any support for .Net core? I can't seem to find one. I mean how can I generate .net core code from the specs

As a user, I'd like to understand what's the vision and scope of AsyncAPI. I should be clear what is part of the scope and what is not, and where the project is heading to.

@jhigginbotham did some great questions that must be answered in this document:

• What is the overall scope?
• Is it just to capture events and streams available?
• Is it a higher-level view of all interaction styles, e.g. RPC, REST, message streams, events, file drops/FTP
• What is the end goal/stopping point for the spec - drive definition capture, doc generation, other?
• How does this fit with OAS?
• How does this fit with ALPS?
• Do we support any/all of the following technologies? e.g. gRPC (has bi-dir support), Websockets, SSE, Webhooks, Kafka, and Kinesis streams
• What formats do we support? e.g. JSON, XML, Avro, ProtoBuf, Binary

References:

• https://wiki.base22.com/btg/template-vision-and-scope-document-20480031.html
• http://trishmarie.com/vision.pdf
• http://www.startupcto.com/templates/software-vision-document-template
• vision-document-template-v1.pdf

The purpose of this meeting is to focus on contributors, focus on people that want to contribute to AsyncAPI Initiative but do not know how to do it. AsyncAPI Initiative is a large project, with lots of code, lots of docs, and many many other areas that need help, but it is not easy to start.

Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM 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.

This meatin is a live-stream that goes to the following social media:

• YouTube
• Twitch
• Twitter
• LinkedIn

To broadcast the live-stream, we are using Restream. You are invited to join us live on the call and not only interact through chats on YouTube and Twitch.

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. AsyncAPI Hackathon and Conference - @derberg
4. Q&A

Notes

We talked about the events proposals for AsyncAPI Initiative, Hackathon and a Conference.
We just kick off preparation and it is the best time for you to join -> https://github.com/asyncapi/community/pull/37/files

Chat

00:08:57 Aayush Sahu: No questions. Thanks :)
00:10:17 Lukasz Gornicki: https://github.com/asyncapi/community/pull/37/files
00:13:53 Lukasz Gornicki: https://www.asyncapiconf.com/
00:15:53 Aayush Sahu: speaking of marketing, can we implement something that nextjs does?
00:16:21 Aayush Sahu: wait, let me find that link.
00:16:52 Aayush Sahu: Like a virtual ticket kind of. Saying that you have participated in the conference. I'm finding the link
00:17:39 Aayush Sahu: https://nextjs.org/conf/tickets/jun21/aayushmau5#room-hy8xk
00:17:59 Aayush Sahu: It's free. It's just for a show. Things you can tweet
00:18:06 Aayush Sahu: to make people more aware i guess
00:18:47 Aayush Sahu: after registration.
00:18:50 Aayush Sahu: optional
00:19:01 Aayush Sahu: kinda of a marketing tactic
00:20:24 Aayush Sahu: WIll make a suggesting in the PR.
00:22:14 Aayush Sahu: Bye. Have a good day :D

Recording

https://youtu.be/PGfkfI9SMmY

Firstly, thanks for getting involved! Please make sure you are familiar with the project's Code of Conduct.

There are several ways to communicate with the AsyncAPI project:

• Subscribe to our Newsletter to learn about the status of the project.
• GitHub issues - for bugs and feature requests
• GitHub pull requests (PRs) - for fixes or new features already discussed, as per the contributing guidelines
• The AsyncAPI Slack workspace
• The regular meetings:
  • See the shared Google Calendar.
  • More info about meetings is on our dedicated Meetings view on the website.
• The AsyncAPI YouTube Channel
• Social media:
  • Twitter
  • LinkedIn

Reason/Context

To help visualize collections of applications we could create a VR/AR "game" which can visualize how multiple applications are connected.

Why?

• Help new members of teams quicker learn about the setup rather than looking at UML diagrams.
• It is cool 🤷

Description

It should show the applications and who are connected to each other. Furthermore, you should be able to further inspect specific channels, messages, operations, etc.

Wishful thinking

• Connect it to deployments to inspect specific messages that are being transmitted in the system as well as application monitoring. This can be done since each application would have its own AsyncAPI document we know which applications exist in the system.
• Maybe even extend it to allow modifications to the underlying AsyncAPI documents to propose new connections, remove old ones, modify message payload validation rules, etc.
• Trigger messages on specific channels/scenarios using the simulation library.

Related issues/libraries

• https://github.com/asyncapi/community/issues/16 might be useful to integrate.
• https://github.com/asyncapi/community/issues/19 for simulating messages in a system.

Feedback

• Other ideas for extensions/improvements that could be included?
• Is it a good or bad idea?

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Awesome news from Google Summer of Code @derberg
3. Release 2.1 prep status @derberg
4. Intent-driven API discussion onboarding @jonaslagoni
5. Place for your topic
6. Q&A

Notes

• Lukasz Gornicki provided an update on the AsyncAPI participation in Google Summer of Code. Thanks to Postman we got 5 spots, which means that next few months 5 amazing students will work with us on new libraries for AsyncAPI. To learn more about the ideas read this list or just stay tuned for an article with updates on what happened in May at AsyncAPI (rss feed)
• Lukasz Gornicki provided an update on work towards 2.1 release. All work tracked here. Automation of release candidates' publish process is done. Automation of docs publishing to the website is in progress. Remember that if you have some proposal that is already there in the repo for few months, no objections from the community to get it into the spec, but you cannot champion it atm, feel free to share it in our Slack with our most active community, maybe there will be someone that can help out to push it through the process.
• Jonas Lagon shared an overview of the discussion around intend-driven API and the current API design. We had a long discussion and explained well the core of the current issues with the API so this part of the meeting is a good kick-starter for you to join this discussion. We need you there!
• Colin Sullivan from NATS project joined to talk about the current contributions of AsyncAPI to NATS and offered help. The most active project around NATS is TypeScript/Node.js NATS template and we definitely need help there, but there are also other areas, like the request/reply pattern discussion that is also interesting for NATS. The best is to join our Slack and discuss details there.

Recording

https://youtu.be/UCaDcQhDRIY

Review the existing governance model and improve it to assure model is open for community and assures project can still efficiently go forward:

• assure open governance
• make it clear what it means to join the project as a maintainer (what maintainer is)
• what sponsorship means?
• make sure that the model we pick is open but also non-blocking. Whenever voting is needed the voting group has to be odd so we never get a draw
• should we draw a clear line between spec and tooling? should we separate technical oversight committee for the governance board (steering committee)? Then we need to clearly describe how to become a member of each, and how to stop being a member
• should we differentiate between individual contributors and corporate contributors? In the case of corporate, we need to make sure that it is not possible to have to representatives from the same company in the TOC and SC and also what to do if one of the members moves to the company that already has a member (membership termination rules)

Some good resources:

• current model https://github.com/asyncapi/asyncapi/blob/master/GOVERNANCE.md
• https://github.com/vulcansonline/awesome-open-management
• https://opensource.com/article/20/2/open-source-projects-governance

Proposed official channels:

01_introductions (NEW)
    topic: Welcome to our AsyncAPI Slack! Take a moment to introduce yourself.
02_general (old general)
    topic: Talk here if your topic is not only about the spec, nor tools but kinda mix and not only but involves AsyncAPI :)
03_specification (NEW)
    topic: All around the spec discussions. It is ok to ask for support here.
04_tooling (old tooling)
    topic: All around the spec tools discussions. It is ok to ask for support here.
05_promotion-and-marketing (old promotion-marketing)
    topic: Purpose of this channel is to help us with AsyncAPI promotion. Share your ideas for marketing and learn what we are working on at the moment. We use “channel” annotation here when we want to ask you to share our specific resources on different social media.
06_training (old training)
    topic: All about trainings, workshops, courses, etc. — https://github.com/asyncapi/training.
07_events (NEW)
    topic: At least once a year we need to organize an event that makes a lot of noise around AsyncAPI. Sometimes it is a conference, meetup or a hackathon. This is the place where we regroup and organize. This is also a place where you should always let others know what events are you involved in, where and when do you present a topic related to AsyncAPI. Looking for a speaker that can talk about AsyncAPI? Ask here.
08_jobs (NEW)
    topic: Looking for a job that will let you work on AsyncAPI? Let others know. Looking for AsyncAPI expert to join your company, post your offer here and also on the AsyncAPI website https://www.asyncapi.com/jobs.
09_not-humans (NEW)
    topic: Sometimes you're just tired of humans. Share your love to non-humans. Pics or it didn't happen!
10_watercooler (old random)
    topic: Talking about things that are off-topic. Get to know folks' other interests that aren't around AsyncAPI :) When you have a need to talk to someone "in person", join this zoom meeting, if no one is there, ping folks in the channel that you are looking for a connection. Talking to another human solves many problems.
97_bot-github-new-issues-prs (old github-new-issues-prs)
    topic: Bot sends notifications about every new issue and pull request in any AsyncAPI repository.
98_bot-github-releases (old github-releases)
    topic: Bot sends notifications about every new release in any AsyncAPI repository.
99_bot-twitter-mentions (old twitter-mentions)
    topic: Bot sends notifications about every new tweet where AsyncAPI is mentioned.

Why N_ prefix. I copied it from one of my favorite workspaces (the community club) where everything is well organized:

• Prefix brings order and structure
• Prefix indicates that a given channel is officially maintained
• We all can easily and proactively educate all members about where to go with a given topic

Other comments:

• Channels that are not on the above list will be removed
• Every new joiner gets a welcome message from a bot that introduces channels and the protocol
• We will use @channel annotation in general channels once all the changes are done in the system, so members that are already here are aware of the reorg
• There will be a new repository called support where only Discussions will be enabled. We will use it as an archive for topics we discuss on Slack. How? I will write a bot that reacts to specific emoji (a sign of infinity) called infinity/forever. If emoji is added to a main message, bot will save it with entire thread as new discussion item in the support repository. This is important even if someday we can afford Standard subscription on slack and unlimited messages history. This solution will make it very easy to access all the important discussions we had in slack from one location. Another cools stuff about this solution is that we will be able to write another bot that suggests answers to questions in Slack basing on the data from Discussions ❤️
• the etiquette will be part of .github repository, so any changes to it will go through a usually approval process over pull request
• why Slack and not something else? why not? every tool has its advantages and disadvantages, so let us just optimize Slack. why we need Slack or any other messaging tool? because we want to stay close with those that are most active in the community, have an option to establish connection other than email

Slack Etiquette aka Protocol:

• Respect each other. Choose empathy over judgement. Act according to the AsyncAPI Code of Conduct
• Run discussions in threads. Every singe message in a main thread triggers notification, another message about the same triggers another notification. Let us not ping each other when it is not necessary. Always reply to a message in a thread.
• Avoid using @channel and @here unless the description of a given channel states differently.
• Once you post a message with links. Remove generated previews. Leave them only if they add some more context to the message.
• In case you need a dedicated channel for some discussion, feel free to create it but don't use N_ prefix that is allowed only for officially maintained channels.
• When you mute some channel, we encourage you to configure alerts for discussions that are most interesting for you. We do not want to loose your input. Go to Settings -> Notifications -> My keywords section.

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. @GeraldLoeffler - Support defining and referencing protocol headers
3. Place for your topic
4. Q&A

Notes

• Fran shared the current status of the 2.1 release. It is scheduled for June. Also plans on the next release that will happen in September.
• Gerald started a discussion about bindings and also the message headers:
  • contentType purpose and meaning
  • userId from amqp binding
  • HTTP binding headers and having common headers (for stuff like content-type and others)
  • correlationID and headers relation + how about the correlationId points to protocol-specific location (when we usually put protocol-specific things into bindings)
• Bindings JSON Schemas are ready, now they need to get integrated with the Parser so it can validate binding information properly. Reference issues are asyncapi/parser-js#315 and asyncapi/spec#507

Recording

https://www.youtube.com/watch?v=DLgWdC1mHJI

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Usual hackathon and conference update - @derberg
   • website https://conference.asyncapi.com/
   • sponsors https://opencollective.com/asyncapi/events/asyncapi-hackathon-and-conference-2021-3156d7af
   • cfp https://linuxfoundation.smapply.io/prog/asyncapi_conference_2021/
3. TSC setup update - @derberg
   • current list https://github.com/asyncapi/community/blob/master/TSC_MEMBERS.json
   • current voting setup https://groups.google.com/u/1/g/asyncapi-tsc-members
   • what is still missing asyncapi/.github#47 (comment)
4. Place for your topic
5. Q&A

Notes

• Lukasz shared progress on AsyncAPI Hackathon and a Conference. Website ready, CfP opened and we are looking for sponsors. Please talk about it with your managers and also feel free to contact Lukasz if you need help in convincing it makes sense to sponsor the event
• Lukasz shared progress on setting up a list of TSC members. He explained how it looks like in theory from open governance model point of view and what is accomplished already. We have basic voting setup with google groups, and decisions are visible publicly. More help with fill automation is needed.
• Alejandra brought up important topic of woman representation in TSC group. Lukasz explained technicalities behind becoming a TSC member. We agreed that we need to continue discussion and find a way to bring more women to the project. Kin opened this public discussion -> #72 and we should continue discussion in public

Chat

00:08:23 NektariosFifes: hello
00:08:31 NektariosFifes: 1 sec I have an issue with my mic
00:14:47 Lukasz Gornicki: https://conference.asyncapi.com/
00:14:57 Kin Lane (Postman): WOOOHOOO!!
00:15:18 Lukasz Gornicki: https://opencollective.com/asyncapi/events/asyncapi-hackathon-and-conference-2021-3156d7af
00:17:24 Alejandra Olvera-Novack: YAY! yesss
00:17:37 Lukasz Gornicki: https://linuxfoundation.smapply.io/prog/asyncapi_conference_2021/
00:26:21 Jonas Lagoni: Will we utilize the TSC to be the group that will vote on talks or?
00:28:14 Lukasz Gornicki: https://github.com/asyncapi/community/discussions/categories/asyncapi-hack-conf-2021-organization
00:28:51 Alejandra Olvera-Novack: This is soooo cool ! 😎
00:30:14 Jonas Lagoni: Makes sense, I will follow up in the discussion
00:30:35 Charlton Port: do you have any idea of the expected size of the event?
00:30:49 Charlton Port: Also, are there any “themes” for the hackathon?
00:35:45 Charlton Port: One is: “Bring new AsyncAPI-related solutions that can solve the existing challenges the community is facing with event-driven architectures” - can you offer any examples
00:37:40 Charlton Port: Makes sense thank you!
00:40:10 _acebuild: POWER!
00:40:57 Lukasz Gornicki: https://github.com/asyncapi/community/blob/master/TSC_MEMBERS.json
00:42:27 Kin Lane (Postman): I will schedule a separate meeting to discuss across all of the API specifications. BIG PROBLEM!!
00:43:35 Alejandra Olvera-Novack: Yup
00:44:51 Lukasz Gornicki: https://groups.google.com/u/1/g/asyncapi-tsc-members
00:45:30 Lukasz Gornicki: asyncapi/.github#47 (comment)
00:48:17 Alejandra Olvera-Novack: Thank you :D
00:51:35 Aayush Sahu: Lemme know how can I help :)
00:52:03 Alejandra Olvera-Novack: I want to meet Kin’s dog !!
00:52:56 Aayush Sahu: The best part of the meeting xD
00:53:24 Sergio Moya: Sooo cute

Recording

https://youtu.be/KNMdqXIxr-s

The charter: https://github.com/asyncapi/community/blob/master/CHARTER.md#2-technical-steering-committee

Item 2.5. is as follows:

No more than one-fourth of the TSC members may be affiliated with the same employer. If the removal or resignation of a TSC member, or a change of employment/affiliation by a TSC member, creates a situation where more than one-fourth of the TSC membership shares an employer, then the situation must be assessed by TSC. In any case, the number of TSC members affiliated with the same employer must not be higher than one-third (round half up number).

The last line says "one-third", while twice previously it says "one-fourth".

Was this an oversight? Should it be "one-forth"?

Slack discussion thread: https://asyncapi.slack.com/archives/C023A76SV2Q/p1634634997121400
Inspiration: https://pbs.twimg.com/media/FAkpXMmWEAQeZFr.jpg

Design criteria

• Logo
• Presentation Title
• Presenter(s') Headshot(s)
• Presenter Name(s) & Credentials
• Register Now button

In addition, need card templates for live streams, and contributor-first meetings

The purpose of this meeting is to focus on contributors, focus on people that want to contribute to AsyncAPI Initiative but do not know how to do it. AsyncAPI Initiative is a large project, with lots of code, lots of docs, and many many other areas that need help, but it is not easy to start.

Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM 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.

This meatin is a live-stream that goes to the following social media:

• YouTube
• Twitch
• Twitter
• LinkedIn

To broadcast the live-stream, we are using Restream. You are invited to join us live on the call and not only interact through chats on YouTube and Twitch.

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. Q&A

Notes

There was nothing in the agenda because there was no agenda as I was taking care of it this time and y'all know I'm pure chaos 😅 I'm creating this issue after the SIG meeting just for the sole purpose of leaving a record of what happened.

We mainly talked about Glee and I even did an improvised demo.

Chat

00:09:19	Fran Méndez:	https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md
00:09:36	Fran Méndez:	https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md#stage-3-accepted
00:19:10	Fran Méndez:	https://github.com/asyncapi/glee/
00:19:17	Kin Lane (Postman):	That is what I came to see. ;-)
00:28:41	Aayush Sahu:	oh, it's running the function based on the file name?
00:28:43	Sergio Moya:	Folks, need to leave! See u on Slack!
00:28:50	Dale Lane:	I have to run - this is looking really cool!
00:29:01	Aayush Sahu:	Bye
00:35:41	Maciej Urbańczyk:	Format of the repo name is create-{YOUR_NAME}-app
00:39:05	Fran Méndez:	https://github.com/asyncapi/create-glee-app#options
00:40:43	Fran Méndez:	https://github.com/asyncapi/glee/tree/master/examples/dummy-java
00:41:57	Fran Méndez:	https://www.github.com/asyncapi/modelina
00:42:43	Fran Méndez:	—experimental-java
00:43:21	Aayush Sahu:	Bye. It was a good meeting :)
00:43:37	Michael Davis:	Thanks, bye!

Recording

https://youtu.be/IA-0NYuvqvU

All our repositories use the same logo and it does not look great with the new darkmode GitHub recently introduced. Just wanted to raise awareness in case its something we want to address.

There are many useful features that are not incorporated to the spec because they're specific to a protocol, or they add too much complexity to the spec, etc. I always respond suggesting to create a specification extension (you know, those starting with x-). However, I understand that when something is standardized it's much easier to reuse. Right now we have different people creating different specification extensions to tackle the same problem.

It would be awesome to have a specification extensions catalog, where anyone can find —and contribute to— extensions that already solve the problem they have. For us, the specification maintainers, it's a good source of information to understand what people do want to achieve using AsyncAPI and, eventually, we might want to incorporate some of these extensions into the spec.

Reason/Context

Creating an educational & technical video explaining AsyncAPI's main features will be helpful for new on-boarders that need a high-level intro to the spec.

This video can be used for any kind of audience and should be agnostic-minded.

Tagging @derberg @Barbanio @fmvilas

(note: Can lukasz or someone help me tag Debi into this issue? I don't know her GH handle and me trying @Docjones doesn't seem to be working here, that seems to belong to someone named Mark?...)

The purpose of this meeting is to focus on contributors, focus on people that want to contribute to AsyncAPI Initiative but do not know how to do it. AsyncAPI Initiative is a large project, with lots of code, lots of docs, and many many other areas that need help, but it is not easy to start.

Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM 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.

This meatin is a live-stream that goes to the following social media:

• YouTube
• Twitch
• Twitter
• LinkedIn

To broadcast the live-stream, we are using Restream. You are invited to join us live on the call and not only interact through chats on YouTube and Twitch.

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Usual hackathon and conference update - @derberg
3. Release 2.2 - @derberg
4. Place for your topic
5. Q&A

Notes

Conference

• event details http://conference.asyncapi.com/
• registration is finally available https://zoom.us/webinar/register/9316328215628/WN_pv8NDGIoSg2CnF9qsoptWw
• sponsors prospectus ready https://conference.asyncapi.com/attachments/AsyncAPI-Hackathon-and-Conference-Prospectus.pdf
• Contributor-first meetings for Hackathon participants and also Hacktoberfest folks are scheduled for every Wednesday in October. Check out AsyncAPI calendar https://calendar.google.com/calendar/embed?src=tbrbfq4de5bcngt8okvev4lstk%40group.calendar.google.com

2.2 release

• It happens today
• All features come from amazing @ GeraldLoeffler
• Release notes PR -> asyncapi/website#324
• Release coordination for 2.3 for January 2022? anyone can take this role -> https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md

Chat

00:09:36 Lukasz Gornicki: https://conference.asyncapi.com/
00:14:05 Lukasz Gornicki: https://calendar.google.com/calendar/embed?src=tbrbfq4de5bcngt8okvev4lstk%40group.calendar.google.com
00:16:40 Lukasz Gornicki: asyncapi/website#324
00:18:57 Lukasz Gornicki: https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md
00:19:40 Ben Gamble: Sry my scrum is starting, have a great day all!
00:22:40 _acebuild: Yep!
00:23:06 Sergio Moya: 🎉
00:25:15 Viswa Ks: #81 is this one ?
00:27:45 Lukasz Gornicki: https://www.asyncapi.com/slack-invite
00:28:34 Vladimír Gorej: No; looking forward for a release! ;]

Recording

https://youtu.be/8ddwX0CyUeE

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. Let us finally schedule that 2.1.0 release!
4. Q&A

Notes

Release 2.1:

• We talked about release cadence in general + schedule of the 2.1 release (May vs June). We want to make a decision this week. Please join here asyncapi/spec#513
• If you want to push your things into 2.1 release, and you do not know how to do it - contact us and we help.

Other:

• The last 7min of the call we quickly discussed a topic from @GeraldLoeffler PR that proposes a "link" between servers and channels. One of the use cases is when your application talks to 2 different message brokers, for example MQTT and Kafka. Join the discussion asyncapi/spec#531

Recording

https://youtu.be/roiMTGhoBfo

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. Update on AsyncAPI Conference and Hackathon - @derberg
   • 1 hackathon submission
   • over 150 Conference registrations
   • 10 CfP submissions (deadline this weekend) - IoT/Kafka/CloudEvents/ServerlessWorkflow/Socket.io/WebSocket
   • 4 platinum sponsors
4. Contributor-first meeting advertisement - @derberg
   • every week of October, Wednesdays, twice a day. Details in AsyncAPI's Google Calendar.
   • Recordings available here
5. AsyncAPI Landing Page improvements - @boyney123
6. Ideas for AsyncAPI docs generation - @boyney123
7. Q&A

Notes

Hackathon and Conference

• 1 hackathon submission
• over 150 Conference registrations - organic growth without paid marketing
• 11 CfP submissions (was 10 on the meeting day. deadline this weekend) - various topics IoT/Kafka/CloudEvents/ServerlessWorkflow/Socket.io/WebSocket
• 4 platinum sponsors 🚀 and more sponsors to come

We did not have time to have a strong public discussion about if it is worth investing in paid Facebook adverts. So the discussion is opened. Just leave your opinion here -> #47 😄

Contributor first meeting

• special meeting for those that want to start contributing but are not sure how. It is a live stream that you can join on different AsyncAPI social accounts (Twitter/Twitch/YouTube/LinkedIn)
• every week of October, Wednesdays, twice a day. Details in AsyncAPI's Google Calendar.
• Recordings available here
• 13th of October, 4PM UTC it will be dedicated to Modelina and Glee project, from a contributor perspective
• We know we still lack good visibility of these meetings. We are open to any suggestions.

Landing page improvements

• there are some great ideas to improve landing page, one of those is adding "what is AsyncAPI section" (share opinion asyncapi/website#406)
• there is also a discussion on how we should do changes, like reorganization or removal of some parts of the landing page. There are different opinions. 2 strong opinions are that we should use extended tracking with Google Tag + do A/B testing with alternative versions of landing page using split testing functionality from Netlify.

Join discussion #108

Eventstorming aka UI that will make it much easier for folks to design their architecture in UI without manually writing the AsyncAPI file

The title includes the overview 😄
You really should join related discussion -> #91

Chat

18:09:01 From Lukasz Gornicki : https://github.com/asyncapi/community/discussions/categories/ideas
18:17:08 From Aayush : 👏👏
18:17:21 From Deven Phillips : WOW! Awesome!
18:17:31 From David Boyne : 👏
18:24:08 From Sergio Moya : Jonas rocking on stage
18:25:05 From Deven Phillips : I’m interested in helping with generators.
18:25:15 From Deven Phillips : Specifically, I would like to help with Quarkus and Vert.x
18:26:37 From Deven Phillips : I cannot attend tomorrow unfortunately.
18:28:07 From David Boyne : Be good to understand how the js-parser works and how you could contribute to that too, (at some point in the future)
18:33:03 From Jonas Lagoni : For all relevant events you can add the calendar from here: https://github.com/asyncapi/community/#meetings
18:33:14 From Alejandra Quetzalli : Thank you!!
18:33:23 From Lukasz Gornicki : https://calendar.google.com/calendar/u/0/[email protected]
18:33:27 From Irmin Nadir Palacios : Thank you
18:41:17 From Jesse Menning : agree with David.
18:43:24 From Sergio Moya : Have to leave folks, a pleasure! Take care
18:43:50 From Deven Phillips : +1 To Alejandra
18:45:11 From Aayush : +1 to Deven.
18:45:11 From Kin Lane (Postman) : +1000 to Deven & Alejandra
18:45:56 From Alejandra Quetzalli : That SEO I tell ya :D
18:48:01 From Alejandra Quetzalli : +1 to Irmin: “good also for non-technical people”
18:50:02 From Alejandra Quetzalli : So cool, David!! Thank you for doing this
18:51:57 From Deven Phillips : We should try to get metrics and journey data first to be able to compare.
18:52:10 From Alejandra Quetzalli : https://www.rust-lang.org/
18:54:22 From Irmin Nadir Palacios : You mean AB testing by polling questions? Or deploying different websites at the same time?
18:54:46 From Deven Phillips : Not sure if that is possible with netlify
18:55:10 From Irmin Nadir Palacios : That’s what I just thought. Ale. Great!✌🏻
18:55:44 From Deven Phillips : https://docs.netlify.com/site-deploys/split-testing/
18:58:18 From Deven Phillips : I’m drooling over the idea of an EventStorming webapp.
18:58:29 From Alejandra Quetzalli : :D
18:59:16 From Deven Phillips : With the advent of the pandemic, we have been unable to effectively run an event storming session with our customers.
19:02:05 From Lukasz Gornicki : #91
19:05:01 From David Boyne : Thank you all 👋
19:05:28 From Aayush : Bye

Recording

https://youtu.be/6D0Oem-jzyg

As a maintainer, I'd like to understand what are the processes when managing the project.

The following are some things to document:

• When to apply the following issue labels: good first issue, "version x.y.z", backlog, question, bug, feature request, and duplicate.
• When and how to communicate the rest of the team you're working (or blocked) on an issue.
• Which branch the Pull Requests should go against.
• When are SIG meetings happening.
• Create feature-related Slack channels.

Reason/Context

Please try answering few of those questions

• Why we need this improvement?
• How will this change help?
• What is the motivation?

In a Kafka Cluster, you start a project with few topics but the it grow with the time. Traditionally, you could create a documentation about the topics in a manual way but that documentation could be obsolete soon.

Kafka by nature is asynchronous, so why not generate an AsyncAPI Spec from Kafka in an easy way?

Description

Please try answering few of those questions

• What changes have to be introduced?
• Will this be a breaking change?
• How could it be implemented/designed?

It could be interesting to create a Maven plugin or something with the idea to:

1. Connect with the cluster
2. Generate an AsyncAPI Spec
3. Put the generated Spec in a folder.

That execution could be chained with other external mechanisms like FTP/Others running in a CI pipeline for the publication of this Kafka documentation.

Note: this idea was the outcome from a conversation from @RobWin and me on Twitter: https://twitter.com/juanantoniobm/status/1397444093484089345?s=20

Many thanks in advance

Juan Antonio

Reason/Context

AsyncAPI Initiative maintains not only AsyncAPI spec but also a huge amount of different tools. People can contribute whatever they want really:

• docs
• tests
• code
• articles
• coordinate release process of the spec
• actually anything, we just need to know what are your capabilities

This of course means that making first (and not only first) contribution may be difficult. There are many repos, many old problems (with testing of templates for example) that only few know and can explain. There is different contribution guide for tools and spec. We need to start writing a good contribution toolkit/guide and best would be to write it basing on the experience of current contributors.

Description

• have it every week
• at least one of the regular contributors/maintainers MUST be there to answer questions. We need to figure out how to schedule that
• have it like SIG meeting in different time zones
• every meeting should end with notes from the meeting host on things that we could improve basing on the questions from the participants
• recorded - live streamed
• setup should be maintenance-free, automatic because basing on my experience, the setup of SIG meeting takes time, no question about it
• advertise the meeting
• maybe we need dedicated channel on Slack like 09_contribute instead of 09_not-humans that is inactive
• create a callendar invite like for the SIG meeting

We are now able to easily start a zoom call in any Slack channel. We can set Slack reminder in channel too. Most tricky will be to start z zoom call and start immediately streaming the meeting to AsyncAPI youtube/twitter/twitch accoutns

As a contributor, I'd like to understand what being a maintainer actually means.

Don't feel bad for reusing what others have done already.

References:

• https://github.com/Homebrew/brew/blob/bbed7246bc5c5b7acb8c1d427d10b43e090dfd39/docs/Maintainers-Avoiding-Burnout.md
• https://github.com/CocoaPods/CocoaPods/wiki/Communication-&-Design-Rules

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Important special announcement
3. Q&A

Notes

1. Important special announcement
   • AsyncAPI joins Linux Foundation
   • Charter -> https://github.com/asyncapi/.github/blob/master/CHARTER.md
   • Blog post from Fran -> https://www.asyncapi.com/blog/asyncapi-joins-linux-foundation
   • Linux Foundation blog -> https://linuxfoundation.org/en/press-release/linux-foundation-will-host-asyncapi-to-support-growth-and-collaboration-for-industrys-fastest-growing-api-spec/
   • Making changes in the spec -> https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md (if you know GraphQL way of doing it - it's the same)
2. Hint for big companies. If you want to get a spot in TSC easily, just hire current individual contributors 😉
3. We are looking for people willing to contribute to bindings and becoming owners of them
4. No requirement for CLA for tooling. Most probably we need one for the spec.
5. Next steps

   • Agree on release cadence asyncapi/spec#513

   • Setup CODEOWNERS and VOTING files everywhere

   • Put somewhere on the website a list of current TSC members

   • Start thinking about tooling that supports the charter rules

   • Figure out CLA need for the spec
     Disturbance in force:

   • Fran will be super busy now with his kid

   • Next 2 weeks Lukasz will be involved in the review of Google Summer of Code applications

     !!!Any help with the above will be highly appreciated!!!

Recording

https://youtu.be/AVUhWL1nw6Y?t=1151

As a contributor, I'd like to understand what are the plans for tooling so that I can better understand where and when to help.

As a user, I'd like to know what are the plans for AsyncAPI and when they plan to release the tools.

Currently in the .github repo we have a several very useful docs related to community like (eg) https://github.com/asyncapi/.github/blob/master/slack-etiquette.md. I think that we should move community-driven files from .github repo the community repo like:

• https://github.com/asyncapi/.github/blob/master/recognize-contributors.md
• https://github.com/asyncapi/.github/blob/master/slack-etiquette.md
• https://github.com/asyncapi/.github/blob/master/git-workflow.md
• https://github.com/asyncapi/.github/blob/master/repository-settings.md

Maybe these files should be copied to every repo - maybe it's a purpose that they are inside the .github repo, I don't know - but we should make these files available to as many people as possible, and right now they are hard to access.

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. Google summer of code status by @derberg
4. Job offers for AsyncAPI experts by @derberg
5. Q&A

Notes

1. Deadline for Google Summer of Code ends today, so all students need to remember to officially submit their proposals through Google application. We so far saw 10 proposals in initial phase but they need to go through official path. We also explained briefly for others what GSoC is in general
2. Community can now publish their AsyncAPI-related job offers on official AsyncAPI website -> https://www.asyncapi.com/jobs
3. We had a detailed explanation of what we are currently working on - the API of AsyncAPI parsers that should be breaking-change-proof and not tightly coupled with the structure of AsyncAPI document. Feel free read more here. We discussed more about the aspect of bindings in the API design and the best approach for now on it. You might want to have a look at this and that. Long term, how we implement the API is a subject for discussion, how to do the mapping of intends to the spec structure, as Mike pointed out others might be interested with some more generic solution that would work not only with AsyncAPI

Recording

https://youtu.be/ao81sT4XLDM

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM 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. Place for your topic
3. Progressing with decision/consensus on topic of Response specification in RFC, see discussion and proposal for more info here: asyncapi/spec#594 - @smarek
4. Collective work efforts towards 3.0 #157 - @jonaslagoni
5. Conference efforts updates - @derberg
6. if there's enough time asyncapi/spec#622 - @magicmatatjahu
7. Q&A

Notes

• We skipped Progressing with decision/consensus on the topic of Response specification in RFC, see discussion and proposal for more info here. It will be discussed at the next meetings. Please get familiar with asyncapi/spec#594
• We discussed an idea to have a separate meeting just dedicated to AsyncAPI 3.0 release that could help us organize the work towards this goal. Please join this discussion #157 if you are interested
• The summary from the conference is - all is good 😄 Presenters cards ready to start promotion of individual talks. We also kicked of marketing, but stopped on Twitter as it was not bringing any value at all.
• We talked about Proposal to allow defining schema format other than default one (AsyncAPI Schema). Maciej explained the purpose of asyncapi/spec#622 and what goods it will bring to the spec. We identified possible breaking changes and advised that might be easier to address with the proposal a smaller scope and focus one feature at a time. Also, suggestion was made to open a PR where it will be easier to see what proposal is changing.
• We announced winners of the Hackathon -> #165

Chat

17:08:05 From Alejandra Quetzalli : Holaaaaa Barbaño :D
17:08:05 From Lukasz Gornicki : asyncapi/spec#594
17:08:20 From Barbaño : Hi :)
17:09:58 From Sergio Moya : I’ll need to leave in about 10 mins! But how cool is to see all your faces :D
17:10:09 From Alejandra Quetzalli : Que bueno verte Sergio :D !
17:10:54 From David Boyne : Yeah sorry got camera off I’m sorting out kids haha whilst listening
17:11:35 From Aayush Sahu : Hurry up Lukasz! :D
17:11:39 From Alejandra Quetzalli : Haha the joys of fatherhood, Dave
17:11:46 From Aayush Sahu : with the recording*
17:12:37 From Jonas Lagoni : #157
17:16:20 From Sergio Moya : #163
17:16:57 From Alejandra Quetzalli : It’s so cool!!
17:19:58 From Alejandra Quetzalli : I like that idea!!
17:20:07 From Alejandra Quetzalli : A slack channel for changing to spec v3 could be so sueful
17:20:11 From Alejandra Quetzalli : useful*
17:25:00 From Sergio Moya : Have to leave. Don’t say anything Lukasz keep going with live video.
17:25:06 From Sergio Moya : Will keep up later
17:25:14 From Jonas Lagoni : Cya Sergio!
17:25:16 From David Boyne : Cya 👋
17:25:21 From Maciej Urbańczyk : Bye!
17:25:31 From Barbaño : Bye Sergio!
17:26:09 From David Boyne : If we git clone Jonas x 50 we can get the 3.0 release for Jan 🤠
17:26:16 From Alejandra Quetzalli : OMG hahahahahahah
17:26:21 From Alejandra Quetzalli : Git clone jonas
17:26:24 From Alejandra Quetzalli : 😂
17:27:29 From Alejandra Quetzalli : Thank you barbaño !!
17:27:34 From Alejandra Quetzalli : :D
17:29:15 From Lukasz Gornicki : https://drive.google.com/drive/u/1/folders/1QBwLkkcVSFWL125ZvA22_quiRNbXQeXg
17:38:05 From _acebuild : This is super awesome!!!
17:40:45 From Lukasz Gornicki : asyncapi/spec#622
18:03:38 From _acebuild : Thanks Guys
18:04:27 From Alejandra Quetzalli : Wohooo 🥳
18:05:18 From _acebuild : Lukasz send my swagggggggg
18:05:34 From Alejandra Quetzalli : All the SWAG

Recording

https://youtu.be/_AvA5cGmuPs

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. Place for your topic
3. AsyncAPI Hackathon and Conference progress - @derberg
4. Traits inheritance - current and future - @Fannon
5. Q&A

Notes

The meeting was entirely dedicated to traits (example Trait Object). Simon did a great introduction to the current behavior of the algorithm that handles traits merging when the AsyncAPI file with traits is parsed by the JavaScript Parser. We learned why it works this and not the other way (as composition). Simon explained his proposal (to support inheritance) and we discussed possible options on how to support all possible use cases. Please engage with the proposal and challenge it with different use cases.

How and what for do you use traits in AsyncAPI? Tell us!

Chat

00:15:12 Michael Staub: This is like javascript Object.assign() which makes sense to me. Does it do a deep merge though? If the message had ‘Cat’ in the array would the final array also contain ‘Cat’?
00:16:34 Sergio Moya: Wouldn’t make sense to raise an error on tooling whenever a property is found in both places
00:16:34 Michael Staub: That answers my question.
00:16:58 Michael Staub: Or warning at least
00:19:33 Michael Staub: Here is a similar API: https://www.npmjs.com/package/deepmerge#options
00:20:13 Simon Heimler: Here is the PR: asyncapi/spec#532
00:24:19 Sergio Moya: You can/should remove the all the required except chirp on the trait
00:26:50 Michael Staub: I think it makes sense as is, just needs to be better documented.
00:27:17 Michael Staub: I can’t think of a use-case where merging arrays would not be an code smell in the API?
00:42:41 Michael Staub: Perhaps the Object could have an ‘overrides’ field that specifies which traits ( or other sources ) that should be overridden?
00:42:50 Simon Heimler: https://jsfiddle.net/FannonF/yLsonr57/latest/
00:42:53 Michael Staub: So force the users to be explicit
00:44:41 Fran Mendez: I’m not sure I get it Michael. Mind expanding?
00:45:06 Michael Staub: Sure
00:49:32 Jonas Lagoni: That or create a trait object instead of relying only on JSON Schema for defining traits
00:52:25 Michael Staub: So create a DSL and ditch JSON?
00:53:05 Sergio Moya: HCL!
00:54:16 Hugo Guerrero: DSL for everyone! :)
00:55:02 Hugo Guerrero: That way we can secure our work for many many years
00:55:09 Sergio Moya: lol
00:55:14 Michael Staub: Decades*
00:55:20 Fran Mendez: Forever haha
00:55:30 Fran Mendez: XSD FTW
00:56:47 Michael Staub: If they coexist, then it will not be a breaking change, correct?
00:56:55 Simon Heimler: yes, I think so
00:57:02 Jonas Lagoni: Yep
01:00:39 Sergio Moya: Are u talking about FCL? FRAN CUSTOM LANGUAGE
01:00:55 Fran Mendez: You mean Extremeño?
01:01:36 Aayush Sahu: XD
01:01:37 Lukasz Gornicki: https://github.com/asyncapi/community/discussions
01:02:25 Simon Heimler: Ok, I'm not sure on the Breaking Change nature on a second thought. If you introduce a new feature that users start using and the tooling / consumers of the spec don't support it already it will break.
01:02:48 Michael Staub: thanks

Recording

https://youtu.be/FXgaLehiQcQ

The purpose of this meeting is to focus on contributors, focus on people that want to contribute to AsyncAPI Initiative but do not know how to do it. AsyncAPI Initiative is a large project, with lots of code, lots of docs, and many many other areas that need help, but it is not easy to start.

Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 4PM 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.

This meatin is a live-stream that goes to the following social media:

• YouTube
• Twitch
• Twitter
• LinkedIn

To broadcast the live-stream, we are using Restream. You are invited to join us live on the call and not only interact through chats on YouTube and Twitch.

Consider introducing https://issuehunt.io that is also integrated with GitHub. We could gather sponsorship for individual issues. It might have some disadvantages though. It would be awesome to get some input from an experienced user.

• pick some candidate-issues
• set it up and announce
• let's see if it gives anything

Proposal:

Forks only

Doesn't matter who you are, org member or not, all work on AsyncAPI should be done in Forks. PRs should come from Forks, and there should be no feature branches in the upstream.

Why

• A common practice for larger projects
• Get rid of issue of polluted list of branches, and zombie branches that were already merged.

What has to be done

• Clear instruction on how to setup your Fork so it is up to date with upstream master
  • explain the usage of Pull bot
  • explain how to set your local fork in the way that master is pointing to upstream

Disable Wiki and Projects

Why
We do not use this feature, let's just disable it for all repositories.

What has to be done

• cleanup if we have some old stuff there
• disable those features and document for future

Squash merging only

All repos should allow only squash merging of PRs

Why
To not have Merge pull request ... commits that are not very descriptive, but always have a commit message that introduces the commit. The advantage is also that you always have a final word on commit message before merging in.

Example of squash and merge, and just a merge

What has to be done

• set squash and merge for all repos and document for future

Introduce CODEOWNERS

It is a GitHub https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners that helps out to automate the assignment of PRs to proper group of people.

Why
You can, for example, specify that specific part of the repository can be only reviewed by a given person. If someone donates a template into the generator, he can become a main code owner to assure that only he/she can approve changes in it.
Code owners is also well integrated with branch protection, so you can set a clear PR requirement

What has to be done

• create those files in all repos, specify code owners and then set proper branch protection
• document for future repos
• make sure to have a setting that if there is a commit after approval, the approval should be canceled. Good tip from @fnobilia

Reason:
To encourage contributions and tools adoption, we need to make sure work done on those projects is done consistently and in clean way.

The purpose of this meeting is to focus on contributors, focus on people that want to contribute to AsyncAPI Initiative but do not know how to do it. AsyncAPI Initiative is a large project, with lots of code, lots of docs, and many many other areas that need help, but it is not easy to start.

Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM 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.

This meatin is a live-stream that goes to the following social media:

• YouTube
• Twitch
• Twitter
• LinkedIn

To broadcast the live-stream, we are using Restream. You are invited to join us live on the call and not only interact through chats on YouTube and Twitch.