From 4bad3e758b4315b8a5aaca759acf198cdb4b8a1c Mon Sep 17 00:00:00 2001 From: Daniel Ehrenberg Date: Mon, 7 Apr 2025 11:42:45 -0400 Subject: [PATCH 1/5] Document agenda rules A reframing of the agenda rules, from the template, encouraging people to add things sooner. --- agenda.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 agenda.md diff --git a/agenda.md b/agenda.md new file mode 100644 index 0000000..3b84c15 --- /dev/null +++ b/agenda.md @@ -0,0 +1,20 @@ +## Agenda topic best practices + +All TC39 agenda items should be posted on the agenda before the "agenda deadline", which is precisely 10 days before the start of the meeting. It's best to post agenda items as soon as you know you'll be presenting on the topic, even if you don't have all of the supporting materials yet. + +Before the agenda deadline, agenda items should be accompanied by supporting materials. 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. + +Pull requests are encouraged for all agenda additions, especially for late additions after the deadline, so that members are notified of changes. All delegates have write access to the agenda, and should promptly land agenda additions so that they are maximally visible quickly. + +If agenda items or their supporting materials are added only after the agenda deadline, then TC39 is unlikely to reach consensus on that item. Many TC39 delegates review the agenda ahead of the meeting with their colleagues, in order to collect feedback to bring to the committee. + +TC39 may reach consensus on certain proposals whose supporting materials are added late, if a normative change is considered urgent. It's best to avoid this situation, however. + +Some types of supporting materials which are typically necessary based on the stage of the proposal, in addition to slides: +- A Stage 1 proposal should explain the problem statement in a README. +- Stage 2, 2.7, 3 and 4 proposals, as well as any consensus-seeking normative change, need spec text, in addition to a README explaining the proposal and its motivation in some detail. +- Stage 4 proposals 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. + +The TC39 agenda items about proposals are sorted primarily by stage (descending), secondarily by timebox (ascending), and finally by insertion date. Items may be reordered by chairs when running the meeting based on various constraints. + +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. From a5270ab516f2142474cc5efdae821fc9fd0e61e7 Mon Sep 17 00:00:00 2001 From: Daniel Ehrenberg Date: Mon, 7 Apr 2025 11:54:03 -0400 Subject: [PATCH 2/5] Update agenda.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Nicolò Ribaudo --- agenda.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agenda.md b/agenda.md index 3b84c15..0e22fe0 100644 --- a/agenda.md +++ b/agenda.md @@ -13,7 +13,7 @@ TC39 may reach consensus on certain proposals whose supporting materials are add Some types of supporting materials which are typically necessary based on the stage of the proposal, in addition to slides: - A Stage 1 proposal should explain the problem statement in a README. - Stage 2, 2.7, 3 and 4 proposals, as well as any consensus-seeking normative change, need spec text, in addition to a README explaining the proposal and its motivation in some detail. -- Stage 4 proposals 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. +- Stage 4 proposals and normative changes pursued outside of the stages process 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. The TC39 agenda items about proposals are sorted primarily by stage (descending), secondarily by timebox (ascending), and finally by insertion date. Items may be reordered by chairs when running the meeting based on various constraints. From 15b79cbb1830325b6a061edccc9ceaea41c06945 Mon Sep 17 00:00:00 2001 From: Daniel Ehrenberg Date: Mon, 7 Apr 2025 14:29:32 -0400 Subject: [PATCH 3/5] Update agenda.md --- agenda.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/agenda.md b/agenda.md index 0e22fe0..d7a59e6 100644 --- a/agenda.md +++ b/agenda.md @@ -1,4 +1,4 @@ -## Agenda topic best practices +## Plenary agenda topic best practices All TC39 agenda items should be posted on the agenda before the "agenda deadline", which is precisely 10 days before the start of the meeting. It's best to post agenda items as soon as you know you'll be presenting on the topic, even if you don't have all of the supporting materials yet. @@ -16,5 +16,3 @@ Some types of supporting materials which are typically necessary based on the st - Stage 4 proposals and normative changes pursued outside of the stages process 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. The TC39 agenda items about proposals are sorted primarily by stage (descending), secondarily by timebox (ascending), and finally by insertion date. Items may be reordered by chairs when running the meeting based on various constraints. - -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. From 9f5bfa9c902581c005f124cfcfaa614100f4d5ce Mon Sep 17 00:00:00 2001 From: Daniel Ehrenberg Date: Mon, 7 Apr 2025 14:29:49 -0400 Subject: [PATCH 4/5] Update agenda.md Co-authored-by: Michael Ficarra --- agenda.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agenda.md b/agenda.md index d7a59e6..0292592 100644 --- a/agenda.md +++ b/agenda.md @@ -4,7 +4,7 @@ All TC39 agenda items should be posted on the agenda before the "agenda deadline Before the agenda deadline, agenda items should be accompanied by supporting materials. 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. -Pull requests are encouraged for all agenda additions, especially for late additions after the deadline, so that members are notified of changes. All delegates have write access to the agenda, and should promptly land agenda additions so that they are maximally visible quickly. +Pull requests are encouraged for all agenda modifications, especially for late additions after the deadline, so that members are notified. All delegates have write access to the agenda, and should promptly land agenda additions so that they are maximally visible quickly. If agenda items or their supporting materials are added only after the agenda deadline, then TC39 is unlikely to reach consensus on that item. Many TC39 delegates review the agenda ahead of the meeting with their colleagues, in order to collect feedback to bring to the committee. From 31ea512d49c0c083948582f26f7138e77546a402 Mon Sep 17 00:00:00 2001 From: Daniel Ehrenberg Date: Mon, 7 Apr 2025 14:29:59 -0400 Subject: [PATCH 5/5] Update agenda.md Co-authored-by: Michael Ficarra --- agenda.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agenda.md b/agenda.md index 0292592..659c2d1 100644 --- a/agenda.md +++ b/agenda.md @@ -12,7 +12,7 @@ TC39 may reach consensus on certain proposals whose supporting materials are add Some types of supporting materials which are typically necessary based on the stage of the proposal, in addition to slides: - A Stage 1 proposal should explain the problem statement in a README. -- Stage 2, 2.7, 3 and 4 proposals, as well as any consensus-seeking normative change, need spec text, in addition to a README explaining the proposal and its motivation in some detail. +- Stage 2, 2.7, 3, and 4 proposals, as well as any consensus-seeking normative change, need spec text, in addition to a README explaining the proposal and its motivation in some detail. - Stage 4 proposals and normative changes pursued outside of the stages process 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. The TC39 agenda items about proposals are sorted primarily by stage (descending), secondarily by timebox (ascending), and finally by insertion date. Items may be reordered by chairs when running the meeting based on various constraints.