Skip to content

Latest commit

 

History

History
175 lines (137 loc) · 12.9 KB

02.md

File metadata and controls

175 lines (137 loc) · 12.9 KB

Ecma logo

Agenda for the 106th meeting of Ecma TC39

  • Host: F5
  • Dates and times:
    • 10:00 to 17:00 PST (America/Los_Angeles) on 18 February 2025
    • 10:00 to 17:00 PST (America/Los_Angeles) on 19 February 2025
    • 10:00 to 16:00 PST (America/Los_Angeles) on 20 February 2025
  • Location: Seattle, WA
  • Attendee information: https://github.com/tc39/Reflector/issues/547
  • Total duration of scheduled discussions: dynamically computed total of timeboxes on the agenda
gantt
  1 month before the meeting: milestone, 2025-01-08 10:00-0800, 1m
  Proposal advancement deadline: milestone, 2025-02-08 10:00-0800, 1m
  Schedule constraint deadline: milestone, 2025-02-15 10:00-0800, 1m
  Day 1 : day1, 2025-02-18 10:00-0800, 8h
  Day 2 : day2, 2025-02-19 10:00-0800, 8h
  Day 3 : day3, 2025-02-20 10:00-0800, 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('2025-02-18T10:00[America/Los_Angeles]')
  .withTimeZone(Temporal.Now.timeZoneId()) // your time zone
  .toLocaleString()

Background:

Agenda topic rules

Deadline for advancement eligibility: February 8th, 10:00 PST

  • 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

  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. Project Editors’ Reports

    1. ECMA262 Status Updates (15m)
    2. ECMA402 Status Updates (15m)
    3. ECMA404 Status Updates (15m)
    4. Test262 Status Updates (15m)

  8. Task Group Reports

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

  9. Updates from the CoC Committee (5m)

  10. Web compatibility issues / Needs Consensus PRs

    timebox topic presenter
    15m Don't call well-known Symbol methods for RegExp on primitive values Gus Caplan, Luca Casonato

  11. Overflow from previous meeting

    timebox topic presenter

  12. Short (≤30m) Timeboxed Discussions

    timebox topic presenter

  13. Proposals

    stage timebox topic presenter
    3 5m Float16Array for stage 4 (spec PR) Kevin Gibbons
    3 10m Explicit Resource Management Needs Consensus PR (PR) Ron Buckton
    3 15m Redeclarable global eval vars for stage 4 (spec PR) Shu-yu Guo
    3 15m RegExp Escaping for stage 4 (spec PR) Jordan Harband
    3 20m Temporal normative PR and status update (slides) Philip Chimento
    3 30m Intl Locale Info API Update in Stage 3 (PR, slide) Frank Yung-Fong Tang
    3 30m Decorators implementation updates Kristen Hewell Garrett
    2.7 10m ShadowRealm status update (slides) Philip Chimento
    2.7 15m import defer for Stage 3 (tests: all PRs linked to tc39/test262#4215) Nicolò Ribaudo
    2 30m Immutable ArrayBuffer for stage 2.7 Mark Miller
    2 45m Records & Tuples future directions temp checks Ashley Claymore
    1 30m Limited ArrayBuffer update: stay on stage 1 or withdraw?, slides Jack Works
    1 30m Stabilize integrity traits status update Mark Miller
    1 60m A unified vision for measure and decimal (slides Jesse Alama
    1 60m Stable Formatting update (PR, slides) Eemeli Aro
    0 30m Error Stack Accessor for stage 1 or 2 Jordan Harband
    0 30m Math.clamp for Stage 1 or 2 Oliver Medhurst
    0 30m Error.captureStackTrace (slides) for Stage 1 Matthew Gaudet
    0 30m Curtailing the power of "Thenables" (Slides TBD) for Stage 1 Matthew Gaudet
    0 30m Number.isSafeNumeric (slides) for Stage 1 ZiJian Liu
    45m Decision Making through Consensus - take 2 Michael Saboff

  14. Longer or open-ended discussions

    timebox topic presenter
    60m (fine to be shorter) Language design goal for consensus: Things should layer (slides) Daniel Ehrenberg

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

    topic presenter

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

  17. Other business

    1. Thank host

  18. 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 available from 11:30pm to ~12:30pm on each day.
  • Kristen Hewell Garrett will not be available on Wednesday, Feb 19th until 14:00 PST
  • Matthew Gaudet will be unavailable the afternoon of Thursday Feb 20th.
  • Matthew Gaudet would prefer Error.captureStackTrace, Curtailing the power of "thenables", and Error Stack Accessor happen between 12:00 and 3:00 PST
  • Eemeli Aro will be unavailable during the afternoons of each day.
  • Philip Chimento: mild preference to present ShadowRealm and Temporal back to back, if possible.
  • ZiJian Liu: hope to schedule Number.isSafeNumeric during the last two hours of the first and second days(15:00 - 17:00 PST), or the last hour of the final day(15:00 - 16:00 PST).

Late-breaking Schedule Constraints