-
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
base: main
Are you sure you want to change the base?
Conversation
A reframing of the agenda rules, from the template, encouraging people to add things sooner.
Co-authored-by: Nicolò Ribaudo <[email protected]>
|
Is the idea to link to this from the agenda instead of inlining it in each agenda? |
agenda.md
Outdated
|
|
||
| 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. |
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 duplicated above.
agenda.md
Outdated
| @@ -0,0 +1,20 @@ | |||
| ## Agenda topic best practices | |||
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.
We might want to clarify we're just talking about TG1 agendas here.
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.
Clarified that it's for plenary
|
Why have this in tc39/how-we-work instead of a document in the tc39/agendas repo? It only applies to the agendas in that repo, right? |
| - 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. |
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)
Co-authored-by: Michael Ficarra <[email protected]>
Co-authored-by: Michael Ficarra <[email protected]>
Yes, see tc39/agendas#1835 |
I don't have a strong opinion here, but my thought was that this repo is for the how-to information, and the agendas repo is just for the agendas. Theoretically we could also have it in ecma262, since it's just for plenary :) |
A reframing of the agenda rules, from the template, encouraging people to add things sooner.