Skip to content

Commit d14a1b0

Browse files
ctcpipctcpip
committed
✨ 2025 November agenda
1 parent 066e387 commit d14a1b0

File tree

2 files changed

+146
-1
lines changed

2 files changed

+146
-1
lines changed

‎2025/11.md‎

Lines changed: 145 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,145 @@
1+
<img src="../images/Ecma_RVB-003.jpg" align="right" height="70" alt="Ecma logo" /> <!-- markdownlint-disable-line MD041 -->
2+
3+
# Agenda for the 111th meeting of Ecma TC39
4+
5+
- **Host**: Bloomberg
6+
- **Dates and times**:
7+
- 10:00 to 17:00 JST (Asia/Tokyo) on Tuesday 18 November 2025
8+
- 10:00 to 17:00 JST (Asia/Tokyo) on Wednesday 19 November 2025
9+
- 10:00 to 16:00 JST (Asia/Tokyo) on Thursday 20 November 2025
10+
- **Location**: Tokyo, Japan
11+
- **Attendee information**: https://github.com/tc39/Reflector/issues/564
12+
- **Total duration of scheduled discussions**: ![dynamically computed total of timeboxes on the agenda](https://tc39-agenda-time.deno.dev/2025/11/)
13+
14+
```mermaid
15+
gantt
16+
1 month before the meeting: milestone, 2025-10-18 10:00+0900, 1m
17+
Proposal advancement deadline: milestone, 2025-11-08 10:00+0900, 1m
18+
Schedule constraint deadline: milestone, 2025-11-15 10:00+0900, 1m
19+
Day 1 : day1, 2025-11-18 10:00+0900, 7h
20+
Day 2 : day2, 2025-11-19 10:00+0900, 7h
21+
Day 3 : day3, 2025-11-20 10:00+0900, 7h
22+
todayMarker stroke-width:5px,stroke:#0f0,opacity:0.5
23+
```
24+
25+
For meeting times in your timezone, visit [Temporal docs](https://tc39.es/proposal-temporal/docs/) and run the code below in the devtools console.
26+
27+
```js
28+
Temporal.ZonedDateTime.from('2025-11-18T10:00[Asia/Tokyo]')
29+
.withTimeZone(Temporal.Now.timeZoneId())
30+
.toLocaleString()
31+
```
32+
33+
Background:
34+
35+
- Allen Wirfs-Brock's [paper on standards committee participation for new attendees](http://wirfs-brock.com/allen/files/papers/standpats-asianplop2016.pdf)
36+
- TC39's documentation on [How to participate in meetings](https://github.com/tc39/how-we-work/blob/HEAD/how-to-participate-in-meetings.md)
37+
38+
## Agenda topic rules
39+
40+
Deadline for advancement eligibility: [November 8th 10:00 Asia/Tokyo](https://www.timeanddate.com/countdown/winter?iso=20251118T10&p0=248&msg=111th+TC39+Plenary+in+Tokyo&font=sanserif&csz=1)
41+
42+
- <sub>Note: this time is selected to be precisely 10 days prior to the start of the meeting</sub>
43+
44+
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.
45+
1. 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.
46+
1. Such proposals *should* include supporting materials when possible.
47+
1. 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.
48+
1. Such proposals *must* link to a proposal repository and they *should* link to supporting materials when possible.
49+
1. 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.
50+
1. If the supporting materials change substantially after the deadline, delegates may withhold consensus for advancement, based on the committee’s judgment.
51+
1. 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.
52+
1. Proposals looking to advance to stage 4 *must* link to a pull request into [the spec](https://github.com/tc39/ecma262), since the [process](https://tc39.github.io/process-document/) requires one.
53+
1. Proposal-based agenda items should be sorted primarily by stage (descending), secondarily by timebox (ascending), and finally by insertion date.
54+
55+
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.
56+
57+
## Agenda key
58+
59+
When applicable, use these emoji as a prefix to the agenda item topic.
60+
61+
| Emoji | Meaning |
62+
| :---: | :--- |
63+
| ❄️ | hard schedule constraints apply to this agenda item (e.g. presenter) |
64+
| 🔒 | schedule constraints apply to this agenda item |
65+
| ⌛️ | late addition for stage advancement and/or schedule prioritization |
66+
| 🔁 | continuation of a previous agenda item |
67+
68+
## Agenda items
69+
70+
1. Opening, welcome and roll call (Chair)
71+
1. Opening of the meeting
72+
1. TC39 follows its [Code of Conduct](https://tc39.github.io/code-of-conduct/)
73+
1. Introduction of attendees
74+
1. Host facilities, local logistics
75+
1. Quick recap of meeting IPR policy
76+
1. Overview of communication tools
77+
1. Reminder to review Github Delegate teams (Jordan Harband)
78+
1. [TC39 stenography support and legal disclaimer](https://github.com/tc39/Reflector/blob/main/transcriptions.md)
79+
1. Find volunteers for note taking
80+
1. Adoption of the agenda
81+
1. Approval of the minutes from last meeting
82+
1. Next meeting host and logistics
83+
1. Secretary's Report (15m, Samina Husain)
84+
1. Project Editors’ Reports
85+
1. [ECMA262](https://github.com/tc39/ecma262) Status Updates (15m)
86+
1. [ECMA402](https://github.com/tc39/ecma402) Status Updates (15m)
87+
1. [ECMA404](https://www.ecma-international.org/publications/standards/Ecma-404.htm) Status Updates (15m)
88+
1. [Test262](https://github.com/tc39/test262) Status Updates (15m)
89+
1. Task Group Reports
90+
<!-- 1. TG2: Internationalization (5m) - in practice, this is covered via the ECMA-402 project editors' report -->
91+
1. TG3: Security (5m)
92+
1. TG4: Source Maps (5m)
93+
1. TG5: Experiments in Programming Language Standardization (5m)
94+
1. Updates from the [CoC Committee](https://tc39.es/code-of-conduct/#code-of-conduct-committee) (5m)
95+
1. [Web compatibility issues](https://github.com/tc39/ecma262/issues?utf8=✓&q=is%3Aopen+label%3A%22web+reality%22+is%3Aissue) / [Needs Consensus PRs](https://github.com/tc39/ecma262/pulls?q=is%3Apr+is%3Aopen+label%3A%22needs+consensus%22)
96+
97+
| timebox | topic | presenter |
98+
|:-------:|-------|-----------|
99+
100+
1. Overflow from previous meeting
101+
102+
| timebox | topic | presenter |
103+
|:-------:|-------|-----------|
104+
105+
1. Short (≤30m) Timeboxed Discussions
106+
107+
| timebox | topic | presenter |
108+
|:-------:|-------|-----------|
109+
110+
1. Proposals
111+
112+
| stage | timebox | topic | presenter |
113+
|:-----:|:-------:|-------|-----------|
114+
115+
1. Longer or open-ended discussions
116+
117+
| timebox | topic | presenter |
118+
|:-------:|-------|-----------|
119+
120+
1. Overflow from timeboxed agenda items (in insertion order)
121+
122+
| topic | presenter |
123+
|-------|-----------|
124+
125+
1. Incubation call chartering (15m on the last day)
126+
127+
1. Other business
128+
1. Thank host
129+
1. Adjournment
130+
131+
### Schedule constraints
132+
133+
*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.*
134+
135+
<!-- DO NOT PUT YOUR CONSTRAINTS HERE! Put them in one of the next sections: either "Normal Constraints" or "Late-breaking Schedule Constraints" -->
136+
137+
<!-- Be specific! Provide a full name, date and time range that they will or will not be available, and which sessions they are trying to prioritize. Satisfaction not guaranteed, but more information is useful. Conflicting constraints honored on a first-come, first served basis. -->
138+
139+
#### Normal Constraints
140+
141+
<!-- Constraints supplied more than three days before the meeting should go here -->
142+
143+
#### Late-breaking Schedule Constraints
144+
145+
<!-- Constraints supplied less than three days before the meeting should go here -->

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@
44

55
| Mtg Num | First Day | Last Day | Location | Host |
66
| :-----: | ------------ | ------------ | ----------------------- | -------------------------- |
7-
| 110 | `2025‑09‑22` | `2025‑09‑25` | _Remote "New Orleans"_ ⚜️ | _n/a_ |
87
| 111 | `2025‑11‑18` | `2025‑11‑20` | Tokyo, Japan 🌸 | Bloomberg |
98

109
## Agendas
@@ -13,6 +12,7 @@
1312
<details open>
1413
<summary>2025</summary>
1514

15+
- [November](./2025/11.md)
1616
- [September](./2025/09.md)
1717
- [July](./2025/07.md)
1818
- [May](./2025/05.md)

0 commit comments

Comments
 (0)