Skip to content

Latest commit

 

History

History
147 lines (109 loc) · 8.19 KB

06.md

File metadata and controls

147 lines (109 loc) · 8.19 KB
Raw

Ecma logo

Agenda for the 102nd meeting of Ecma TC39

  • Host: Mozilla & Aalto University
  • Dates and times:
    • 10:00 to 17:00 TZ (Europe/Helsinki) on 11 June 2024
    • 10:00 to 17:00 TZ (Europe/Helsinki) on 12 June 2024
    • 10:00 to 16:00 TZ (Europe/Helsinki) on 13 June 2024
  • Location: Helsinki, Finland
  • Attendee information: https://github.com/tc39/Reflector/issues/527
gantt
  1 month before the meeting: milestone, 2024-05-11 10:00+0300, 1m
  Proposal advancement deadline: milestone, 2024-06-01 10:00+0300, 1m
  Schedule constraint deadline: milestone, 2024-06-08 10:00+0300, 1m
  Day 1 : day1, 2024-06-11 10:00+0300, 8h
  Day 2 : day2, 2024-06-12 10:00+0300, 8h
  Day 3 : day3, 2024-06-13 10:00+0300, 8h
  todayMarker stroke-width:5px,str3ke:#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-06-11T10:00[Europe/Helsinki]')
  .withTimeZone(Temporal.Now.timeZoneId()) // your time zone
  .toLocaleString()

Background:

Agenda topic rules

Deadline for advancement eligibility: June 4th, 10:00 EEST

  • 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

  11. Overflow from previous meeting

    timebox topic presenter

  12. Short (≤30m) Timeboxed Discussions

    timebox topic presenter

  13. Proposals

    stage timebox topic presenter
    3 15m Avoid second pass/buffer in base64 setFromBase64/setFromHex methods (issue, PR) Kevin Gibbons
    2.7 15m Promise.try for stage 3 (tests) Jordan Harband

  14. Longer or open-ended discussions

    timebox topic presenter

  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

  • Jordan Harband is only available either the first two hours of each day, or the last two hours of each day; whichever is easier for the chairs to arrange.

Late-breaking Schedule Constraints