These are the minutes from the meeting today. I've taken some of what was
discussed in the meeting today and added to the Wiki page under the
existing work initiatives, but I'm hoping each of the Sig members can
update to better capture the specifics of the work/what is already in
place.
https://fedoraproject.org/wiki/SIGs/WASM#Existing_Work/Initiatives
Agenda
- Intros
- Communication channels
- Mailing list
- Slack/IRC/etc ?
- Pagure/Wiki
- Capturing existing work/initiatives
- Known Gap
Minutes
- Intros
-
Zuzana - Node.js is using WASM so need to find out what else is
using/needed WASM in Fedora/RHEL
-
Michael - On the runtimes Node.js team, initial interest based on
Node.js use of WASM as well.
-
Milad - Node.js with a focus on keeping V8 going
-
Ivan - in CTO office at Red Hat leading WASM effort
-
Jan - Work in same team as Jan, similar interest
-
Richard - In upstream Node.js project, if there are updates needed in
Node.js upstream then may be involved in that.
- Communication channels
- Mailing list
- asked everybody to join new mailing list
- Slack/IRC/etc ?
- Jan, for more complex topics good to keep to mailing list
- Zuzana, good for smaller more one-on-one discussions
- Jan, traditional way to do that is irc, centos discussions are
mostly IRC
- agreement to stick to IRC
- - Pagure/Wiki
- Wiki is at
https://fedoraproject.org/wiki/SIGs/WASM
- Pagure, idea was somewhere we could get notifications about bugs
- Maybe use something like Trello ?
- Ivan, does seem like some other Sigs use a project in Pagure
and just use for issues.
-
https://pagure.io/ContainerSIG/container-sig (lead is from RH
we can reach out to ask about best practice) - Michael
will reach out to
owner to ask about their best practice in terms of managing issue
-
https://pagure.io/cloud-sig (lead is also from RH) is a nice
example where top level is the main repo
- Ivan will also ask around a bit to see what he can learn
- Capturing existing work/initiatives
- Jan, working on wasi-libc (Needed to support WASI)
-
https://gitlab.com/khx/fedora/wasi-libc, fork of upstream with
some Fedora specific mods. Approach of have a set of commits
that float on
top of upstream. Not sure if we’ll prefer that or regular
repo. Have not
had time for last few months.
- Can compile it
- Can point clang to it
- Not sure if it is in line with any Fedora guidelines etc.
- RH/Fedora devtools team has WASM support in clang for emitting
WASM from C in RHEL 8.
- would be good to capture what specifically has been made to
support etc.
- Rust support ?
- Ruby ?
- WASM Edge already supported in Fedora (x86, arm)
- Ivan working on getting WASM Time to get it support in Fedora (x86,
arm and s390x)
- crun with WASM Edge in Fedora
-
Important uses cases
-
Compile language from X to WASM with support for WASI
-
C ( Needed by Node.js)
-
Rust
-
possibly Ruby ?
-
Run WebAssembly within a runtime
-
Node.js (supported through V8)
-
Ruby, python etc ?
-
Compile interpreter to WASM to run in browser
-
Out of scope
-
Running WASM containers
-
What needed for use cases we want to cover to start:
-
Compile language from X to WASM with support for WASI
-
compiler support (clang)
-
wasi-libc
-
Run WebAssembly within a runtime
-
Same components as “Compile language from X to WASM with support
for WASI”
-
WASM engine (V8, wasm-edge, …), Garbage collection is often a
challenge