From e30bc1f5682b24e4e03a957a23fb9530ea3c53ed Mon Sep 17 00:00:00 2001 From: CazJT <113366164+CazJT@users.noreply.github.com> Date: Thu, 29 Aug 2024 09:28:35 +0100 Subject: [PATCH] Update 2024-08-28-community-meeting.mdx Updated missing section and added Github contributor handles Signed-off-by: CazJT <113366164+CazJT@users.noreply.github.com> --- community/2024-08-28-community-meeting.mdx | 23 ++++++++++++---------- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/community/2024-08-28-community-meeting.mdx b/community/2024-08-28-community-meeting.mdx index bfc1c71e..2ab5a4f8 100644 --- a/community/2024-08-28-community-meeting.mdx +++ b/community/2024-08-28-community-meeting.mdx @@ -21,23 +21,26 @@ title: 'Meeting Agenda - 2024-08-28' - wasmCloud 1.2 is our latest release, now out! Check out this a great blog post on [wasmCloud 1.2](https://wasmcloud.com/blog/2024-08-27-wasmcloud-1.2-improved-streams-automatic-config-updates) which is well worth diving into. - Highlights include: automatic config updates for providers (update to the latest SDK - there is a great first issue for implementing this in Go), improved streams, additional policy and secrets validation, better downstream link validation, and fully-tunable wasmtime runtime parameters (important to be able to control how much memory a component can use). -- In focus: `wasi-blobstore` streaming has seen a whole suite of improvements; manifests are better. Suggest checking out the blobby example to see how this is working in practice. +- In focus: `wasi-blobstore` streaming has seen a whole suite of improvements; manifests are better. Suggest checking out the [blobby example](https://github.com/wasmCloud/wasmCloud/blob/04d7e8e902ec27dcc20e1deeb222574554166ad1/examples/rust/components/blobby/README.md?plain=1#L4) to see how this works in practice. - This closes out all the remaining issues in the Q2 roadmap. - In wash 0.31 we have a couple of great improvements - as always check out the recording for Brooks's demo. -- FEATURE: If you output the version for wash we now get the version and the embeded default versions of NATS wadm and wasmCloud that wash will utilize. This is super useful in the command line - easy to do wash// version and get all the versions needed by wash. -- FEATURE: improvements to the tables that we output in the command line. wash app lists - instead of having loads of separate fields, we hace the desc listed belwo the app and ave streamlined theinfo there. +- FEATURE: If you output the version for wash we now get the version and the embeded default versions of NATS, wadm and wasmCloud that wash will utilize. This is super useful in the command line - easy to do wash version and get all the versions needed by wash. +- FEATURE: improvements to the tables that we output in the command line. wash app lists - instead of having many separate fields, we have the description listed below the app and have streamlined the information there. - We have also updated the way we output to the terminal so we don't exceed the width of the terminal, which helps wth consistency. -- FEATURE: Thank you Aditya for enabling us to watch the status of wash app lists - instant refresh allows us to reconcile before compiling. -- FEATURE: We have a much improved wash status view. We can see a lot more info about the application and its inner state. When we query the wash app status, we can now see why it might not reconcile - infinitely more helpful. +- FEATURE: Thank you for your work [Aditya Salunkhe](https://github.com/Aditya1404Sal) in enabling us to watch the status of wash app lists - instant refresh allows us to reconcile before compiling. +- FEATURE: We have a much improved wash status view. We can see a lot more information about the application and its inner state. When we query the wash app status, we can now see why it might not reconcile - infinitely more helpful. ### DISCUSSION: wasmCloud Q3 roadmap check-in -- Thank you to the community for taking on a ton of work! Encouraging the community to contribte is one of our main goals and so it's exciting to see you all getting involved! The roadmap is a great place to start to find out our good first issues. +- Thank you to the community for taking on a ton of issues! Exciting to see a growing number of you getting involved! The roadmap is a great place to start to find out our good first issues. +- And don't forget being a wasmCloud contributor means SWAG! - The Q3 wasmCloud roadmap is always available to view [in the repo](https://wasmcloud.com/docs/roadmap/). -- We have 4 completed, 5 issue in progress and 6 to begin. -- In progress Massoud has take on a all-in-one helm chart. -- We have started on custom interface functions that support xxx re-listen. -- We have started on the work to support relisten. +- We have 4 completed, 5 issues in progress and 6 ready for work. +- Improving CI, extensibility of wadm have landed already. +- In progress: thank you Massoud, for taking on the all-in-one helm chart. +- We have started on custom interface functions that use resources. Support for exporting a resource won't land in this feature but passing a resource around with custom interface functions is implemented today. +- Sharing components and providers between wadm manifests is progressing nicely. +- Working with [Ahmed Tadde](https://github.com/ahmedtadde) on [FEAT] emit application events on wadm topic - check out the link above for the full list of current issues and get involved! ### DISCUSSION: wasmCloud Innovation day, [sign up!](https://wasmcloud.com/innovation-day)