• Host: TBD
• Dates and times:
  • 10:00 to 17:00 EDT (America/New_York, UTC-5) on 10 March 2026
  • 10:00 to 17:00 EDT (America/New_York, UTC-5) on 11 March 2026
  • 10:00 to 16:00 EDT (America/New_York, UTC-5) on 12 March 2026
• Location: New York, NY
• Attendee information: https://github.com/tc39/Reflector/issues/573
• Total duration of scheduled discussions:

gantt
  1 month before the meeting: milestone, 2026-02-10 10:00-0500, 1m
  Proposal advancement deadline: milestone, 2026-02-28 10:00-0400, 1m
  Schedule constraint deadline: milestone, 2026-03-07 10:00-0400, 1m
  Day 1 : day1, 2026-03-10 10:00-0500, 8h
  Day 2 : day2, 2026-03-11 10:00-0500, 8h
  Day 3 : day3, 2026-03-12 10:00-0500, 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('2026-03-10T10:00[America/New_York]')
  .withTimeZone(Temporal.Now.timeZoneId()) // your time zone
  .toLocaleString();

Background:

• Allen Wirfs-Brock's paper on standards committee participation for new attendees
• TC39's documentation on How to participate in meetings

Deadline for advancement eligibility: February 28th 10:00 America/New_York

• _{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.

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

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)

7. Election of the 2026 Chair Group, Convenors, and Editors (15m, Aki Rose Braun, Samina Husain)

8. Project Editors’ Reports

   1. ECMA262 Status Updates (slides) (5m, Michael Ficarra)
   2. ECMA402 Status Updates (5m)
   3. ECMA404 Status Updates (1m)
   4. Test262 Status Updates (5m)

9. Task Group Reports

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

10. Updates from the CoC Committee (1m)

11. Web compatibility issues / Needs Consensus PRs

    timebox	topic	presenter

12. Overflow from previous meeting

    timebox	topic	presenter

13. Short (≤30m) Timeboxed Discussions

    timebox	topic	presenter
    30m	Abort Protocol Discussion	James M Snell

14. Proposals

    stage	timebox	topic	presenter
    3	15m	import defer interaction with tc39/ecma262#3715, and normative PR Shield dynamic import defer against Promise.prototype monkey patch (PR#77, PR#79, slides)	Nicolò Ribaudo
    3	15m	Explicit Resource Management Conditional Stage 4 Status Update (spec PR, test262 PRs, slides)	Ron Buckton
    3	30m	Intl Era/Month Code for Stage 4 (slides, PR)	Ben Allen
    3	90m	Temporal for Stage 4 (slides, ECMA-262 PR, ECMA-402 PR)	Philip Chimento
    2.7	20m	Intl: Keep Trailing Zeros for Stage 3 (slides)	Eemeli Aro
    2.7	60m	Update on ESM Phase Imports (slides to follow)	Guy Bedford
    2	5m	Withdraw Dynamic Import Host Adjustment	Steve Hicks
    2	15m	⌛️ RegExp Buffer Boundaries for Stage 2.7 or 3 (slides, test262 PR)	Ron Buckton
    2	30m	Error Stack Accessor for Stage 2.7	Jordan Harband
    2	20m	JSON.parseImmutable update (slides)	Peter Klecha
    2	45m	Import Text for Stage 2.7 or 3 (slides, PR #10)	Eemeli Aro
    1	20m	Intl Energy Units Stage 1 Update (slides)	Shane F Carr
    1	30m	TypedArray concat for Stage 2 (slides)	James M Snell
    1	30m	TypedArray find within for Stage 2 (slides)	James M Snell
    1	30m	Intl Unit Protocol for Stage 2 (slides)	Shane F Carr
    1	60m	Amount for Stage 2 (slides)	Ben Allen
    1	60m	Thenable Curtailment for Stage 2 (Slides)	Matthew Gaudet
    1	60m	First-class Protocols Update (slides TBD)	Lea Verou
    0	30m	Iterator Includes for Stage 1, 2, or 2.7 (slides)	Michael Ficarra
    0	30m	Error code property for Stage 1, 2, or 2.7 (slides)	James M Snell

15. Longer or open-ended discussions

    timebox	topic	presenter
    60m	test262 coverage strategies	Richard Gibson
    90m	Tree-shakeable methods (slides)	Evan B Winslow
    90m	Toward structured concurrency (slides, repo for discussions)	Kevin Gibbons

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

    topic	presenter

1. Other business
   1. Thank host
2. Adjournment

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.

• Philip Chimento: Temporal not on Tuesday. Preferably on Wednesday.
• Jesse Alama (JMN): Cannot attend first half of March 11th, and not at all on March 12th. If possible, please schedule any numerics-related presentations (e.g., Amount) for Tuesday or second half of Wednesday. Since I'm likely not presenting myself, this is a violable preference, not a hard constraint.
• Nicolò Ribaudo: Cannot attend the first two hours on Thursday. I only need to be available for my topics, but I'm also interested in the thenables and abort protocol topics
• Eemeli Aro: I'm not available for the last hour of each day, and would prefer to be present for all numerics-related presentations.
• The "towards structured concurrency" item should go after (not necessarily immediately after) the "abort protocol" item.