AsyncAPI Community, 8 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: AsyncAPI SIG meeting 68 (March 8, 2022)

Description

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

https://github.com/asyncapi/community/issues/285

Chat:
17:06:16 From Khudadad Nomani : Welcome aboard Namya.
17:06:16 From Abir : We just merged Spec Watcher last week
17:07:30 From Abir : We have lot of programs!! No worries
17:08:07 From AKSHAT NEMA : Yepp, there are lot of open source programs and events going on for our community
17:08:11 From Lukasz Gornicki : https://github.com/asyncapi/community/discussions/284
17:10:13 From Lukasz Gornicki : https://github.com/asyncapi/community/issues/245
17:12:46 From Namya LG : renaming would be a good idea
17:12:48 From Sergio Moya : +1 to rename it.
17:13:08 From Abir : yeah we can
17:13:50 From AKSHAT NEMA : I think we should rename to something precise which give good impression to anyone who is joining, instead of just SIG.
17:14:54 From Siham TAHI : For me I saw the purpose of these meetings but I did not know the meaning of SIG so it's better to change it
17:15:20 From Abir : `AsyncAPI Public Call`
17:15:37 From AKSHAT NEMA : yepp good one from Abir
17:16:15 From Khudadad Nomani : +1 for "Community Meeting"
17:16:44 From Lukasz Gornicki : https://github.com/asyncapi/community/discussions/categories/asyncapi-conf-2022-organization
17:18:18 From Abir : The situation is bit weird, due to war
17:18:56 From Abir : How do we avoid over engineering...
17:23:45 From Lukasz Gornicki : https://github.com/asyncapi/website/issues/453
17:24:50 From AKSHAT NEMA : https://github.com/asyncapi/website/pull/609Where it is implemented

A

Good evening, uh good morning, uh welcome to asean epi community meeting, um I'm mukash kunitsky your host and uh I I missed it um and um we as usual, uh just a reminder for others that this meeting is being recorded um for a transparency reasons um to upload it to youtube. Right after before we jump into regular um items from the agenda um usual question to the folks that are at the meeting.

A

Would you like to maybe ask some question upfront or introduce yourself if it's your first meeting, um that's the best moment to do it.

B

Hi, hello, everybody, I'm I'm namiya. This is my first time attending uh the meeting and I just started working on an issue recently, uh so just wanted to understand a little more about the whole ecosystem and what how it works.

A

Awesome welcome, as far as I recall, you're working on this um links, validation right through code flow.

B

A

B

Link validation.

A

Yeah yeah, but it's related to open for cm awesome. Wow. Welcome thanks for joining.

C

Anyone else uh we also merged spec watcher last week, uh I think in under async api calling, oh yeah yeah.

A

Yeah and shout out to.

C

Message for that he'd had a lot of reviews.

A

Yeah definitely I was out so he had to be double himself, so I could have a decent holidays thanks magik.

A

So, um let's jump into the agenda, so the first item on the agenda is uh google summer of code.

A

Yes, so um we got rejected second year in the enroll, but the problem is that even postmodern got rejected, so our backdoor from last year will not work this year, but yeah. um Some of you already saw the discussion on github, so we are not much worried. Actually, I think it um because of this situation. We will actually start something much better than than than g-suck something more um more flexible, so um yeah, so just for others that um do not know what I'm talking about um so yeah we applied for google summer of code.

A

We got rejected, but essay as a response to that, um especially that we saw so many people um joining before this final announcement and then contributing a lot. um We want to work on a kind of asking api mentorship program um and um yeah like I'll, just share a link to the discussion.

A

um It's something that we will still have to um put under the voting of technical steering committee, because it's about spending money of the collective but yeah. I don't expect any any issues with that. Really. So, um if you're interested still in taking part in this mentorship, even though it's not under google brand, it's not so much um visible to others.

A

But you still want to be with asking api community, then yeah. Please leave your comment there under the discussion, so we know how many people are interested and how much how much we have to prepare and help to um yeah suggest some answers to the questions that fran posted in the discussion um so yeah. That's it from my site. um Any questions in regards to that topic.

A

Nope good awesome, so yeah, um so we will have two programs this year, ambassador program and uh and nothing api mentorship program. So yeah again many things to do um next topic on the agenda, just um just a question and suggestion. I will anyway open separate discussion too and yeah not make decision on the call. But I wanted to hear your opinion about this meeting. So um you probably heard, but if you didn't, I'm gonna share a link. So there's a topic.

A

I I'm focusing on now it's uh it's called meeting as a service because we're organizing more and more different meetings. Different people are responsible for these meetings and.

A

And it doesn't really make sense to have me as a um as a bottleneck here that um organizes everything um and uh I'd like to like make sure that um whoever wants to organize meeting have it regular et cetera. It's it's all documented and automated as much as we can with available tools, but yeah. The most important in regards to this topic is that I'd like to use the opportunity that we will like we will have new calendar.

A

We will have new new zoom accounts like um basically, all the links to all the meetings will will be refreshed because of this automation, um because still we're using franz accounts that he's paying for like we're using. um I think the the calendar is associated uh with his private account, so we need to get rid of these things. um Have them like asking api official so because we're changing all the links, um and we will also have this live streaming of all the meetings um possible because we tested it already with some meetings.

A

So I was thinking that it would be a good moment to rename this meeting that we're having now, because now it's called async api seek meeting.

A

But I on my own even stopped using this sick name for some time, because this acronym, I think it's called an english acronym um like it's not so well known, um especially if you're, not in cncf world, uh so like sick means special in uh or sig means special interest group. But I was always referring to it as a community meeting, because we we usually talk here about like um community-wide meeting uh community-wide topics uh and yeah.

A

So did you ever care about the name of the meeting or were you confused by this come seek meeting, or what do you think? Would it be bad to to rename it? What's your opinion folks.

D

E

I think it makes sense actually.

A

Thank you. um So that's one thing, and the second thing was that this meeting was always just available through zoom, um but I noticed when I'm looking on these meetings that have um have zoom presence, but also streaming that it enables more more people to to view the meeting like not everyone can always join.

A

uh We notice that like, even though we try to have meetings in different time zones, uh there are people that cannot join because they have to attend some other meetings because they work in corporation and they uh they can't uh leave them or they just have something else to do so. They could always watch a live stream and just listen to the meeting to know. What's what's happening and um what's like?

A

Do you have some different view here like because I was thinking that actually all the meetings that we do should always be live streamed, um because the advantage also is that it's automatically uploaded uh to youtube um and other platforms. We don't have to really do it manually.

A

So um I think that in the past somebody said, like it's a risk that less people will join the meeting but yeah. I don't think it will happen. Looking at the dry run, we did already with some meetings, but yeah um anybody has a view on this. One.

E

I think there will always always be some people that find it intimidating and that's kind of unavoidable, but I don't think it's. I don't think people will find it more intimidating than what we have now. So I don't think it's gonna be a big problem.

E

Because you're talking about streaming, it right like with restream.

E

What did I misunderstand.

A

No, no, that's that's good. You understood it well. I was just reading also a comment from um about the sick name, uh that it was never like clear what it means so yeah, uh so yeah good, um but yeah anyway, I'm gonna open a short discussion like for a week or two to see. um If maybe there are other ideas, maybe it should not be community meeting something different, um because there are also like some different communities to office hours, whatever the name is but yeah.

A

And last from my site, an update because we discussed it before my holidays is asking api conference.

A

So um before holidays, I wrote to the um to a person from linux foundation that was talking to me about the um open source conference open source summit in dublin, um but she never got back to me uh and it's like um yeah four weeks uh already passed.

A

So I'm not sure if that option will be any longer available, uh but yeah. Let's, let's see um the most important is that like not much discussion really happened.

A

uh These are strange times now so um I'll just like to remind you, um I send a link to the discussion uh category. So there's a dedicated category um related to us in api conference. You can see also previous previews and categories from last year. What topics we discussed in regards to the conference. So if you, if you like to actively participate there, then please feel free to open any discussion and and and talk about it. I also wrote a reminder, email to this person from linux foundation, to to check where we are.

A

And- um and I'm not sure how like because of the situation in ukraine, if the option that I wrote in slack before my holidays about the the manga museum in poland, if anything in poland will be feasible uh for a conference in next months, so uh so yeah, um please join and suggest um what options do we have there like if it comes to the location of the conference, because we definitely should try to do something in person but yeah. Now it's a matter where.

A

Any comments on this one.

A

Yeah exactly so yeah, um that's it if it comes topics from my side and anyone has some questions. Some other topics to talk about.

F

I just heard from you that uh we are having the france of private account to do various things like to have the calendar invites or to to do the production based of the website, so we are making the softwares on it. So is everything on the front private account, because I do have something that I'm working on, that something is back and the production it means I've discussed with anything marching, but I haven't discussed with, I think you and uh friendly to it.

A

um Could could you rephrase, maybe because I there's an echo.

D

A

Side because what you're saying talking about website and but what do you mean by backhand for the website.

F

um I'm just talking about actually it's related to the docs, so feedback from that. Oh.

D

F

If you as discussed before that, we can have a google sheets for it and I just made a br for it, but it requires two additional certain environment variables. So I just have to confirm that uh on which netlife account it is it's on france, private account or do async api. Has some official account for it taking premium moment.

A

But uh can you remind me, did alejandra already shared her opinion? uh If we should do the github discussions or not no.

F

But she hasn't reviewed anything right now: yeah, okay,.

A

um So I'll talk to her to have a look, um I think like mache. Can you uh can you help me out? Do you remember, like this github uh token that we have on netfly uh yeah.

D

A

Is it? Is it france, private token? Is it not? uh It's.

D

Bots, okay, it's probably the same as the workforce. I think.

A

Yeah, I'm not sure because he was.

D

A

D

A

Yeah because he was, uh he was adding this token when he worked on shape up and when he worked on shape up. He was not involved in ci works and I don't remember him asking me for token and also he had to have some additional um zen hub permissions. So most probably he has his private token yeah.

F

Yep you actually, I tried to deploy it on my personal attitude account, so it asked me for the various permissions that environment ends has been used to, so I think he has must be having some personal problems too.

A

Yeah but but also the thing is um like, for example, when you, when you have a pull request on the website,.

D

A

And you uh you, you want to see a preview of your build. um It's not like. Whatever token we will have provided in the environment variables, it will not work uh because netlify disables them so um because of security reasons. um So.

F

That's that's what I try to just module out um the suggested me to deploy it on your account and have a trial on your local development production as well. So I tried it that way. It doesn't happen in that way that they'd ask for something else and have given many address to them.

A

Okay, um so yeah I can. I can just promise that I'm gonna talk to alejandra, because it's um it's the most important first is that if she's, okay, with changing the approach from uh to github discussions and uh and if it comes to token, I have access to asking api port. So I can add it to the to netlify account just to make sure that we have the the correct token there um but yeah, but still for testing.

A

um You need to test it out on some uh private organization.

F

I think it's a no problem to it. I already twisted on my pc just creating that env file, so it worked fine for me, but it was. It was just my local environment that I tested okay, interesting.

A

Okay, cool but yeah we're in contact. I will open up this issue as well, so I don't forget.

A

It was feedback card right.

A

I'm also gonna share a link to the issue for folks that uh are not so familiar with this issue, so we can have a look. What um akshat is working on.

A

Okay, um so yeah, and just to summarize, I'm gonna create this token uh this week for sure and let you know what's the name.

A

Of the environment variable.

F

A

F

Should first uh contact your alarm draw to just summarize it to what exactly we should be doing. Yeah.

A

That's easy: I have a meeting with her in 30 minutes so.

A

A

Any other questions topics.

A

No, you sure, because next meeting is in two weeks.

A

Okay cool, um so thank you a lot for for joining um yeah the I will upload recording, maybe even today, because it's it's going to be short so should be able to upload it quickly and yes, see you in in two weeks.

A

A