Skip to content

Latest commit

 

History

History
92 lines (75 loc) · 3.28 KB

WASI-02-27.md

File metadata and controls

92 lines (75 loc) · 3.28 KB
Raw

WASI logo

Agenda for the February 27 video call of WASI Subgroup

  • Where: zoom.us
  • When: February 27, 17:00-18:00 UTC
  • Location: link on calendar invite
  • Contact:

Registration

None required if you've attended before. Email Dan Gohman to sign up if it's your first time. The meeting is open to CG members only.

Logistics

The meeting will be on a zoom.us video conference. Installation is required, see the calendar invite.

Agenda items

  1. Opening, welcome and roll call
    1. Please help add your name to the meeting notes.
    2. Please help take notes.
    3. Thanks!
  2. Proposals and discussions
    1. Whole-program LTO coming:
    2. Frame-buffer API:
      • WebAssembly#229
      • The process for designing and submitting new API proposals is still being figured out, so in addition to the proposal, let's also talk about what we can do to make the process easier.
    3. Crypto API!
      • WebAssembly#231
      • What criteria should we apply?
      • We can also talk about process.

Meeting Notes

Attendees:

Dan Gohman Mark McCaskey Eric Rosenberg Mark S. Miller Peter Huene Yury Delendik Luke Wagner Daiki Ueno Johnnie Birch Lee Campbell Benjamin Brittain Aaron Turner Pat Hickey Ralph Squillace Sam Clegg

Meeting notes:

Whole-program LTO coming: WebAssembly/tool-conventions#134 Smaller binary size, optimization of combining libraries with Wasm binary (for example libc) Frame-buffer API: WebAssembly#229 The process for designing and submitting new API proposals is still being figured out, so in addition to the proposal, let's also talk about what we can do to make the process easier. Aaron: Idea: add a short and sweet markdown document laying out the steps for a proposal Aaron: I wouldn’t mind writing this up. It’s already pretty much already in my PR. So it’s just cleaning that up and we would be good to go :) Josh Triplett’s talk at Wasm SF was helpful, but a bit outdated even though it was only given a few months ago.

Crypto API! WebAssembly#231 What criteria should we apply? We can also talk about process. Being developed to support running wasm within a trusted execution environment, but intending this crypto API to have broader use cases. Enarx: https://github.com/enarx/enarx/wiki Prerequisite for sockets support Lots of interest in sockets support. Sockets dependency on merging read/write with send/recv? Don’t over-rotate on POSIX. How much appetite should we have for prototyping? Feature flags are a great way to support this Declare ahead of time what the process is. Maybe it’s ok to use alternate names, as long as we document what’s going to happen. And maybe use polyfills to ease transitions. Action item: Dan to write up a brief README for how to prototype a new feature. Also add things to watch out for. Separate experimental repo? Directory? Maybe just put features in ephemeral/snapshot Back on read/write - we don’t want to over-rotate on POSIX, but we do want a general read/write? We are heavily influenced by POSIX here.