Knative Community Meetups, 24 Feb 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Knative meetup # 9: 2.24.21

Description

On February 24, 2021 the Knative community hosted a meetup featuring a demo, "Transforming CloudEvents with Bumblebee" presented by Sebastien Goasguen, Co-founder of TriggerMesh, who introduced Bumblebee which allows people to define cloudevents transformation declaratively. Combined with knative primitives it helps build event flows that integrate separate services.

Other discussion tops include:
Eventing v1.0 work started. Help is always welcomed
Eventing Roadmap 2021 finalized
Release 0.21 happened yesterday
Removing v1beta1 API in release 0.23

A

And yes, we are off welcome everybody to the creative community meetup. My name is maria cruz, I'm a program manager in the global, open source programs office, and um we have a few items to go through on our agenda today.

A

So if you haven't seen the agenda, it's linked on the calendar invite otherwise somebody can drop it on the chat here.

A

Okay, we're gonna start with um working group updates. uh Is there anybody from the eventing working group.

B

Oh, is there there's plenty of us here um so uh zohan villa um one of the things that we've been talking about for a while is how do we get event into uh version 1.0, and what does it really mean? um We spent a lot of time last year getting the apis into shape, but there is a lot of work that still needs to happen. So uh thank you, scott, who basically uh all of his monday grinding through and putting together issues and so forth.

B

So please do come there and take a look see if something is missing um and it would be fantastic if folks would come in there and help so yay yeah.

C

This might be a good time for like new contributors if they want to come in and ask questions or find really small tasks. We can find those things for you, because there's a ton of work to do- uh maybe not today but like in a week or two there's going to be a bunch of patterns of what we've done to solve problems, and it's more of that. So we want people.

B

And there's a lot of areas to contribute, so it's not just cranking out code, there's a lot of docs work. There's a lot of spec work, there's a lot of all kinds of different things. So please do come come party with us.

B

You know you wanna all right enough of that. uh Okay, uh thank you. uh The other one that has been kind of a long haul is uh getting our road maps into shape. So ahmed has been tirelessly uh uh working through this and getting uh roping folks in getting them to come in and figure out. Okay, what are the things we are going to be doing this year?

B

um So there's the road map there please go, take a look um and um yeah it's in um and, of course, just like clockwork to talk every six weeks we cranked out a new release, so 21 went out. um There's some um some highlights from that which is. uh There is a ping source breaking chains, so their binary mode is in a 64., so heads up, and we also have triggers delivery which allows you to go ahead and configure delivery, and you might say what is delivery.

B

This is where you can go ahead and configure things like retries or dlqs or, um or things like that, so um that was a that was the last sort of kind of a feature that we added or slash oversight. So go take a look at that um it makes things uh cooler um and then I just wanted to uh bring your heads up uh raise visibility.

B

uh We are removing the v1 beta v1 beta1 apis in the uh o23 release, which is uh well. It is what it is. I'm not gonna go uh switch my calendar right now, but it is basically two releases from now uh so 12 weeks from now so start planning for that, and uh actually that call to action. It's I intended that wrong. So the call to action that I would like to do is in the vein of the eventing 1.0 work.

B

uh We have quite a few of the repos that uh um have been put in the eventing uh uh sorry k, native sandbox, eventing star, um so some examples might be like nets and- or you know, github skidlabs and everything else.

B

So we definitely would love to go and find folks that are interested in those particular areas and uh come in and um and uh take a take a role in their um as in if you are using them or not, because otherwise, if, if we don't get uh maintainers for them, then uh the risk, the fact that they will basically be archived because uh we don't uh see the use for them and we don't have the bandwidth to go and deal with them.

B

So even if it'd be helpful, even even if you come in and say like no, no. This is very important to me, uh so we can at least gauge uh some uh some uh usage this way and I think I'm done yeah. I'm done.

A

Awesome, thank you so much, and I guess for for that update. um I think uh next up is carlos santana. With a user experience working group update, there was a big message on the slack, so you should go back and read it afterwards, but you can't lose. Please go ahead with your updates.

D

And you hear me: oh um yeah, I added two two bullets. uh One is the ux and on the docks so for for the ux uh uh working group. uh If you don't know, uh that's a a new working group that got proposed and went through the whole uh community process, which is documented in our uh github repo, and um we went through all the steps and then we formed a new user experience.

D

Working group uh more details is that an announcement that I sent out to you today on the menu list and slack and there's links in there to all our information, our repo roadmap um studies that we do with the interviews and we work on folks that want to help out, enhance the experience of using k native and the other update, is dots working group. um A new release of 0.21 of canadians is being cut, so there'll be new docs for 0.21.

D

As always, the last release in the docs gets dropped. So we support only three and uh also this week, uh we'll be posting our usual blog release post, which is summarize everything around all the things cli eventing and serving so I'll, be going after people for information.

D

A

Great thank you so much for for those updates and thank you for pushing the the blogs as well.

A

If somebody added creative v1.

A

E

So I don't know random.org coinflip. What do you want to do? Here's the tldr and vla? Maybe you can blend any gaps that I miss is uh within steering and a trademark committee and toc.

E

I think it's safe to say that we collectively feel that uh getting to v1 um and what you might call ga level for k-native as a project is a high priority for us this year um and uh doug and folks, uh doug and brenda, I think, have been working on a scope document to kind of be the basis of uh like uh the process to drive down what remains before. We can call things b1 uh and drive those to a conclusion.

E

So um that is something that we will probably begin to talk about more widely in the coming weeks. Vla, I don't know if you want to go into exactly what the generalities of that document.

B

Anyways, no, I don't think so. I mean, I think you said it much better as uh as usual than I could have said it. So please go take a look at.

F

B

Is for us to grow and get the ga so.

E

That that level of saying that something is 1.0 or it's ga, it tends to be a very important psychological threshold to meet for folks to adopt it. So the the motivation here in case it's not perfectly clear- is that we believe that hitting that threshold will help us to drive adoption of the project, which is something that we're all very interested in doing so that uh that more people can use the great technology that we've developed here. That's the motivation.

A

Awesome, uh thank you so much for for sharing this update and, yes also a scandalous design get to know 2.0.

A

um I hope that everybody has a chance to to look at the documentation, scope, it's linked on the agenda and finally, I have a community update. I thought of about asking you all uh what are your? What are the events that you're interested in presenting about creative this year? If that's, you know, even I think that any of you would like to do, uh and I thought that creating a simple spreadsheet to map this out and maybe hopefully drive some collaboration around this.

A

It was a good idea, so I set up a spreadsheet that you can find. I can actually link it here in the chat um and I thought we could take a.

A

uh We could take a few minutes if you have anything in mind right now or otherwise come back to this later, um to to write down what are the conferences or events that you would like to participate in and pre specifically, if you are interested in something about k native uh and if you're looking for collaboration or copy centers- or maybe you want to present, but you don't have a lot of time. So you need somebody to help you out with something.

A

um I thought that this could be a good resource for the group and feel free to unmute and and share any any thoughts or events that come to mind right now. We can give this a couple of minutes before we run out of time.

B

E

The cubecon I saw uh in the chat- and uh I I would encourage folks to if you, if you have something you'll, want to talk about in kubecon like please consider putting together a cfp response um and we'll see what happens I'll I'll say my usual disclaimer around kubecon here that, like uh as uh someone that's done, a program committee for kubecon several times like the number of submissions that they get are vast uh and far greater than the actual available slots.

E

So kubecon I tend to think of in a vacuum like independent of the topic as being kind of uh it's a crowded, uh it's a crowded cfp.

E

um I definitely would encourage folks like to think about like what what things may not be as crowded, but things might be more focused on serverless specifically, and it doesn't have to be big. uh You know I I know the world's a little upside down, um but there are still uh user groups and regional conferences that are virtual. So, like uh we don't have to think big to get some really good exposure.

E

We can think small. We can think medium and we can still think big. But um let's not only.

E

A

I'm capturing some of what you said here in the notes poll uh and adding your comments or recommendation to to also think of smaller.

A

E

Like the reach in terms of the same reach as kubecon, would it doesn't mean that um that you can't make good connections with people and inspire people to take a look and even to contribute by speaking at things that aren't as big as kubecon, which, like uh my frame of reference for kubecon, is that I think last year, kubecon was.

E

Long last year, but in 2019 I think kubecon was more widely attended. The red hat summit, so uh like kubecon is, is has become a fairly large event like we can have a lot of impact and like um information and like inspiration to people uh without necessarily having a ton of talks to get uh they get into cubeco.

A

And I'm seeing here uh carlos idea of having a canadian twitch channel, which seems I mean I love that idea.

E

Can I take a moment, since I'm already kind of talking uh to share your idea that, like I've recently created an issue about I'd love to get like some people's thoughts about this um and the idea is to have like a contributor of the month type of thing, uh so I'm still kind of thinking over what what uh directions we can go um with this. But let's see uh trying to find the issue. So it's community 469., if folks want to uh to check out community 469.

E

Let's talk about how to have something fun around contributor of the one.

E

Maybe we could even announce it on twitch.

C

You know, as the falco contributor of the month, it feels real nice.

E

This idea is shamelessly stolen from a falco community, uh but I'm glad it feels good and we want folks to feel good. We want things to be fun, uh so click on over to community 469 and, let's party, on what we can do. That would be fun like that.

G

Well, are you talking about a link that people should visit? I, I don't see it on the agenda.

E

uh I can put it into the chat, but it's I'm just asking.

D

E

To look at issue 469 in the community: okay, cool awesome! Thank you awesome. Thank you.

A

Cool, I think uh we ran out of time to to discuss this, but I wanted this to be on your on your else's minds, um so we can come back to this document and fill it out with other ideas. I don't want to take any more time so and without any further ado, I'm gonna pass the mic to some koa who is going to present a demo. Try transforming cloud events with bumblebee sebastian. I think you should be able to present.

H

Yes, can you hear me yeah yeah.

A

H

So that's good, so something we we realized that trigger mesh is that we needed a way to be able to modify the cloud events uh declaratively uh when we were describing a flow. We do it for basic integration, so we have an event source and we need to send it to an event sync.

H

So we call that a transformation. So basically it's a crd with a controller, a kind transformation and it just transform cloud events. You can transform the attributes. You can transform the payload, you can add, delete, shift keys. uh You can store keys things like this. All right. So can I share yeah.

C

I can share.

H

All right, so it's pretty straightforward ooh looks much better now boom. Can you see the slides.

A

H

Okay, so sebastian co-founder of trigger mesh, uh so bumblebee the transformer right. So that's how we call the the transformation engine. uh The author actually of bumblebee is a developer in our in our team. Who's been with trigger trigonometry, since the beginning he's contributed to k native timor is out in kyrgyzstan, uh he's the main author, but because of uh you know, time zone differences. He cannot present so I'll I'll present bumblebee bumblebee is open source. You can get it uh trigger bumblebee.

H

uh Potentially we could give it to the sandbox uh written in. Go uh you deploy it with ko. It's pretty simple, uh simple use case: again, you have a source cloud event. Type fool goes to a broker. You want to transform that cloud event. So what you do is that you end up with two triggers: there is a trigger that gets the type foo you send it to a transformation which is an addressable declarative. Api defines how you're going to modify the the attributes and the payload gets back to the broker.

H

Second trigger uses the new type to actually send to the uh the end target um things that we faced. I mean I'm sure. Maybe some of you faced it quite a lot. Is that if you, if you're, not careful with your types, uh you know you can get tons of event loops. So you know definitely you need to be extremely careful.

H

uh The object looks like this kind transformation, and we have you know a first in the spec. We have a first section which is context, and that has to deal with the cloud event. uh You know I want to say attribute so id source type things like this.

H

You can actually store the you know the context of an incoming cloud event in variables, but you can also add right or you know, modify so if you want to modify a cloud event type you you do context operation, add and then the key will be type and doing this you switch the the type of the cloud event uh on the fly.

H

If you want to modify payload, then you define uh in the spec. There is a section data and then you can add a key. So you add a key foo bar in this case. You set a value. You can shift the key from full to wolf or you can delete a key right. So very you know basic transformation, all declarative.

H

uh You know quite quite useful, um so demo uh demo so demo a little bit of advertising for the google cloud uh cloud. Shell, can you see this? Yes, okay? So it's uh it's a gke cluster. I installed uh kennedy from scratch. uh You know latest release and then I deployed uh I deployed bumblebee uh with uh ko.

H

So if you look at the tree of bumblebee, you know it's pretty straightforward and when you deploy it with ko, then you end up with uh you know: basic transform controller running in transformation, namespace right and you're you're good to go. So what I did is I I launched uh sockeye the new version.

H

Thank you, scott! So ah and I lost network. No, can you still hear me.

A

We can hear you.

H

Okay, so what's going on with my sockeye.

H

F

H

Right, okay, so that's the demo! God.

H

Xip server cannot be found.

C

Try http not https.

I

The error is named not resolved, which suggests that xip.io has decided to take a little break ah jesus. uh You can.

H

I

Switching to nip.io I've heard that maybe that's slightly more reliable, but it seems like these things are. um Apparently you know you get what you pay for slightly less.

H

Yeah yeah, okay, so fine, let me show you the uh so we're gonna go in the in the config. You know: basics basic samples. You you in the bumblebee repo you'll, find the basic sample with the the diagram that I showed. What I was going to show. You is a basic. uh You know a pink source, all right, pink source that has you know first uh and last name, alice smith right.

H

So we can, uh you know we can apply the we can apply the source right and maybe, while we do this, um so we can apply the source. Of course we have. uh You know a broker right, that's running uh perfect and then, if we look at uh the triggers, so I have two triggers uh the basic ping goes to uh the transformation. So you see how you know the transformation can be set here as a you know, subscriber here in the in the trigger.

H

So it goes to the uh you know: the transformation service, if you wish and then the the response comes back to the to the broker, and then you know what happens that you need uh the second trigger to. Actually, uh you know send it to uh to sockeye right. I mean here, it's commented so that I'm gonna get all all events.

H

uh You know all events display in sokai simultaneously, uh don't think I, okay, so they're still in place, and now, if we look at the the transformation object all right, so the first transformation that we can do you know is simply hey. I want to to modify the cloud event type of the ping and I switch to trigger mesh transformation pink source right. So it's not the k native ping anymore.

H

We just switch the cloud event type and then we add, you know a new key in the payload, so you know middle the key will be middle and the value will be maria all right. So if you do this, then you're modifying your thing. So we just apply.

H

All right, so we apply the transformation. It's a crd. You get the idea so get transformation. You know we see the object. It has. You know uh an address here, let's see if our sockeye has started. Oh, yes, a little bit of luck from the demo, god right. So what should we see on the sockeye on the sockeye? We're gonna see the two events, because I didn't, I didn't remove the the ping ones.

H

So, every minute we're going to see the the original ping event right and we're gonna see that type and we also should see a transform event uh with a new key middle with the value, maria and a new type right. So if we wait one minute, you can still hear me.

G

H

Okay, there you go demo, gods are with me, okay, so can I zoom that so perfect? We see the first event dev kenneth sources, ping. You know that's the original original payload alice smith, and now we see the second event. That's been transformed, key maria and a new, a new type, all right, so events being transformed on the on the on the fly.

H

uh Let's look at a second transformation.

H

uh This one again, you know the so we switched the type. uh There are different things you could store. You know the source, you could store the id which could be very useful and so on. You know uh here. Second transformation we're shifting a key, so the key, which is first in the payload, becomes k native right. So it's going to be k native. You know uh alice right, so we apply.

H

uh We apply that one and I'm sure that you know by now. You have you know you, you got. You got the idea right, so uh you know we need to wait another minute and we're gonna see that uh what's that transformation that I said so, the the key first is going to shift to k native right. So we're going to see k native alice and we're going to still see last smith middle.

H

Mario, I should have put less than a minute. I don't know if we can do less than a minute in the pink source. Can we?

H

Oh? No, it's a crown tab.

C

huh Well, while we're waiting, you can show off the sockeye filter feature if you click on the upper left, oh the new version, and then you can add in the attribute your filtering on is maybe type.

D

C

Trigger mesh, and then you should see only the transformed events in sockeye.

C

H

C

Even know, and then.

H

Push add filter.

C

And then this will dynamically update the display that you see, and so the idea here is that you could kind of play with what a trigger might do in production on a stream of events. Yeah.

H

Cool so now you see and we got our event with our shift. So now we shift it from first alice to canadian alice right. Is it big enough? I mean it's pretty straightforward, so I guess I guess you all. You all understand what what this is doing right and it just works.

H

So last one a delete. You know, of course we can. We can delete keys, so you know apply uh I'll, do the delete and then one last one which is, which is nice with um the actual cloud event context.

H

So this one we're going to delete we're going to delete the key last right. So what we should see is kennedy alice, middle maria and last smith. Should this should disappear.

H

And this is useful to us, because we've we've developed a trigger mesh, a set of event syncs, we actually call them targets and our event. Syncs actually accept a particular. uh You know event types right, so you know if, for example, we get github and we want to talk to twilio the github events they come in as github knativ, and then we need to send them to our target which takes in you know twilio.triggermesh.

H

So we need to transform the events and uh and set the type in addition to the payload, of course,.

H

There you go, and now you see we have deleted the key all right, so the last one I wanna I wanna show you is uh is one which uh actually here uh we can store what an attribute of an incoming cloud event.

H

So here you see that in the section context we are doing a store operation and we are going to store the value of the the cloud event source right uh in a key here within the context of that of that manifest, we need to set it as dollar source right and then I further uh down here in the data section, I now add a new key foobar and I set that new foobar key to the value of that. You know incoming cloud event source all right, so this is just showing that you can.

H

You can store incoming attributes, uh which can be, which can be handy, so apply dash, f, uh trans, three. There you go so now. What we should see in the next event is that we should see that we're going to have an additional key which is going to be fubar, and it's going to have the value of the actual cloud event. Source makes sense. So you can, you know, mix.

H

Things so I actually don't know, can we can we put less than a minute in the in the crown tab.

I

I think you need to use the heartbeat source for that. Oh okay, I was just looking it up.

H

Okay, so, meanwhile, you know the repo trigger mesh bumblebee open source uh apache software license. Oh no, okay, we put them under licenses. Okay, why is it under licenses? Is because when we, when we try to get things certified with red hat, we need to put a hula and a license under licenses directory, but anyway it's apache software license. We have a release process, uh so this gets tagged. uh You know automatically when we release new software.

H

There you go so we have our bot cyber wood ford, it's not the it's, not the connective.

H

You know uh actions uh yeah and deploy with ko. So a simple ko apply should do it for you, you'll get the crd the controller, and then you can start. You know doing your your transformation. If we go back to our soca here, you go so the last. You see that we now just added a key foo bar and it's set to the value of the you know the cloud event source right.

H

So you know all of this. Hopefully what you're seeing is you know it's, uh it's quite straightforward, but it's actually! You know. I find it extremely neat. Actually clever and super clean, uh you know basically manipulating cloud events on the fly with a declarative api, all right and that's it. Thank you.

A

Wonderful, thank you so much for presenting that uh there are a ton of comments here on the chat box and given how far we're into the meet up. I'm not gonna go into breakout rooms, uh so please feel free to uh mute, starting with jax, who has his hundreds.

F

It's sebastian, um I have one question: is it limited to cloud events? No, some reason. Okay, so no need.

H

Yeah, it could be anything.

F

Yeah, I I smell future controllers being written. This way is what I was thinking. A lot of controllers just take one bit of json, move the fields around and spread out. Another piece suggestion.

H

Yeah, so we and- and you know I did it with- uh I did it with uh a broker and so on. But of course you could just curl straight into the the endpoint of the of the service right.

H

You know it's pretty and it could be yeah any any json.

H

H

So should I go back, should I go through all the questions or you all got your questions answered.

A

uh Maybe we can call them uh one by one.

H

Shift a question from alex shift: yeah shift replaces modifies the key. It keeps the value, but it shifts the key to something else.

H

Yeah right now you know operations. We could totally see adding additional operations, but right now, that's you know. Those are the operations that we needed, so you know add especially add, delete and and use the uh use the cloud event context.

H

Thank you vlay yeah. I didn't do anything. Actually, it's all timor uh yeah. I have the filter on yeah. Don't do event loops, be careful with your event. Types yeah, okay,.

I

That's it. Thank you all very much. I think there were two more things. There was one comment about testing um and whether they're, whether you had any patterns for you, know, as you start to build more complex transformations, making sure they work right.

H

uh Honestly, I don't think we have. I don't think we have uh testing for the actual.

H

You know I'm totally going to punt on that one. uh So we've worked, I mean on testing, so some of you know some of the folks in the in the team, so uh antoine antoine coten works for for trigger mesh. We've done a lot of work internally on using uh ginkgo ginkgo for end-to-end testing, so we have end-to-end testing for our sources and targets and also some of those integrations right, uh but we don't have yet end-to-end testing purely for bumblebee. I don't.

I

Think we do, um I actually meant something different. I met consumers of bumblebee who are writing starting to write code effectively in these yaml files. Right may want to test that their code, that is the bumblebee transformations, actually does what they want.

E

I think that was alex's.

I

Point, okay and yeah, so that may be something that um there may be. You know: hey open.

H

I

H

um No, but it's qui, it's quite fun, you know it's it's a little thing, that's that's quite powerful and uh yeah I mean when uh you know we we discussed this internally and then timor implemented it and you know we think it's it's super clean and you know very useful. I like.

I

It um one other thing I was going to point out was: I noticed, your releases um have the binaries, but if you use co resolve you can get a yaml, that's all of the config, bundled into one chunk, with references to like gcr dot io. If that's, where you're, storing your containers, yeah yeah,.

H

I

H

I

We use for k-native releases.

H

I

H

J

I

You want to do, but I figured I'd mention that no we should we should. We should.

H

Make it just a cube.

I

Control apply some url from github.

H

Yeah yeah yeah totally totally fair. We should do it. That's that's! uh That's a new mission. uh I actually run into a ko, ok problem uh when I was preparing for the demo. So so yes, we should add the manifest to the release.

A

It looks like carlos has some comments. Do you want to unmute something about metrics.

D

No yeah, I don't know if you have time, but um do you have a metrics endpoint or you push metrics about getting stats about transformation that didn't work errors or how many shapes or operations you're doing.

H

No, I don't think we're, um I don't think we're exposing a matrix uh endpoint on that one.

D

To get the health of the controller, does, does it scale horizontally? Is it stateless, I'm guessing.

H

H

Good question: I don't even know how it's is it wow, it's just using a canyon service. It's it's a deployment, oh yeah,.

C

H

I thought was no: no, no, no, no! No! No! No! Actually, the the controller.

H

D

I'm looking see mariah what'd, you do when you would mute me. No, no.

H

Yeah, I know the transformations are actually pure deployments right so that we don't have. We don't have the auto scaling out of the box any.

D

Reason why they need to be deployed instead of okay native. So no.

H

D

H

I'll I'll have to check with timor actually, because we should we should be hold on. Let me check no, no, no, my bad, my bad yeah, the transformation or creative services. Yeah, of course,.

H

Yeah yeah, so the transformation themselves have the the auto scaling of k native um out of the box.

D

So it's a matter for the matrix thing. Then maybe it's a matter of adding a open telemetry and do the pushing yeah.

J

Of the metrics.

H

I'll put I'll put an issue.

I

Actually, if it's a k-native service, you may be able to get some of them just out of the box with the services yeah. Yes, response code and latency and stuff like that,.

D

Yeah kind of like mesh type of metrics, not business inside.

H

Yeah, so you know, we think we think it's pretty cool. Definitely you know there is potential for more work and.

D

That was another question. Leonardo is asking, I think the same question I asked uh before in the chat about multi-tenancy and he thought about what the tenancy of that of that controller may be, isolating that that store or that state.

H

Or uh so we haven't, we haven't dealt with multi-tenancy on the tr on the transformation on bumblebee uh right now. Actually uh antoine has has moved all our sources to being multi-tenant. So if you look at all the trigger mesh aws sources, they are now all multi-tenant, uh but we haven't done it for uh we haven't. We haven't looked at it for uh bumblebee yeah.

I

If I'm understanding correctly, the store is in the context of a single event, it's not applied to things in the future right, no.

H

No there's no persistency in that one yeah.

I

Yeah, so this is stateless.

I

Shouldn't be an issue.

H

G

I'm not even just I'm not even.

H

Sure I'm not even sure what multi-tenant transformation I mean you.

I

Could use a single pod and handle.

H

I

Namespaces uh but since you're using a creative service, um you know you'd get small incremental savings. Not you know like oh hey. We have these pods running all the time and most of the resources yeah.

I

Now it may be that ibm, you know running an enormous cloud actually cares about saving those. uh You know those pennies from each namespace, but.

H

Cool, that's awesome.

A

Great this was an amazing conversation and thank you for bearing with all of us as we navigated, through technical difficulties. I just launched the paul I wanted to let you know that this poll helps me to make a better meetup every time. So, if you take a few seconds to respond to that, that would be awesome.

A

uh Demos keep the creative world going round. So uh please consider uh submitting a demo idea to this form demos that I'm pasting here on the chat um we are looking for demos every month and uh we always upload them afterwards to the communities uh youtube channel, which you should follow to get updates, and thank you so much to sev for presenting this again and uh we'll see you at the next community.

H

Thank you. Everyone bye.