Skip to content

Latest commit

 

History

History
187 lines (148 loc) · 16.6 KB

04.md

File metadata and controls

187 lines (148 loc) · 16.6 KB
Raw

Ecma logo

Agenda for the 101st meeting of Ecma TC39

  • Host: Remote
  • Dates and times:
    • 10:00 to 15:00 ET (America/New_York) on 8 April 2024
    • 10:00 to 15:00 ET (America/New_York) on 9 April 2024
    • 10:00 to 15:00 ET (America/New_York) on 10 April 2024
    • 10:00 to 15:00 ET (America/New_York) on 11 April 2024
  • Attendee information: https://github.com/tc39/Reflector/issues/522
gantt
  1 month before the meeting: milestone, 2024-03-08 10:00-0400, 1m
  Proposal advancement deadline: milestone, 2024-03-29 10:00-0400, 1m
  Schedule constraint deadline: milestone, 2024-04-05 10:00-0400, 1m
  Day 1 : day1, 2024-04-08 10:00-0400, 7h
  Day 2 : day2, 2024-04-09 10:00-0400, 7h
  Day 3 : day3, 2024-04-10 10:00-0400, 7h
  Day 4 : day4, 2024-04-11 10:00-0400, 7h
  todayMarker stroke-width:5px,stroke:#0f0,opacity:0.5

For meeting times in your timezone, visit Temporal docs and run the code below in the devtools console.

Temporal.ZonedDateTime.from('2024-04-08T10:00[America/New_York]')
  .withTimeZone(Temporal.Now.timeZoneId()) // your time zone
  .toLocaleString()

Background:

Agenda topic rules

Deadline for advancement eligibility: March 29th, 10:00 ET

  • 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. Note: an unmerged PR counts as “added” for the purposes of this requirement.
  2. Proposals seeking feedback at stage 0 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 stage 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 must link to a proposal repository and they should link to supporting materials when possible.
  4. Proposals looking to advance to stages 2, 2.7, 3, or 4, as well as other normative changes to the standard or proposals in stage 3 or later looking to achieve consensus, must be added (and noted as such) along with links to the supporting materials prior to the deadline, or else delegates may withhold consensus for advancement solely on the basis of missing the deadline.
    1. If the supporting materials change substantially after the deadline, delegates may withhold consensus for advancement, based on the committee’s judgment.
    2. For urgent normative changes, the committee is expected to be more forgiving of a missed deadline, since there is generally less material to review than in a stage advancement.
    3. Proposals looking to advance to stage 4 must link to a pull request into the spec, since the process requires one.
  5. 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 key

When applicable, use these emoji as a prefix to the agenda item topic.

Emoji Meaning
❄️ hard schedule constraints apply to this agenda item (e.g. presenter)
🔒 schedule constraints apply to this agenda item
⌛️ late addition for stage advancement and/or schedule prioritization
🔁 continuation of a previous agenda item

Agenda items

  1. Opening, welcome and roll call (Chair)

    1. Opening of the meeting
    2. TC39 follows its Code of Conduct
    3. Introduction of attendees
    4. Host facilities, local logistics
    5. Quick recap of meeting IPR policy
    6. Overview of communication tools
    7. Reminder to review Github Delegate teams (Jordan Harband)
    8. TC39 stenography support and legal disclaimer
    9. Solar eclipse reminder: https://www.nasa.gov/news-release/how-to-watch-upcoming-total-solar-eclipse-with-nasa-from-anywhere/

  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. Secretary's Report (15m, Samina Husain, slides)

  7. Project Editors’ Reports

    1. ECMA262 Status Updates (slides) (5m, Kevin Gibbons)
      1. update on automatically producing print-quality PDFs (30m, Michael Ficarra)
    2. ECMA402 Status Updates (15m)
    3. ECMA404 Status Updates (1m, Chip Morningstar)
    4. Test262 Status Updates (10m, Philip Chimento)

  8. Task Group Reports

    1. TG3: Security (5m, Chris de Almeida)
      1. TG3 convenors appointment (5m, Ujjwal Sharma)
    2. TG4: Source Maps (5m, Jon Kuperman) (slides)
    3. TG5: Experiments in Programming Language Standardization (5m) (slides)

  9. Updates from the CoC Committee (5m, Chris de Almeida)

  10. Web compatibility issues / Needs Consensus PRs

    ✓ timebox topic presenter
    15m Reality and spec differ on property key resolution timing for o[p] = f() (PR) Ross Kirsling

  11. Overflow from previous meeting

    ✓ timebox topic presenter

  12. Short (≤30m) Timeboxed Discussions

    ✓ timebox topic presenter
    1m “array last” proposal withdrawn Jordan Harband
    1m TC39 website - call for translators - GH issue Chris de Almeida

  13. Proposals

    ✓ represents an agenda item which has been presented, and does not indicate stage advancement

    ✓ stage timebox topic presenter
    3 10m Duplicate named capture groups for stage 4 (PR, tests) Kevin Gibbons
    3 10m Set methods for stage 4 (PR, tests) Kevin Gibbons
    3 15m Temporal normative bugfix (PR, slides) Philip Chimento
    3 30m Explicit Resource Management Normative Updates and Needs Consensus PRs (slides, PRs) Ron Buckton
    2 10m joint iteration: confirm our stance on #1 Michael Ficarra
    2 15m ❄️ AsyncContext Stage 2 updates Justin Ridgewell
    2 20m Promise.try for Stage 2.7 Jordan Harband
    2 20m RegExp.escape for stage 2.7 Jordan Harband
    2 30m Deferred import evaluation for Stage 2.7 (without "tree-shakeable" exports) (slides) Nicolò Ribaudo
    2 30m Treeshakeable/deferred re-exports status update (slides) Nicolò Ribaudo
    2 30m Make eval-introduced global vars redeclarable for stage 2.7 (slides) Shu-yu Guo
    2 30m Iterator.range for stage 2.7 Jack Works
    2 30m Math.sumExact for stage 2.7 (slides) Kevin Gibbons
    2 60m Discussing new directions for R&T (slides, related repo) Ashley Claymore
    2 60m Array.isTemplateObject next steps (slides) Daniel Ehrenberg
    1 15m Atomics.microwait() (without mini wait) for stage 2 (slides) Shu-yu Guo
    1 30m eval/new Function changes for Trusted Types as Normative PR or Stage 3 (PR, slides) Nicolò Ribaudo
    1 30m ESM Source Phase status update and layering change (slides Guy Bedford
    1 30m Module sync assert for stage 2 Jack Works
    1 30m Intl.MessageFormat status update, maybe for stage 0? Eemeli Aro
    1 30m Discard Bindings for Stage 2 (slides, spec) Ron Buckton
    1 45m Extractors for Stage 2 (spec, slides) Ron Buckton
    1 60m Decimal for stage 2 (slides) Jesse Alama
    1 60m Shared structs discussion (slides) Shu-yu Guo
    0 30m bringing back Error.isError, for stage 1 or 2 (or even 2.7) Jordan Harband
    0 30m Strict Enforcement of 'using' for Stage 1 or 2 (slides, spec) Ron Buckton
    0 60m ⌛️ Signals for Stage 1 (slides) Daniel Ehrenberg and Jatin Ramanathan

  14. Longer or open-ended discussions

    ✓ timebox topic presenter
    45m Stop coercing things pt 4 (slides) Kevin Gibbons

  15. Overflow from timeboxed agenda items (in insertion order)

    ✓ topic presenter

  16. Incubation call chartering (15m on the last day)

  17. Adjournment

Schedule constraints

Schedule constraints should be supplied here as soon as possible, and at least three days before the meeting begins so that the Chairs can take them into account when preparing the schedule.

Normal Constraints

  • Ron Buckton will not be present on Day 1 of the plenary (April 8), but would like to be present for (w/highest priority first) Shared structs discussion, Pattern Matching, R&T, Atomics.microwait(), and Signals.
  • Nicolò Ribaudo will not be available on Day 4, and would like to be present for (sorted by priority) ESM source phase, module sync assert, R&T.
  • The changes for Trusted Types presentation should be before Array.isTemplateObject, ideally in the same day
  • Eemeli Aro will not be present on Day 2 of the plenary (April 9).
  • Ross Kirsling will only be available during the first hour of each day.
  • Jesse Alama prefers to present the decimal presentation sometime in the first two hours. Any day is fine. A co-presenter in Asia (TC39 delegate from Albibaba) will make a 5-minute contribution during the decimal presentation, hence the request to have the presentation within the first two hours.
  • Justin Ridgewell will not be available to present AsyncContext on day 1 (April 8).
  • Andreu Botella will not be available for the first two hours of day 4 (April 11), and would like to be present for AsyncContext.

Late-breaking Schedule Constraints