-
Notifications
You must be signed in to change notification settings - Fork 29
Document agenda rules #163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
littledan
wants to merge
5
commits into
main
Choose a base branch
from
agenda-rules
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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,18 @@ | ||
| ## 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. | ||
|
|
||
| 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 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. | ||
|
|
||
| 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 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. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably best left inlined in the agenda document.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added in https://github.com/tc39/agendas/pull/1835/files#diff-aba7587e39c1482d1c0c48d2e63fed479b50fa10686da59dca2312b7cb4cd7a5R48 (but preserved here too)