AsyncAPI Community, 24 Jan 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Community Meeting (January 24, 2023)

Description

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

A

B

Just few hours.

C

Sorry, sorry, are you in college I.

B

Said yeah I'm in college right.

C

Now, like India, oh so no no dealer.

C

B

C

Have dinner with family.

B

Yeah, no no dinner from the family. It's like mess.

C

Yeah, it's always messy, probably just have some junk food.

B

Exactly but yeah I was registered to The Institute mass and from there I get my daily means.

C

Nice, nice.

C

uh So, let's see if some people other people can join I'm, pretty sure Jonas is gonna join us today. You'll see how some topic, um speaking of Jonas, exactly.

B

Okay, perfectly: let's wait for him.

C

Oh, hey, Iman, hello, Naomi,.

D

C

No I'm not I'm a horrible. What's going on somebody help, can you hear me.

C

How you doing man.

E

I'm doing good nobody.

C

Yeah is it good, I was just talking about you. I was like you know, let's wait for you and us to join and boom. You know summoned you, you were eavesdropping.

E

I wish just good timing, I guess.

C

Yeah, perfect timing, um so I don't think we have to wait for anybody to just like study meeting. So, okay folks um welcome to today's community meeting.

C

um You know we all know the community when it is happens, bi-weekly uh one in the morning and one later in the evening, which is currently happening now. uh Okay, we have someone joining Jonathan foreign.

C

A

You doing good.

C

How are you yeah I'm doing good too thanks for getting into the school first time joining yeah.

A

First time, uh first time, cool.

C

Cool um looking forward to seeing you in more meetings.

A

See how we go, hopefully yeah.

C

Okay, we have Pedro.

C

C

C

Hey hey, do you hear me? Hey man, yeah and I can hear you how you doing nice to see you yeah me too nice to see you. You can see. You all are looking amazing. Looking fresh.

C

Texted and they call uh so I I hope we have a fun conversation today, uh so without no further Ado I'm gonna get right into it, um so you don't have some things he also wants to discuss into this community I also have some few things. I also want to discuss and probably share so yeah.

C

So the first thing I'm going to talk about uh with this coming to my team, is actually uh the AC kpi previous, um oh, which is currently still ongoing, which is the ckpi 2022 mentorship program, um which is which is pretty fun right so far. You know I get to like organize these mentorship program, which I'm also like oh, not am I, am I breaking.

D

C

Yeah a little bit: okay cool, oh sorry, I hope. My internet doesn't me up today.

C

So the the mentorship program for financial is still ongoing, which wasn't supposed to have ended, but due to some reasons, I would say: I have some folks that are still working on the projects, uh but we have um a few folks that have completed their project, uh which includes um actions is on the call and also um a bill who is not on the call really amazing folks.

C

um So I would love to like make uh give the mic to action. To just now give us a brief overview of how the program went like so. Actually do you mind.

B

Yeah yeah perfectly so like a Singapore mentorship program, I always say that it has something new for you means like you, do want you, but whenever projective product idea you choose, you always get to learn anything out from it and I always compare that. Mr I should say it's a comparison. It is a like a G-Shock. Everyone has a hype about Google's summer of code, but many of them do not get selected for that. But yeah. This program is really awesome.

B

With that my mentor was Lucas and, along with that, I have Machi was guiding me in the entire process. It was a really a fun and interactive sessions with them to never felt I, never felt that there was a like burden type of internship going on like that's yeah, it's open, so it's cool, it's a learning process and everyone has its own uh particular time to do the contributions with it and, along with that, uh the ace like he's the coordinator of the program always he's very cheerful to take uh feedback from us.

B

Have we do have many of the coffee talks in the in the evening in the in the meetings that happens twice the month? That was why weekly so like it's a very fun program, and then we are hoping for the next year mentorship program to be much more fruitful and learning for everyone.

C

Yeah, that's amazing I'm. Actually, thanks for the quick um shout out, which was interesting so actually has completed this project. Amazing folks, interesting project is also now in Medina. So he also like part of the comment TSA members, which is really fun um so talking about the mentorship program. So we are also like in the process of organizing um the expenditure program, which is in 2023 executive mentorship program, so I'm going to share a link uh about the request. I opened uh related to the program. Give me a few seconds.

C

So I'm going to start a discussion, also I'll tag, all CSC members or if you're also interested. You can join the discussion about the because the previous mentorship program, the 2022, which is our first mentorship program initially, so we don't have any um rules said we don't have anything casting Stones. We just wanted to like do it and see. If we can do it right and we've seen, we can do it, which means we can even do a lot small.

C

So this year we're gonna have a couple of rules, uh so we sold a couple of ideas from how Google season. Of course, some of code does a thing. So we tricked it and also like hitting our own thing just to make the next membership program much more easier and flexible. So here's a link to it for request I opened um concerning uh so I'm gonna show it in the charts and also in YouTube, uh can I do that.

C

um Okay, I shared it on YouTube also so there is request, is actually um main trying to like organize the directory um called mentorship under the Community repository right. So we have an alternative to the mentorship program and the previous ones, the running ones and the upcoming one type. So you can go to the Asic API for order under the mentorship progress then check out the 23. You can see. I have some rules, so you can go get view it and also share your opinion to say: oh, we have someone joining okay.

C

So so you can also share your opinion on what you think we can uh do or not do and I think I. Think Jonas you. You should have some mentorship project ideas for this year. You know you, you didn't Mentor anybody last this last year. Right, yes,.

C

Unfortunately, yeah, oh, you did oh cool. Are you definitely gonna get selected this time around? So we have a couple of. We have a couple of our mentors uh guidelines also. So if you want to be a mentor, you should also like go check it out to see. If there are some things you feel needs to be changed. Also so I'm gonna also study a discussion on target Hall to also like check it out. So that's for later this call so the next the mentorship program is coming.

C

The next 2020 English program is coming so I'm actually super hyped. You know looking forward to it and I also think um folks, like akshat, which were the previous uh mentees, also the governmentals in this um common program and also talking about mentorship programs. uh We also like in the process of participating in the winter cold. If you have attended the previous Community maintain I, always say some Spanish about that.

C

So we have a lot of folks, like you know, coming in from Winter of course saying they want to participate and yeah they're going to participate, so we're just waiting for the program to start um they'll pin some updates update store by like they've. Only just so many things about the deadline, dates and stuff which I know I, don't know, I, don't like I, don't know why well I think it's for the good of the community so once we get um green light from them, so we're gonna kick off the hey!

C

Oh hello, how you doing yeah I'm fine ah cool, your first community meeting.

D

C

I come again. Your first comment is amazing: yeah yeah yeah. Do you want to introduce yourself.

D

Oh yeah I'm, pranama, madhu I'm from India Kerala and like I'm, a participant of intro, Sport and I, have submitted a proposal regarding the issue that was mentioned in GitHub yeah and Rusty.

C

School ah cool, you can say, he's talking about winter of code, nice. uh You know um looking forward to seeing your contributions and I hope you get selected for this program and if you don't get selected, don't worry man. We have a lot of issues you can know you can work on, so you don't need to get selected to become a contributor assistant API right. So that's it about winter of code without food is starting pretty soon and I'm also super hyped.

C

You know we're gonna be participating in a lot of uh open source programs this year as much as we can just like encouraging contributions, foreign.

C

About mentorship right, so, if I go on and take the whole time, I would love for you to answer. My call me: hey yes,.

C

So you have a couple of um discussions.

E

Yes, let me find it.

C

E

Thank you. Thank you. Thank you.

D

E

Right, let me share my screen with or not can this can you give me access to share screen.

C

Well, I just see you, you want to be organizers.

C

Making you co-hosts thank you.

E

Okay, it's gonna be a rather technical question, but I kind of want to see. If any of you have a an idea of how to do this so for whenever you use async API, and you want to generate data models, for example, something that represents your payload.

E

We build a tool called Malina for it now Molina integrates with the CLI at the moment, but it's rather hard to provide the full features that it that the tool enables, because it's a lot of its are basically callbacks that enables you to customize the output in a very detailed manner.

E

So the idea is to have something of a configuration file, a JavaScript file or typescript file that, where you're, where you're able to use all of the features, Within modelina um while still provide this easy interface through the CLI, for example. So for example, this could be if you wanted to generate typescript models. But you also want to use unions instead of regular enums. It could be.

E

You want the models to have a specific indentation for whatever reason um or even change, some of the type mappings that say that, instead of an any type, that's the normal one, then maybe you wanted a number or something completely different. So all of these things could be done through this configuration file here.

E

However, each of these specific configurations are just for one generator, so, for example, this configuration file in this scenario would only be for typescript, for example.

E

So if you wanted to generate models for say shop instead, you would have to have a separate files or we could kinda wrap everything into one specific file, for example here where you specify something for typescript, something for c-sharp Etc.

E

So my question, I guess, is: do you have any or have you seen other tools that does this differently when it comes to configuration files or have any ideas that might be better than what I can come up with any feedback is appreciated. Let me link you some links as well.

E

So that's this one and Marlena itself and then we have a pull request, which is like kind of at draft Early, Access uh kind of stuff to see what fits and what doesn't. But yeah have it to take.

E

B

E

uh Yeah but that's kind of my question but uh or what I wanted to discuss or bring up, but it might be a bit too technical for just this meeting. Maybe.

C

Hey um so no questions, foreign.

C

Yes, so I'm talking about modelina, uh I, think uh Madelia also like I you, the project also needs contributors right.

C

um So if you're interested in contributing to this project, uh don't forget to check it out and uh you know, go through a list of issues, and you know um eonas is always helpful like it would eventually help your house if you need any help concerning the projects, because it is always openly so for sure cool. So, uh if there's no question about modelina uh or this discussion, yes, we have to like go to the next step. So on the next thing is um I, don't have any next effects.

C

There wasn't more on my agenda, except for the new um um I think at the new um release right so I'm currently voluntarily for the um next smkpi um spec 2.6 uh release uh yeah. So it's currently a work in progress and and I think it's generally like I feel like it has to be done like completed this one like what what will happen. I have a question which is obvious right. So I still like asking this call. What will happen if you release get past January.

C

C

You should know sorry.

E

C

Like I was just asking right, so we have like these months of release right, so I think uh January, um I, think September, so like I'm, just asking it like what, if we don't get to like make this release in that particular month, like what happens like maybe something happens, then we're gonna make the release nothing.

E

It's just a skip release, so it it kind of depends, there's no forcing it because we have the next release as well, which is in April, I, think end of April. If I recall correctly, so you can move your uh 2.6, you can easily move the release schedule for that and just include more stuff. uh It's not going to be any issues with it.

E

So yeah like a skip. Please it's no worries. If there's no there's no need to change stuff just to change stuff right so.

C

E

C

About just minor minor release right. So what if it's a major release, like maybe 3.0.

E

So, for so 3.0 is gonna happen. We have a bit of a different release schedule for that, because we want all of the tools to be uh adapted to the new version as well, so you can switch over to version 3 of async API and use all of the official tools anyway, so you shouldn't miss anything and you shouldn't be restricted by it, um and for that reason we have somewhat of a freeze period so from the end of February next month there are no new changes to this spec.

E

So all of the changes should already have happened by that point or at least be right uh almost uh merged by that time. So that means that from February up until the release in June.

E

um The only thing that's going to change our minor patches to the already existing features or changes to the tools themselves, and we, of course, also are trying to work out how to help migrating tools. Let's say that you're the code owner of a specific tool- and you want help uh in terms of what changed and Etc we're trying to to provide somewhat of a meeting for it as well, something like an office hour, but it's not quite clear what it is yet.

E

But I think that answers your question right. I hope.

C

So yeah, of course, of course so um I was I was thinking. I was like what, if what, if you just means, at least like people, are going to jail? No just kidding clarification.

C

Yeah, nice um so I think what anyone has anything you want to discuss, because I don't really have so much change on my agenda. Pedro looks like you have something in your mind: let it out let it out.

E

So I actually have one more thing. Oh.

C

E

But otherwise jump in because this.

C

A

Happy to share something to you sure if, um if, if you're interested.

E

A

um So I'm I work at a company called trigger mesh I'm. A product manager and Trigger mesh is like uh an event broker, which uh ingests captures events from lots of different sources. Standardizes them transforms them and then lets you. Filter and Route them, deliver them to external targets. So it's kind of like event, driven integration um and I've, so I've been I've, worked on like a Swagger.

A

A lot in the past in other companies and I've always been a bit sad that at trigger mesh we're not um working more closely with the async API stuff, so I'm trying to work on like a little demo at the moment.

A

um Maybe I can just show it's really work in progress. Actually, I can't share my screen. I, don't know if that's something I can do yeah.

C

A

Okay, just to show you my idea- and maybe you can tell me if this makes sense technically or from a community point of view, but uh so where can I start here.

A

Okay, so I'll just share this desktop.

A

Okay, so can you see this diagram yeah? So this is an example of the kind of thing you can build with trigger mesh. um You know ignore the async API piece here, but I've got a bunch of like order, Management, Systems uh and but there's there's lots of different ones and they communicate through different protocols and systems. So, like some sender, some send orders in in a rest, API some send them on an sqsq, some send them on a Kafka topic.

A

Some need to be pulled by HTTP and the idea is that with trigger mesh, you can easily ingest all these events, transform them, standardize them, and then you can route them to other places like Kafka topics or whatever, and so what I'm trying to do is essentially a lot of the sources that we can ingest.

A

Events from you can describe in an async, API file and so I think it'd be really cool to take to write like a parser which takes an AP, async API spec and generates trigger mesh components that can just automatically start ingesting those events and putting them into this broker, and then you can do stuff with them um and I think, because the async API, if the definition is well defined enough, um then there's no reason why we I couldn't do that right and um and Trigger mesh is a fully open source product.

A

So you know this is not generating to some Black Box commercial thing. It's a it's a tool where um all these components the broker the sources, the targets they run as components as as containers, um and you can configure them how you want you can run them on Docker. You can run them on kubernetes anyway, that doesn't really matter.

A

So what I'm trying to do is I'm taking an async, API spec like this one, so I'm, not a developer, so I'm, you know doing this whole passing thing is it's kind of tricky for me, but I've defined a Kafka server um and I've got a channel which is orders uh and I'm saying you can consume you can subscribe. You can consume orders from this channel right.

A

So if I go back to my diagram, that's this topic here, where I can read orders from it later on, it'd, be cool to add other types of sources as well, and so in the past or the idea is you know, you're gonna, your eyes are gonna bleed if you look at this code, but it's the first time I even try to run to do anything in node, but if I run, if I essentially run this password, it produces this file, which has some TM TM cuddle. So this is our command line.

A

Interface has some instructions, and so, if I take this now to the terminal and I do TM control create broker so it'll create a broker which is like a an event bus that you can send events into and then I can copy the command for creating the Kafka source.

A

So you can see it's extracted all the data from the async API spec, okay, so it's creating that creating that source and so now, if I do TM cut, I'll describe I, have a broker and the source is getting events from Kafka and putting them into that broker.

A

I can do TM cuddle watch in a different terminal to watch the events coming in and then I can go to my Kafka broker here, which has a topics, a topic called Auto. So this is the broker, that's actually being exposed by the async, API, spec um and I can go and like paste. Let me take some an example event um like this. For example, I can publish this into the broker and then, if I come back to trigger mesh I see that I got the event right.

A

So the idea is that, in a few steps you can ingest events from these sources defined in an async, API spec, and then you can. They come in as a cloud event. So Cloud event is a standard which has this like standard metadata about the event. So now, I can, if I want to I, can start doing uh like creating a trigger, so I can do create a trigger for an event.

A

Type and I can like copy this type here, which is the Kafka event, and then I can send it to a Target like a I can send it to another Kafka topic: I can send it to sqs I can send it to an HTTP service, whatever I want um so I'm just experimenting with this to see if it makes sense, I think technically, it's doable and like I could generate um interesting stuff from lots of different things defined in the async API spec, and then my bigger question is like.

A

Is this something that could be interesting for users of um of async API I'm? Not sure? That's the biggest open question for me, and that's what's interesting to me, is to see if we can, if our product can be useful for people who are doing async, API.

A

Yeah I don't know if anyone has any reaction to that I and by the way I'm using the passer right now, I tried to use the generator and I I. Guess I, just you know, hit hit some configuration errors, so I couldn't get it to run with my own templates, um but that's yeah. That's a detailed.

E

Yeah, it sounds like a perfect fit for sure. It would be a really uh uh awesome to see. How uh can you bring up your presentation again, I think it or Excel yeah so for the event, consumers, um and even for the producers for that matter, if all of them has so, for example, for the app and the analytics apps, if all of them has specific async API files that defines their behavior, it's rather easy to to generate the code. That makes it much more easy to consume those events.

E

So, for example, let's say that I am building the analytics application.

E

All I have to do in order to consume from all the CU fashion is called as one function from the generated code and that's it and then I get the I get the message payload in a structured way, I get the. If there's any parameters in the topic or headers Etc like just for one liner implementation, kinda, and then you have everything. But of course that depends on how well described it is the async API, of course,.

A

Yeah, that's kind of one of the challenges I'm having with async API is like who, who is the person we're addressing in in the with the description right because I I'm I'm trying so my my instincts, which may be wrong, is to describe these event sources and think about the like devops person, who may need to like ingest this data and then do something with it like push it to these topics, but you're thinking more from like the application developers side and how we can help them go faster right.

E

Yeah and there's also different perspective of persona, so to say, because um there can be different levels of who wants, which kind of information that is described with an async API. So there's, of course, the the consumers of the events, but there's also those that configure everything within a trigger mesh. I could imagine where it's.

D

Like you still.

E

And you might not even want to to specifically use async API for that, but you can have different personas within a company or within a team that that sets up different kind of things within the async API file. So someone describes the topics or the channels, and someone describes the uh the message. Payload like it's, not an exact science. Yet because it's not something that we have discussed or have been discussed much yet and but it's going to be an interesting I am discussion to have.

A

C

And I would advise you um General time to also like start a discussion around these on this KP education up top yeah, okay, I'm, going to show you a link so we're gonna start this session.

A

On GitHub, okay,.

E

Yeah I think the the those kind of discussions are really important to have, because, regardless of whether it's for trigger mesh or in any other company, those definitions of, if you have multiple personas, what are those personas that are.

E

For example, if it's a product manager, what do what do a product manager want to change in an async API file, and it can even be, of course, an abstracted uh perspective from from async API for that matter, um so yeah. Those are. Those are some interesting uh and.

A

Is there? Is there right now like uh I guess this is kind of tricky to answer, but and I can probably do more research, but uh in terms of who are the people using async API today and what what do they use it for is it is it? Is it I mean because I come from the world of swagger and OAS right I did a lot of work on that, and so that was like you're defining a rest API so that consumers can consume it more easily.

A

Like it's much more simple, whereas here, like you, said, there's different actors in the system, so it can solve a number of different problems, but is there? Is there one perspective which, which seems to make more sense in the world of async API than others.

E

I, don't think we have mapped it well enough at the moment, because.

E

Like generally, the async API file is used for one application, so you have app, you have analytics, you have all a management system. You have those multiple order, management system that each of them Define a specific behavior, or at least that's in version three, that's going to be it where they Define what they, for example, send or receives yeah um so yeah. Another good discussion to have cool.

A

Thanks a lot for the feedback I'll keep playing around with it, see where I go where it goes.

C

It looks like a very, very interesting projects.

C

D

C

A link on Zoom, so just in case you want to start a discussion.

A

Sure thanks a lot foreign.

D

No not so far, nothing anything new to that from my side.

C

E

So this is really before anyone should even see it, but I still want to show it, and maybe you have some comment for it so, and especially since you're here, actually um so for I've been having some trouble trying to map out where async API is missing tools or where we are missing, features for that matter within tools, um and we have this new tool dashboard, which is super awesome, because it it kind of grabs all of the tools that we have and externally, as well and kind of have this programmable interface, that it describes exactly like something that I can grab and experiment with.

E

So it's kind of just like a Json file right that describes different things but I'm thinking about how we can Elevate the roadmap in order to display which kind of features we are missing uh or I guess, there's different kind of perspectives for this, so one I want to be able to describe which tools exist. That can help me build my application.

E

It's kind of the end User, it's those that build applications, analytic platform, whatever it kind of, is, um and we have all of these different tools for them that solves different kind of problems, but all of them kind of elevate towards a grouping of uh or within a specific stage in development. So, for example, you have the sign where you have to create your async API file. Then you have developer, you develop the platform, all the the application itself and etc, etc, etc and I'm not set on any of these groupings.

E

It's just what I came up with at the moment. So the idea is that we kind of distinguish between if you want to build an application or whether you want to build tools to work with async API files.

E

So this is kind of the integration part where it's like I want to build. It could be. It could be trigger mesh, for example, that want to integrate with anything API and support using apis as a format. They, then we have tools that you can integrate with that. You can integrate into your platform to make XY set easier to to solve.

E

So the ideas was that each of these tools then has different kinds of so this is kind of like if I double click on this design grouping, it gets into a much more specialized view where all of the tools are so this could be. If you want to visualize whatever is defined within the async API file, then, which kind of tools can you use and also which kind of Standards?

E

Because well we have async API, of course, but we also have how you define the scheme or the message payload that can have different kind of formats as well.

E

um But then the idea is that if we can create kind of like an interactive tool that can show where connections are and where they are missing.

E

In order to say we are not that well supported for angular, for example, here, let's say that none of these tools, uh integrated with angular, is rather easy from our perspective to see okay. Well, maybe there's not enough traction like users that wants it. That's one thing of course, but it also gives us the possibility to see well we're kind of missing that uh that arrow in a sense, it's not there, because none of the tools that we have uh um can be used within.

E

As that specific technology stack, um and it's the same with, for example, develop. Then you have more boxes where it's like. Okay, I I'm using um I want to generate code for typescript, which tools supports generating uh typescript code.

E

Then you can rather easily focus on typescript and see which tools, support that, but also see okay, but I have typescript and I want to support Nets. That's my technology stack or it can be Kafka for that matter. Then you can also see- or you can add those to us as a requirement, and you would have an easier time figuring out which tools you can use or integrate with that supports your unique use case, and it of course also shows.

E

Let's say that we have a protocol, that's not supported new protocol, but then we might need to put some effort into enabling that integration or that missing connection in specific tools.

E

um So yeah I'm, that's kind of what I wanted to show, because I don't have anything else um and it's still a work in progress. I don't think it will. The plan is not that it will replace this. The plan is for the moment that it's gonna imp or live next to the roadmap and vision in some sense, maybe another tab, something something um but yeah happy to hear your thoughts. If you have any about them,.

B

Yeah I do have like to be honest. This was a brilliant idea to me. It's like having a certain road map where a certain user can have or can get the knowledge on how what are the tools that he can use to either build their application or how they can integrate with it, because many a times like in that, even if we see in the tools dashboard, we are not clarifying the things very much we are to getting into the details like it goes with languages Technologies, but yeah.

B

There are certain view that we are missing um previewing those categories like either they are building the tools or they are helping integrate with that I think. Yes, we can do this, while on the roadmap side uh with an animation yeah. Quite a difficult means like quite not difficult task, but um it will be a quite creative I will take uh some time or even if we make the this particular task or issue for any particular program or any particular build task like in inside main distributor.

B

My if I remember like we do have a drag and drop something type of that interactive uh issue. For the assembly pay mentorship program right, yes,.

E

Yeah I think you are referring.

B

To yeah yeah yeah I mean it's like like these type of interactive types, we could make it and yeah. This is by the type of idea you presented. It is quite good to me like we can have but yeah the person who is making. It uh should also have a good knowledge of the tools that are being currently being there used in the Sync API I.

E

Think I think the mapping uh between tools and and this overview is one thing, because that can happen in uh not parallel, but it it doesn't necessarily mean that it's the same person. That does it um because many of these clarification- things for example, which Protocols are supported or with serialization libraries, are whatever other parameters there is um we kind of need to map them out in some sense.

E

B

Point, do you want do you? Do you want to make something like of.

C

Services, this is nice.

C

E

B

Yeah, it means like um I want to know that. Do you want this interactive session to be something um automated like just like? It is for the tools one yes,.

E

That's the idea: yeah I'm kind.

C

Of thinking that it's I have a question uh-huh, so what I'm thinking is right, so um so, firstly, like technically I feel we should find a way. It was right here we're talking about tools right, so why shouldn't it reside in a domain. That's related to tools right so I come into this kpi website. I I need to check how the tools work or something where my mind first goes: it's not a roadmap right. It basically goes to tools right.

C

So when I click on tools, what I see is the tools dashboard right- and this is a dashboard right, so dashboard can be extended, so we can find a way to eventually extend. You know this current um schooling dashboard to find a way to do this, maybe a visual representation of of how all these things are connected right, um which is nice. uh What do you think do you feel it should be in the roadmap, because it doesn't look like a road map actually.

E

The idea is not to decide on where it should reside. Now, it's just a matter of showing it off as soon as possible, so for all iCare it can be a hidden site where you can say, or even a link to the Rope set roadmap but foreign, something like that.

E

It doesn't really matter where, because we can always clarify and where to integrate it, because as soon as we start developing the components that can do these things and react, it's all a matter of integrating those components into other sections of the website. If that's not needed right, so whether it lives in the tool side in somewhere doesn't really matter, yeah I think, but for sure it might not make sense to live in the roadmap alone.

E

C

So also talking about visually, representing like this um idea right so I I was thinking right. What if it is something like visually represented in a tree like formats like you know when you click on it?

C

Okay, let me show you let me share. My screen can I share.

C

C

um So cool I'm, currently working on like on AC API map right. So uh what this project eventually does is it's like, like virtually you know, explain how everything about this in API, spec, right dog, the version and you just play it kind of just keeps like showing you the properties and child and stuff. So I was thinking right.

C

What, if it is something similar to this view, right where maybe you say, um tools, I click on design, and it shows you next job, children of things related to design, and you just keep having this nice um interactive views right, I was thinking what, if they design you're talking about it, could be something similar to this can which can be easily integrated anywhere in the website, or even someone else's projects. By doing the npm install or something.

E

Yep, that could definitely definitely be an option for sure I mean it kind of is like a tree in the um uh the.

C

Design like in the previous concept.

E

Right but it's yeah.

B

Okay, it means like what what you know right now showed us is more visualized like a graph than a tree like there are multiple connections going on like.

C

This this could be like, depending on how you want to implement it. Yeah.

B

C

Exactly so, it could be something that's linked to each other. It doesn't have to be a tree. It could be represented as a graph yeah, so I think the most expensive. The most important aspects is actually the experience right. So whatever we you or we're, gonna implement it. We have like implemented in a way where it doesn't get confusing right. Yes, but not visualizing it now you got lost like where am I coming. What's wrong, where am I exactly so I think it's a very, very nice idea.

C

Now we we have pretty a lot of a lot of good people in the community, because what why I find this interesting is right. So uh one of my my goals is like great um real life project. Examples like workshop and I was trying like I'm, going to working on an example of a webcommerce right and I'm trying to actually use, uh and the goal is to touch as many tools as possible in this kpi um uh project right and what I find really interesting about.

C

This project is also it could be a way of me. You know explaining these tools, like maybe currently doing a live stream. I mean these particular tools. I know it could be like easily for me to also like understand the tools and how they are related and which parent tools I'm using and also explain to people that eventually be watching the recordings on the workshops. Also and I think this is just really interesting. I would I would love, like you know, help you out with that and I'm pretty sure a lot of interesting folks.

C

This could even be part of the mentorship program. Just thinking definitely yeah.

D

B

I was just asking that I have a doubt that uh we're gonna, like ask for the Junior's plan, looks like we are gonna integrate with the other daughter, saying, kpi tool file with the fields that you specified right now.

E

I think my initial idea was I think my initial idea was to use.

C

E

We already have now I have nothing to share, but uh it's just ideas for now, but I I think it would be possible to use the already existing tool file and then modify whatever is needed.

E

So, for example, you can manually map a specific tool with extra information where needed and then manually adding those things for now, at least until as long as we're playing around with it, because one of the major issues I have is that these groupings I have no idea whether they make sense but I kind of just need those kind of groupings in the first place in order to generate some kind of discussion around it, um and my idea was to just take whatever um whatever the life cycle of an API is because it's somewhat similar, but it's still a bit icky in some way.

A

B

Completely understand that yeah.

E

Yeah, um so I am gonna, create an issue for it uh specifically this that outlines the idea behind it also to generate the discussion around it. So for now it's just about the idea and whether those kind of those kind of visuals give any benefit to the end user. Whoever those end users are right, because it's it's us, but it's also other people that either want to build a product with async API or want to build a platform that does something with async API or want to integrate with it right.

E

So I think it's yeah, just it's a long way ahead before we actually have anything or even a proof of concept, but yeah just wanted to hear your thoughts.

C

B

C

Seems very interesting.

C

Any other question.

B

Any news regarding that winter of court, regarding is like I, saw some of the folks writing in the issues that they have submitted. The proposals right now.

C

Yeah, so so what what I'm gonna do um I'm signing into our code right actions, since she would, uh you will say Mentor is um so according I had a conversation with you guys and uh so without no um insults, um so I think the winter of code.

C

Folks are less, you know not organized and I think they have to have issues like making decisions and stuff, but well, we agreed on with our high-endable cash is to try to like, despite so I, don't even know what the selection process is like like in Winter of code. We don't know if we get the proposals or they get video proposals. You know, I wrote them a couple of emails and get no response, and the original to me on Twitter and I'm, less active on Twitter and I was like okay.

C

What do I have to do so? We decided that, no matter what the decision is a Twitter of code right, we should try to like. Have uh these contributors contribute to using kpi right, they're interested in the project? They came to the project yeah, so we should help them. You know contribute like I think we have one of um one of the guys I assigned to you in the navigation issue. Remember.

C

Yeah yeah cool, so he he is so it's. The issue has already been picked out, like you already walked on just doing some enhancements, but that could that can be the okay. It was.

C

Of to assign to him during this phase right.

A

C

Break down in between okay, can you hear me.

E

Yeah, yes, and no yes,.

C

Okay cool, so what we are gonna do is, despite the fact that uh we don't understand what is going on with winter of code. What the decisions are right we are trying to. You know help these folks contribute to a Sync API right at the end. Goal of the program is to give them swags right and we've already decided so whether comes to the program to participate for winter of code, I'm gonna participate regardless right.

C

So one of your mentee is the issue that was assigned to you was it's already been worked on, so, which means you would actually like assign another issue to him for him to work on right, so which is what I'm also doing right, so whoever I get like Mentor during this winter of code, I have to like I said, because those issues are pretty like easy and they don't take time um a couple of weeks or a week or two they are done, but the program is like two months or something so, which means we have to like, assign them more.

C

He just work on. Do you understand.

B

Yeah yeah perfectly.

C

Yeah I'm also gonna um um also call which she would be. He turned the recorded, so wait. I'm gonna invite all the folks in the community that came for winter of code next week.

B

C

So we we we're gonna, have to like finalize everything with them and ask them what they think is best.

C

This might also be the last time we participated in Winter of code. Those guys are giving us headache.

B

C

B

With them next week, then.

C

Yeah, so we're gonna ask something so pranav: um they um active we're gonna host a meeting for winter, actually I'm doing: okay, okay, so we're gonna. Also imagine I'll! Consider winter of code next week um see looking forward to seeing you over there until we can like talk about how we plan to like do this program for you all. So it's just like we're not still in the program for winter of code. No we're just trying to help you guys do your thing. So uh another question.

C

No, so if there's no question um I guess this is the end of today's call. um So thanks for doing this call, this call was amazing, like I want to say something like shots.

B

Yeah, nothing, nothing! That's right! Okay,.

C

Cool, so disco was actually amazing, a lot of interesting um ideas, which is really really amazing, so I I, also so Pedro I think this is my first time um in a car with Pedro commentator. No, no I.

D

Didn't say anything well, I, don't think so.

C

Yeah so um nicely new uh you're, not looking fresh as always, and uh pronounce um um okay uh see you guys next time, um which is next month, um so the next Community will be in the morning uh httc I'm, looking forward to seeing you guys, then bye guys uh have fun good night, see ya, I, don't know if it's good morning for you on some nights, that's.

E

Night night.

B

And and a suggestion for you is I hope you don't see. Today's recording in the YouTube.

C

C

All right, bye, uh bye, guys, bye, see you guys.