Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
16 contributors

Users who have contributed to this file

@DanielRosenwasser @FrankYFTang @mikesamuel @littledan @ljharb @syg @mattijs @gsathya @gesa @codehag @rkirsling @pouwerkerk @pemrouz @leobalter @erights @bakkot
153 lines (122 sloc) 10.2 KB

Agenda for the 70th meeting of Ecma TC39

  • Host: Stripe
  • Dates: 04-06 June 2019
  • Times:
    • 10:00 to 17:00 CEST on 04 and 05 of June 2019
    • 10:00 to 16:00 CEST on 06 of June 2019
  • Location: details
  • Wifi: details
  • Dinner: details
  • Contact:

Logistics

Allen's paper on standards committee participation for new attendees: http://wirfs-brock.com/allen/files/papers/standpats-asianplop2016.pdf

Registration

Details

Agenda topic rules

Deadline for advancement eligibility: May 25, 2019, 18:00 UTC

  • Note: this time is selected to be precisely 10 days prior to the start of the meeting
  1. Proposals not looking to advance may be added at any time; if after the deadline, please always use a pull request so that members are notified of changes.
  2. Proposals looking to advance to stage 0 or 1 must be added (and noted as such) prior to the deadline, or else delegates may object to advancement solely on the basis of missing the deadline.
    1. Such proposals should include supporting materials when possible.
  3. Proposals looking to advance to stages 2, 3, or 4 must be added (and noted as such) along with the necessary materials prior to the deadline, or else delegates may object to advancement solely on the basis of missing the deadline.
    1. Such proposals must link to supporting materials prior to the deadline, or else delegates may object to advancement solely on the basis of missing the deadline. If these materials change substantially after the deadline, the proposal may be disqualified from advancement, based on the committee’s judgment.
    2. Proposals looking to advance to stage 4 must link to a pull request into the spec, since the process requires one.
  4. Proposal-based agenda items should be sorted primarily by stage (descending), secondarily by timebox (ascending), and finally by insertion date.

Supporting materials includes slides, a link to the proposal repository, a link to spec text, etc.; essentially, anything you are planning to present to the committee, or that would be useful for delegates to review.

Agenda items

  1. Opening, welcome and roll call

    1. Opening of the meeting (Yulia Startsev, Aki Rose, Brian Terlson)
    2. TC39 follows its Code of Conduct
    3. Introduction of attendees
    4. Host facilities, local logistics
    5. Quick recap of meeting IPR policy (Daniel Ehrenberg)
    6. Overview of communication tools (Brian Terlson)
  2. Find volunteers for note taking

  3. Adoption of the agenda

  4. Approval of the minutes from last meeting

  5. Next meeting host and logistics

  6. Updates from chair group

    1. New domain name
    2. Moving outreach groups to TC39 org
  7. Report from the Ecma Secretariat (15m, Istvan Sebestyen)

  8. Project Editors’ Reports

    1. ECMA262 Status Updates (15m)
    2. ECMA402 Status Updates (15m)
    3. ECMA404 Status Updates (15m)
    4. Test262 Status Updates (15m)
  9. Updates from the CoC Committee (15m)

  10. Web compatibility issues / Needs Consensus PRs

    timebox topic presenter
    10m HostEnsureCanCompileStrings context Mike Samuel
    10m eval(nonString) should not side effect Mike Samuel
    10m Set "name" property for anonymous functions Sathya Gunasekaran
    10m Lookup constructor.resolve only once in PerformPromise{All, Race} Sathya Gunasekaran
    30m Let all early errors be SyntaxErrors Ross Kirsling
    10m ECMA-402: Add quarter option Frank Y. Tang
    10m ECMA-402: Add dayPeriod option Frank Y. Tang
    10m ECMA-402: Add millisecondDigits option Frank Y. Tang
  11. Overflow from previous meeting

    timebox topic presenter
  12. Short (≤30m) Timeboxed Discussions

    timebox topic presenter
    15m Trusted Types Mike Samuel
  13. Proposals

    stage timebox topic presenter
    3 30m dynamic import() for Stage 4 Daniel Ehrenberg (author: Domenic Denicola)
    3 30m BigInt for Stage 4 (PR) Caio Lima
    2 30m Atomics.waitAsync asking for Stage 3 reviewers (Slides) Shu-yu Guo
    2 30m WeakRefs for Stage 3 Sathya Gunasekaran, Till Schneidereit
    2 60m Top-level await for Stage 3 Myles Borins
    1 30m For-in enumeration order for Stage 2 (slides) Kevin Gibbons
    1 60m JavaScript Standard Library for Stage 2 (slides) Mattijs Hoitink & Michael Saboff
    1 40m Intl.DisplayNames for Stage 2 Slides Frank Tang
    1 60m Optional Chaining for Stage 2 Justin Ridgewell
    1 15m Nullish Coalescing for Stage 2 Justin Ridgewell
    0 15m Array.isTemplateObject for Stage 1 or 2 Mike Samuel
    0 15m evalable for Stage 1 or 2 Mike Samuel
    0 15m Host compile value adjustment for Stage 1 or 2 Mike Samuel
    0 60m Emitter for Stage 1 (slides) Shu-yu Guo & Pedram Emrouznejad
  14. Longer or open-ended discussions

    timebox topic presenter
    30m EcmaScript security Mark S. Miller
    30m Annex B reform Mark S. Miller
    60m How should we specify Jobs precisely? (slides) Daniel Ehrenberg
    60m Title TBD Felienne Hermans
    60m JavaScript and Syntax Research Methods Yulia Startsev
    30m Status update on non-JS module types (e.g., JSON, CSS, WebIDL) Daniel Ehrenberg
  15. Overflow from timeboxed agenda items (in insertion order)

    topic presenter
  16. Other business

    1. Thank host
  17. Adjournment

Schedule constraints

  • Jordan must be present for Standard Library, but will be calling in from PT. Ideal times are at 10AM CEST sharp, or after 3PM CEST. It would also be nice to be present for TLA and Optional Chaining, if possible.
  • Felienne will only be available on Thursday, with a preference to present in the morning. Yulia will present her topic shortly after.

Dates and locations of future meetings

Dates Location Host
2019-07-23 to 2019-07-25 Redmond, WA Microsoft
2019-10-01 to 2019-10-03 New York Bloomberg
2019-12-03 to 2019-12-05 San Francisco, CA Salesforce
You can’t perform that action at this time.