Skip to content

Latest commit

 

History

History
176 lines (135 loc) · 13.2 KB

02.md

File metadata and controls

176 lines (135 loc) · 13.2 KB

Ecma logo

Agenda for the 100th meeting of Ecma TC39

  • Host: ServiceNow
  • Dates and times:
    • 10:00 to 17:00 PST (America/Los_Angeles) on Tuesday 6 February 2024
    • 10:00 to 17:00 PST (America/Los_Angeles) on Wednesday 7 February 2024
    • 10:00 to 16:00 PST (America/Los_Angeles) on Thursday 8 February 2024
  • Location: San Diego, CA, USA
  • Attendee information: https://github.com/tc39/Reflector/issues/516
gantt
  1 month before the meeting: milestone, 2024-01-06 10:00-0800, 1m
  Proposal advancement deadline : milestone, 2024-01-27 10:00-0800, 1m
  Day 1 : day1, 2024-02-06 10:00-0800, 7h
  Day 2 : day2, 2024-02-07 10:00-0800, 7h
  Day 3 : day3, 2024-02-08 10:00-0800, 6h
  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('2024-02-06T10:00[America/Los_Angeles]')
  .withTimeZone(Temporal.Now.timeZoneId()) // your time zone
  .toLocaleString()

Background:

Agenda topic rules

Deadline for advancement eligibility: January 27th, 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, 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)

  2. Find volunteers for note taking

    1. Note about meeting transcriptions

  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)

  9. TG5 charter and chair(s) appointment (15m, slides, Mikhail Barash)

  10. Updates from the CoC Committee (5m)

  11. Web compatibility issues / Needs Consensus PRs

    ✓ timebox topic presenter
    10m needs consensus: tc39/process-document#38: refactor the proposal stages table for better communication Michael Ficarra
    10m Allow locale based ignorePunctuation default for Collator #833 Frank Yung-Fong Tang
    10m ApplyUnicodeExtensionToTag and ResolveLocale set the result record's internal slots to non-canonical values #846 Frank Yung-Fong Tang
    30m Down with [[VarNames]] #3226 Shu-yu Guo
    10m Allow Annex B scripts to start with --> (#3244) Nicolò Ribaudo

  12. Overflow from previous meeting

    ✓ timebox topic presenter

  13. Short (≤30m) Timeboxed Discussions

    ✓ timebox topic presenter
    5m status of the IEEE Software paper about TC39 (slides TBD) Mikhail Barash
    10m collecting user feedback on syntactic proposals (slides TBD) Rolf Glomsrud, Yulia Startsev, Mikhail Barash

  14. Proposals

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

    ✓ stage timebox topic presenter
    3 5m Set Methods bugfix and update Kevin Gibbons
    3 30m Intl.DurationFormat stage 3 update (slides TBD) Ben Allen
    3 45m Temporal update (slides TBD) Philip Chimento
    2 60m Throw Expressions update or stage 2.7 (slides, spec: option 1/option 2) Ron Buckton
    2 60m Uint8Array Base64 for stages 2.7 and 3 (spec, tests, slides) Kevin Gibbons
    2 60m ShadowRealms update and request for stage 3 (slides, Web APIs) Leo Balter
    1 30m iterator sequencing for stage 2 (spec text, slides) Michael Ficarra
    1 30m joint iteration for stage 2 (spec text, slides) Michael Ficarra
    1 30m Extractors update (slides) Ron Buckton
    1 30m Decimal Decimal for stage 2 (slides TBD) Jesse Alama
    1 30m Math.sum for stage 2 (slides) Kevin Gibbons
    1 45m ESM Phase Imports for stage 1 (slides TBD) Guy Bedford
    1 60m Intl.MessageFormat update and discussion (slides TBD) Eemeli Aro
    0 20m iterator unique for stage 1 (slides) Michael Ficarra
    0 30m iterator chunking for stage 1 (slides) Michael Ficarra
    0 30m Micro and mini waits in JS for stage 1 Shu-yu Guo
    0 30m Raw string literals for stage 1 (slides TBD) HE Shi-Jun (hax)
    0 45m "Discard" (void) Bindings for stage 1 (slides) Ron Buckton
    0 90m Function and Object Literal Element Decorators for stage 1 (slides) Ron Buckton

  15. Longer or open-ended discussions

    ✓ timebox topic presenter
    45m Can we reach consensus on what is Consensus? (slides) Michael Saboff

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

    ✓ topic presenter

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

  18. Other business

    1. Thank host

  19. Adjournment

Schedule constraints

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

Normal Constraints

  • Function and Object Literal Element Decorators has a 90 minute timebox. While this is being proposed as a single proposal, the presentation can be split into 60-minute and 30-minute timeboxs focusing on Functions and Object Literal Elements, respectively, depending on the needs of the chairs. — Ron Buckton
  • Guy Bedford will not be available after 12 noon on the afternoon of 8 Feb.

Late-breaking Schedule Constraints