AsyncAPI Community, 10 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: AsyncAPI SIG meeting 35 (November 10, 2020)

Description

This is the recording for the AsyncAPI Special Interest Group (SIG) meeting #35.

Attendees:
- Fran Mendez

- Jonas Lagoni
- Lukasz Gornicki
- Francisco Javier Antúnez Durán

Agenda & Notes: https://github.com/asyncapi/asyncapi/issues/459

Chat:
(no chat this time)

A

And jonas and that's all I can say in german.

A

That's it we're gonna have pretty short call, um not many people joined. Let us know somewhere on different channels. Why? Because now, during the call I um I know that antoneth had problems, finding the link and joining the call. I was also asked by lauren, if we've rescheduled now during the call, so it looks like the message got, lost somewhere or people outside europe. Don't know that europe changed the time zone, but at the end it's still 4 p.m. Utc this time did not change.

A

So it's always 4 p.m. Utc, but depending on your time zone, it might change, uh hopefully for europe, it's the last time this year and next year, we're not going to do those time changes thanks to european union, and now, let's uh let me let me just go to a few updates. I had on my list uh to share with you.

A

So first one is generator. uh You know that we're releasing release candidates. We were supposed to finish with risk on the day 10, where we are now on release candidate 15, but that's the last one.

A

That's the last one famous last words and the plan is my plan. Is so um tell me if I'm wrong um so tomorrow, it's independence day for poland, so I'm off it's cool right and um I was planning about uh to release generator one zero zero on thursday, because then I still have friday to release one zero one with fixes.

A

Any objections to do it on thursday.

B

No, why not on friday,.

A

Because I want to have weekend.

B

Are you, are you afraid of your code.

A

It's not only my code.

B

A

B

A

Next topic to not tomorrow, maybe on thursday or friday, we will also release the first. It's going to be a first release of the web component for rendering custom api. So we had a contribution from outside to the react component to prepare a setup to also generate a web component.

A

There's some react library that lets you create a web component out of the react component, which is awesome, there's a pr that is already accepted that introduces the release pipeline but again, independence day and magic who contributed to the pipeline is also out, um and I don't want to merge his pr because it's his code.

A

So, let's, let's wait for him to merge it.

B

Is there a better way to celebrate independence than merging the code.

A

Fireworks are now not promoted when you have celebrations, so no, we cannot merge it.

A

And it's pandemia, so we anyway cannot go anywhere. Oh you forgot about madinah.

B

Sometimes yeah because.

A

Life hasn't changed.

B

Too much to me, I spend the whole time at home anyway, so.

A

um Topic number three template for templates, um so you know I some time ago I started working on this like template. For templates, like you know, generator to generate something it. You have to have a template and to make it easy for new people to write, templates and and also unify the way, we're testing, for example, or writing readme.

A

I was working on this template for templates. It's a fancy name, it's them. It's called templates for templates because it's a github.

A

Template yeah and um the pr is open, it's already approved by salmon, uh so it would be awesome if you front or you yamas could also have a look, because the you know the the thing about this template is: um is that it's it's not just a um kind of documentation. It's also I'm introducing their uh integration tests with snapshot, testing and also unifying the template for for the readme for the template.

A

So maybe you would like to have a look before we release a first version and emerge the first version, and I just saw that basia contributed her review of the whitney.

A

C

A

Have to scroll through it, but yeah.

A

Would be awesome if you could.

B

So you mean that we just scroll it scroll the whole changes and then accept yeah yeah.

B

A

B

Do that come on guys, it's a matter of trust right exactly and I I prefer that it breaks, and then we fix it then to review everything that'll be now it's it's a big monster, so no it's only 26.

B

Only okay! So that's that's only 26 days of work, yeah.

C

Only 15 000 lines of code.

C

Good luck for him here I saw you oh.

B

A

And the last um just to share that the blog post about oktoberfest got monkey views.

A

Which is good, we got some good feedback on reddit.

A

But we actually also got got really good feedback on on on hacker news, which is good, which is good. I hope the discussion will will continue that digital ocean will pick up the content. I saw a few people from digitalocean liking the uh blog post on twitter, so I hope they will at least take uh forward this idea about having much better way for oktoberfest participants to to pick up the right issue, because I can imagine it's super overwhelming for for people like on.

B

Discord channel you.

A

Could see like links like people were sharing like, for example, they had eight reports in the organization they were sharing, like eight links to to issues from different repos, um um so it it's pretty clear that a simple solution as we had with excel sheet. That's a that solving a a lot of problem uh problems, but if they would have a a something better, some like one up for everything that would be awesome.

A

And that's it from my side and that's it, and we have perfect to finish anyway. So thanks a lot for joining, um see you next time.

B

See you next time and um by the way, we'll have a we're, probably having some good announcements next week so see you I'll leave there.

B

B