Skip to content

01.md

Latest commit

 

History

History
162 lines (122 loc) · 10.8 KB

01.md

File metadata and controls

162 lines (122 loc) · 10.8 KB

Ecma logo

Agenda for the 112th meeting of Ecma TC39

  • Host: Remote
  • Dates and times:
    • 10:00 to 15:00 EST (America/Port-au-Prince, UTC−5) on 20 January 2026
    • 10:00 to 15:00 EST (America/Port-au-Prince, UTC−5) on 21 January 2026
  • Location: Remote
  • Attendee information: https://github.com/tc39/Reflector/issues/572
  • Total duration of scheduled discussions: dynamically computed total of timeboxes on the agenda
gantt
  1 month before the meeting: milestone, 2025-12-20 10:00-0500, 1m
  Proposal advancement deadline: milestone, 2026-01-10 10:00-0500, 1m
  Schedule constraint deadline: milestone, 2026-01-17 10:00-0500, 1m
  Day 1 : day1, 2026-01-20 10:00-0500, 7h
  Day 2 : day2, 2026-01-21 10:00-0500, 7h
  todayMarker stroke-width:5px,stroke:#0f0,opacity:0.5
Loading

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

Temporal.ZonedDateTime.from('2026-01-20T10:00[America/Port-au-Prince]')
  .withTimeZone(Temporal.Now.timeZoneId()) // your time zone
  .toLocaleString();

Background:

Agenda topic rules

Deadline for advancement eligibility: January 10th 10:00 America/Port-au-Prince

  • 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, 10m)

    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

  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)
    2. ECMA402 Status Updates (1m)
    3. ECMA404 Status Updates (1m)
    4. Test262 Status Updates (5m)

  8. Task Group Reports

    1. TG3: Security (1m)
    2. TG4: Source Maps (5m)
    3. TG5: Experiments in Programming Language Standardization (5m)

  9. Updates from the CoC Committee (1m)

  10. Web compatibility issues / Needs Consensus PRs

    timebox topic presenter
    10m Normative: Add 1 new numbering system "tols" for Unicode 17 #1035 Shane F. Carr

  11. Overflow from previous meeting

    timebox topic presenter

  12. Short (≤30m) Timeboxed Discussions

    timebox topic presenter

  13. Proposals

    stage timebox topic presenter
    3 10m Upsert for Stage 4 (Slides) (PR#3740) Daniel Minor
    3 45m Temporal update and needs-consensus PRs (slides) Philip Chimento
    2.7 45m Intl Era/Month Code for Stage 3 (slides, PR #99, PR #101, PR #102, PR #108) Ben Allen
    2 5m ⌛️ Withdraw function.sent Jordan Harband
    2 30m deferred re-exports update (slides) Nicolò Ribaudo
    1 3m Withdrawing Intl.UnitFormat Chris de Almeida
    1 30m Import Sync for Stage 2 (slides) Guy Bedford
    0 30m Error option limit for Stage 1 Ruben Bridgewater
    0 30m Error option framesAbove for Stage 1 Ruben Bridgewater
    0 60m Composable value-backed accessors for Stage 1 (slides) Lea Verou

  14. Longer or open-ended discussions

    timebox topic presenter
    60m+ Stage 3 Proposal Review (Stage 2/2.7 time permitting) Peter Klecha

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

    topic presenter
  1. Other business
    1. Thank host
  2. 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

  • Ioanna Dimitriou (IOA) is only available on the 20th of January, and would like to be present for the Temporal item, and ideally also for the Intl Era/Month Code item.

Late-breaking Schedule Constraints

  • Ron Buckton will not be available on January 20th. While he would like to be present for "Composable Value-backed accessors", if that is not feasible then Michael Ficarra or Kevin Gibbons will be able to cover his position. He would also like to be present for the Stage 3 proposal review, if possible.
  • Lea Verou will be intermittently not available on January 20th, please don't move "Composable Value-backed accessors" to the previous day.