wasmCloud Community, 22 Dec 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: wasmCloud: Community Callout and HAPPY HOLIDAYS! - 12/22/2021

Description

wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.

A

Welcome to wasmcloud wednesday for wednesday december, the 22nd 2021 it'll be an abbreviated meeting today, but we'll get started by handing it off to brooks for community call out and a few announcements brooks.

B

Yeah so we'll go ahead and get started with the community call out. I've got three different good issues here. That would be great to jump in if you're looking to contribute to the project. The first two relate to our github actions and our oci references. So one thing that we'd love to have you notice?

B

If you look in the capability providers repo- and you take a look at our releases- we have different releases for all of the you know: the sql provider, the http server provider, redis provider etc, and these versions match up exactly with the oci reference that were that we're publishing on our azure container registry.

B

So when you go to start http server provider, you can start 0.14.7, but one thing that we'd love to have and that we currently use an action that supports you can edit this github action like our custom, one to include a body um and we can kind of change the uh body of that instead of just the the latest, commits to something like uh what this issue is specifically referencing, um we'd love to add the specific oci reference in there, so that, if you come to the capability providers, page and you're thinking, you know you want to launch the um the latest version of the http server provider.

B

You come right to releases, find http server and then copy the the reference straight from there. So this is the the first issue. I kind of wrote up a little bit here about how you can configure this and and where you can actually find um this action so feel free to reference that um as a reminder, if you're interested in taking on any of these just drop a comment on the issue and say: hey, I'm taking a look at this, so that um so that you can.

B

Let us know that you're taking uh checking it out. um The second one is also in the capability providers. Repo. This is a simple fix in our nats release provider or our nat's provider release action.

B

It's simply that we name the binary something different than the action is um than the action is expecting, and uh you know we'd love for just a little bit of extra attention on this. This is something that's kind of flown under the radar, since we don't release the the provider super, often because it's pretty well fleshed out and then the last one for those of you who are on your wonderful holiday breaks and thinking, you know what I'd love to just love to just experiment with elixir otp on this break.

B

You know I've been waiting to contribute to wasm cloud and and jump into the new run time. This is a perfect one to get started and do that, while you've got all this free time on the holiday right, don't want to hang out with your family. You can just get to contributing to wazing cloud. So, as usual, I'll post, these in the community, slack channel and they'll usually get tweeted out, so you should be able to get started on these if you're interested yeah, that's my community call out now.

B

I do have another announcement that I want to make. um First of all, we recently repurposed our wasmcloud slash wasmcloud repository to act as a sort of organization homepage.

B

This is where we'd love to leave some of our community resources, like our code of conduct, our contributing guide- and you know it also has archive things like for our previous restaurant time, but we'd love to use this as like an overall landing page where we can use to maybe communicate the future things through through the github issues uh here, um etc, etc, and with that we've also kind of made up and and given our readme a little bit of facelift.

B

Here, we got a bunch of badges, got some emojis next to the header uh things here with general links to our elixir, runtime, our javascript runtime, etc. So we have this pinned uh now to the to the repo or to our org pinned repos.

B

But one thing that I noticed when I came over here the other day- is that if you take a look at this little shields dot io badge here wasn't cloud recently surpassed a thousand org stars, so hooray for that across our all of our repositories. We've got a thousand stars right when I started this or where I'm gonna put the badge in it was like 9.97, so I knew it was coming soon. So that's just pretty exciting. I would dropped our um dropped. Our reddit twitter youtube all the all the things here.

B

So hopefully this will be a um a good place to communicate for, for all things wasn't cloud. This is the first thing you hit when you search was cloud on github, so you know we really want this to be like a starting point and then forward people off to other places. So um if any of you have seen uh an example of an org that has done this really well um happy to consider any of those um any of those options.

B

Yeah just wanted to announce the the 1000 org stars and let people know about the uh the landing page.

A

That's great brooks, thank you so much. um I think uh everything else we will hold on this week was there anything else, urgent or interesting that anyone wanted to bring out this week before we, you know let people go to get their break started.

A

All right: well, I think this is the shortest wasn't cloud wednesday of the year. I hope everyone has a great uh uh week and happy holidays and everybody's safe in the latest wave I'll, stop recording. As usual, we can hang out, see ya.