Skip to content

Latest commit

 

History

History
198 lines (157 loc) · 16.8 KB

09.md

File metadata and controls

198 lines (157 loc) · 16.8 KB
Raw

Ecma logo

Agenda for the 98th meeting of Ecma TC39

  • Host: Bloomberg
  • Dates and times:
    • 10:00 to 17:00 JST (Asia/Tokyo) on 26 September 2023
    • 10:00 to 17:00 JST (Asia/Tokyo) on 27 September 2023
    • 10:00 to 16:00 JST (Asia/Tokyo) on 28 September 2023
  • Location: TOKYO, JAPAN
  • Attendee information: https://github.com/tc39/Reflector/issues/499
gantt
  1 month before the meeting: milestone, 2023-08-26 10:00+0900, 1m
  Proposal advancement deadline : milestone, 2023-09-16 10:00+0900, 1m
  Day 1 : day1, 2023-09-26 10:00+0900, 7h
  Day 2 : day2, 2023-09-27 10:00+0900, 7h
  Day 3 : day3, 2023-09-28 10:00+0900, 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.

// UPDATE THE START DATE AND IANA TIMEZONE NAME BELOW AND DELETE THIS COMMENT
Temporal.ZonedDateTime.from('2023-09-26T10:00[Asia/Tokyo]')
  .withTimeZone(Temporal.Now.timeZoneId()) // your time zone
  .toLocaleString()

Background:

Agenda topic rules

Deadline for advancement eligibility: September 16th, 10:00 JST

  • 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, 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 slides (15m, Samina Husain)

  7. Project Editors’ Reports

    1. ECMA262 Status Updates (slides) (10m, Kevin Gibbons)
    2. ECMA402 Status Updates (15m, Ujjwal Sharma)
    3. ECMA404 Status Updates (1m, Chip Morningstar)
    4. Test262 Status Updates (15m, Richard Gibson / Jordan Harband)

  8. Task Group Reports

    1. TG3: Security (slides) (10m, Michael Ficarra)
    2. TG4: Source Maps (5m, Jon Kuperman)

  9. Updates from the CoC Committee (5m, Jordan Harband)

  10. Web compatibility issues / Needs Consensus PRs

    ✓ timebox topic presenter
    5m needs consensus: ecma402#758 Normative: Change the hourCycle default logic Ben Allen
    10m ⌛️ needs consensus: ecma402#780 Normative: Added note about sets of locales for web browser implementations needing to not change as a result of user behaviour #780 Ben Allen
    10m needs consensus: ecma402#811 Normative: Fix order of rounding* option reads and resolvedOptions() Ben Allen
    10m Update GetSubstitution to match reality Richard Gibson
    20m ⌛️ needs consensus: ecma402#788 Normative: Allow UTC offset time zones Ben Allen

  11. Overflow from previous meeting

    ✓ timebox topic presenter

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

  13. Short (≤30m) Timeboxed Discussions

    ✓ timebox topic presenter

  14. Proposals

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

    ✓ stage timebox topic presenter
    3 5m Array Grouping update Jordan Harband
    3 5m ArrayBuffer transfer update Jordan Harband
    3 15m JSON.parse source text access update (slides) Richard Gibson
    3 15m Import Attributes Implementer Feedback (slides) Daniel Minor
    3 30m Iterator helper web incompat (PR) Shu-yu Guo & Michael Ficarra
    3 30m Resizable buffers for Stage 4 (slides) Shu-yu Guo
    3 30m ShadowRealm: Implementer Feedback and Demotion to Stage 2 (slides) Daniel Minor
    3 30m Stage 3 update of Intl Locale Info API (Slides) Frank Yung-Fong Tang
    2 5m Symbol predicates update Jordan Harband
    2 15m Async Iterator Helpers status update (slides; tldr work continues) Kevin Gibbons
    2 15m AsyncContext update (slides) Chengzhong Wu
    2 30m Throw Expressions for Stage 3 (slides, spec) Ron Buckton
    2 45m Uint8Array-Base64: are we doing multi-shot? (issue) Kevin Gibbons
    1 5m Pattern Matching update Jordan Harband
    1 15m Withdrawing FinalizationRegistry cleanupSome (slides) Daniel Ehrenberg
    1 20m Withdrawing numeric literal suffixes (slides) Daniel Ehrenberg
    1 30m Withdrawing operator overloading (slides) Daniel Ehrenberg
    1 30m reviving export default from; for stage 2? Jordan Harband
    1 30m Get Intrinsics for stage 2, with two possible shapes/paths? Jordan Harband
    1 30m DataView get/set Uint8Clamped methods for stage 2 Jordan Harband
    1 30m RegExp.escape for stage 2 Jordan Harband
    1 45m Intl.MessageFormat: Stage 1 update and discussion (slides) Eemeli Aro
    1 60m Structs and shared structs update (slides) Shu-yu Guo
    1 60m Decimal: Stage 1 update and discussion (slides) Jesse Alama
    1 60m Type Annotations: Stage 1 update and discussion (slides) Daniel Ehrenberg and Daniel Rosenwasser
    0 1m Withdrawing Symbol.thenable Jordan Harband
    0 30m iterator sequencing for Stage 1 (slides) Michael Ficarra
    0 30m joint iteration for Stage 1 (slides) Michael Ficarra
    0 30m Stable Formatting for Stage 1 (slides) Eemeli Aro
    0 30m Negated in and instanceof operators for Stage 1 (slides) Pablo Gorostiaga Belio
    0 30m Locale Extensions for Stage 1 (slides Ben Allen

  15. Longer or open-ended discussions

    ✓ timebox topic presenter
    60m TDZ, what is it good for? (slides) Shu-yu Guo
    90m reducing wasted effort due to proposal churn (continued) (slides) Michael Ficarra
    60m Stop coercing things pt 2 (slides) Kevin Gibbons

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

    ✓ topic presenter

  17. Other business

    1. Thank host

  18. Adjournment

Schedule constraints

Schedule constraints should be supplied here 48 hours before the meeting begins so that the Chairs can take them into account when preparing the schedule.

  1. Custom numeric literals must be after operator overloading (since the decisions are dependent on each other).

Normal Constraints

  • Caridy Patino and Leo Balter would like to be present for the ShadowRealm topic but are limited to the first 2 hours for the meeting each day (10:00 to 12:00 JST).
  • Philip Chimento: Would like to be present if possible for (in order of most to least preference) ShadowRealm, stop coercing things, Decimal, withdrawing cleanupSome, get intrinsics. Not available on Day 1 (26th).
  • Peter Hoddie: Would like to be present for Base64. Available for first three hours of Day 1 (26th) and Day 3 (28th).

Late-breaking Schedule Constraints

  • Frank Tang: Can only attend the meeting on Day 1 (26th) and Day 2 (27th).

Dates and locations of future meetings

Dates Location Host
2023-11-27 to 2023-11-30 Remote: "SF"
2024-02-06 to 2024-02-08 San Diego, US ServiceNow
2024-04-08 to 2024-04-11 Remote: "Baltimore"