nikhita
commented
1 year ago As TOC Liaison for TAG Runtime, I am in favor of creating this WG!
There's been a ton of interest around WASM in the community and it would be great to have a dedicated working group around this.
The WG members have also been very active on the #wg-wasm slack channel and in tag-runtime meetings already, so I'm confident that this WG will be a success :)
/assign @nikhita @cathyhongzhang @RichiH
Cathy and Richi - as other TOC liaisons for TAG Runtime, please review and provide your decision. Thanks!
As per https://github.com/cncf/toc/pull/1040/files#diff-0d7e3e82fc5c43ad633b1bffc1779e56f523638d0427543abf39a784a929ba68R148, the working group would be considered approved once the TOC liaisons approve (I'll also work to get #1040 merged ASAP! Edit: this is merged!).
cathyhongzhang
caniszczyk
angellk
RichiH
raravena80
helayoty
Dear TOC,
On behalf of TAG Runtime, we would like to propose a new working group dedicated to Wasm. The community members have come together to produce a proposal for the Working Group. We would like to inform you of the proposal and request the TOC's approval to formalize and launch the working group.
Kindly find the WG Charter PR: https://github.com/cncf/tag-runtime/pull/71
Background
WebAssembly, commonly known as Wasm, refers to a compact binary instruction format utilized by a stack-based virtual machine. Its primary purpose is to serve as a versatile compilation target for programming languages, enabling seamless deployment of applications for both client-side and server-side environments.
In the context of cloud-native, and with the presence of a Wasm runtime, the portability and versatility of Wasm allow users to run workloads in a diverse set of environments in both a centralized location and at the edge, including but not limited to VMs running a single docker daemon, Kubernetes cluster, and any other compatible workload orchestrator.
Mission Statement
The Wasm working group focuses on topics of running Wasm workloads across the edge, Kubernetes, and other cloud-native projects. The primary mission is to enable Wasm to be a first-class alternative to running such workloads. The secondary mission is to ensure Wasm is integrated and evolved across all cloud-native projects. We do so by promoting the adoption and usage of WebAssembly by providing resources, best practices, and tools that enable end users to utilize its unique benefits.
Scope
The working group is interested in all topics related to building Wasm artifacts, packaging and distribution, and developing solutions that embrace Wasm, including:
Deliverables
The working group will build collaboration, knowledge, and projects in the Wasm space, including:
We would happily discuss or answer questions about the Wasm WG with you async or in the next TOC.
@raravena80 , @nikhita
Best Regards, TAG-Runtime chairs