-
Notifications
You must be signed in to change notification settings - Fork 187
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
103 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,101 @@ | ||
|
||
<img src="../images/Ecma_RVB-003.jpg" align="right" height="70" alt="" /> | ||
|
||
# Agenda for the 85th meeting of Ecma TC39 | ||
|
||
- **Host**: TBD | ||
- **Dates and times**: | ||
- 10:00 to 15:00 "ET" on August 31st, 2021 | ||
- 10:00 to 15:00 "ET" on September 1st, 2021 | ||
- **Location**: Remote | ||
- **Attendee information**: https://github.com/tc39/Reflector/issues/388 | ||
|
||
Background: | ||
- Allen Wirfs-Brock's [paper on standards committee participation for new attendees](http://wirfs-brock.com/allen/files/papers/standpats-asianplop2016.pdf) | ||
- TC39's documentation on [How to participate in meetings](https://github.com/tc39/how-we-work/blob/master/how-to-participate-in-meetings.md) | ||
|
||
## Agenda topic rules | ||
|
||
Deadline for advancement eligibility: [August 21st, 2021, 10:00 ET](https://www.timeanddate.com/countdown/generic?p0=1440&iso=20210821T14&msg=TC39%20Submission%20deadline) | ||
- <sub>Note: this time is selected to be precisely 10 days prior to the start of the meeting</sub> | ||
|
||
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. | ||
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. | ||
1. Such proposals *should* include supporting materials when possible. | ||
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. | ||
1. Such proposals *must* link to a proposal repository and they *should* link to supporting materials when possible. | ||
1. Proposals looking to advance to stages 2, 3, or 4 must be added (and noted as such) *along with the necessary materials* 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 supporting materials prior to the deadline, or else delegates may object to advancement solely on the basis of missing the deadline. If these materials change substantially after the deadline, the proposal may be disqualified from advancement, based on the committee’s judgment. | ||
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. | ||
1. 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 items | ||
|
||
1. Opening, welcome and roll call (Chair) | ||
1. Opening of the meeting | ||
1. TC39 follows its [Code of Conduct](https://tc39.github.io/code-of-conduct/) | ||
1. Introduction of attendees | ||
1. Host facilities, local logistics | ||
1. Quick recap of meeting IPR policy | ||
1. Overview of communication tools | ||
1. Find volunteers for note taking | ||
1. Adoption of the agenda | ||
1. Approval of the minutes from last meeting | ||
1. Next meeting host and logistics | ||
1. Secretary's Report (15m, Istvan Sebestyen) | ||
1. Project Editors’ Reports | ||
1. [ECMA262](https://github.com/tc39/ecma262) Status Updates (15m) | ||
1. [ECMA402](https://github.com/tc39/ecma402) Status Updates (15m) | ||
1. [ECMA404](https://www.ecma-international.org/publications/standards/Ecma-404.htm) Status Updates (15m) | ||
1. [Test262](https://github.com/tc39/test262) Status Updates (15m) | ||
1. Updates from the [CoC Committee](https://tc39.es/code-of-conduct/#code-of-conduct-committee) (15m) | ||
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) | ||
|
||
| ✓ | timebox | topic | presenter | | ||
|:-:|:-------:|-------|-----------| | ||
|
||
1. Overflow from previous meeting | ||
|
||
| ✓ | timebox | topic | presenter | | ||
|:-:|:-------:|-------|-----------| | ||
|
||
1. Incubation call chartering (15m on the last day) | ||
|
||
1. Short (≤30m) Timeboxed Discussions | ||
|
||
| ✓ | timebox | topic | presenter | | ||
|:-:|:-------:|-------|-----------| | ||
|
||
1. Proposals | ||
|
||
✓ represents an agenda item which has been presented, and does not indicate stage advancement | ||
|
||
| ✓ | stage | timebox | topic | presenter | | ||
|:-:|:-----:|:-------:|-------|-----------| | ||
|
||
1. Longer or open-ended discussions | ||
|
||
| ✓ | timebox | topic | presenter | | ||
|:-:|:-------:|-------|-----------| | ||
|
||
1. Overflow from timeboxed agenda items (in insertion order) | ||
|
||
| ✓ | topic | presenter | | ||
|:-:|-------|-----------| | ||
|
||
1. Other business | ||
1. Thank host | ||
1. Adjournment | ||
|
||
### Schedule constraints | ||
|
||
<!-- 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. --> | ||
|
||
## Dates and locations of future meetings | ||
|
||
| Dates | Location | | ||
|--------------------------|--------------------------------| | ||
| 2021-10-25 to 2021-10-28 | "London?", GMT | | ||
| 2021-12-14 to 2021-12-15 | Remote: PT | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters