WG-02-28.md

June 5, 2020 ยท View on GitHub

WebAssembly logo

Agenda for the February 28th video call of WebAssembly's Working Group

  • Host: Google Hangouts
  • Date and Time: February 28th, 2018 at 5pm-6pm UTC / February 28th, 2018 at 9am-10am PT
  • Time Date Link: Link
  • Location: Brad will email Google Hangouts link to WG members + registered CG guests prior to the meeting
  • Contact:

Registration

If you are a Working Group member no registration is required.

If you are a Community Group member who would like to observe, please register here: https://goo.gl/forms/HD2kLCM0iSKk7AVl1

Logistics

The meeting will be a Google Hangouts call.

Agenda items

  1. Opening, welcome and roll call
    1. Opening of the meeting
    2. Introduction of attendees
  2. Find volunteers for note taking (chair to volunteer).
  3. Adoption of the agenda
  4. Proposals and discussions
    1. Discussion on the process of branching + Working Drafts.
    2. Discussion on status of the Working Draft.
    3. Future meetings
      1. Confirm next meeting date + time.
      2. Handing of agenda for in person meeting.
  5. Closure

Agenda items for future meetings

None.

Schedule constraints

None.

Meeting Notes

Opening, welcome and roll call

  • JF Bastien
  • Sam Clegg
  • Brad Nelson
  • Kenneth Rohde Christiansen
  • Jacob Gravelle
  • Brad Nelson
  • Andreas Rossberg
  • Derek Schuff
  • Michael Holman
  • Eric Holk
  • Michael Ferris
  • Wouter van Oortmerssen
  • Limin Zhu
  • Luke Wagner
  • Edgar Pek
  • Peter Jensen
  • Arun Purushan
  • Deepti Gandluri

Opening of the meeting

Introduction of attendees

Find volunteers for note taking (chair to volunteer).

Brad Nelson

Adoption of the agenda

JF Seconds.

Discussion on the process of branching + Working Drafts.

   * Do we accumulate all master changes into the next Working Draft?
   * When do we start new REC trains?
   * Context: https://github.com/WebAssembly/spec/pull/714

Discussion on versions, keeping several versions in flight. When to hand the w3c new drafts. Do we want to take new features? What about non-trapping conversions?

Andreas: We should not let new features creep in.

Luke: For now we do the cherry-picking, but later it will be more mechanical.

Andreas: I'm not aware of any that are ready to be merged.

Discussion

Vague consensus is we treat v1 specially, we only land editorial / mvp fixes. We'll sort out later when to start a v2 train.

Discussion on status of the Working Draft.

   * Appeal for more chapter [reviewers](https://github.com/WebAssembly/spec/issues?q=is%3Aissue+is%3Aopen+%5Bspec+review%5D+label%3Aeditorial)

Got a few more owners for various chapters.

Discussion: Useful to have more exhaustive tests.

Luke: Core spec we've been assuming it's fairly good.

JF: Not in the test262 sense. I don't think we want to gate anything on it, not sure we want to block on it.

Andreas: The way the test suite is structured, there's mostly one file for each construct. There's some earlier tests that don't quite fit into that scheme. Within a single file it's hard to tell what any one test tests.

JF: Should we ask Dan?

Luke: Initially Dan is on the hook for JS + Web spec.

AI: bradnelson: open issue on making tests comprehensive. https://github.com/WebAssembly/spec/issues/739

   * Review of open issue:
      * https://github.com/WebAssembly/spec/issues

Some triage of issues.

Future meetings

   1. Confirm next meeting date + time.

March 14th - 11pm PST --- Brad to schedule. [Brad managed to mix up weeks on this, will re-schedule for the following week March 21 at 11pm PT]

Upcoming in-person meeting:

* Hosted by Fastly in San Francisco, Tuesday-Thursday April 10-12, 2018

Tentatively Brad will add agenda items for sections at WG meeting. Will start a redirect doc for WG part of the meeting.