Skip to content

Conversation

@littledan
Copy link
Member

A reframing of the agenda rules, from the template, encouraging people to add things sooner.

A reframing of the agenda rules, from the template, encouraging people to add things sooner.
Co-authored-by: Nicolò Ribaudo <[email protected]>
@michaelficarra
Copy link
Member

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.
Copy link
Member

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
Copy link
Member

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.

Copy link
Member Author

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

@michaelficarra
Copy link
Member

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.
Copy link
Member

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

littledan and others added 3 commits April 7, 2025 14:29
Co-authored-by: Michael Ficarra <[email protected]>
Co-authored-by: Michael Ficarra <[email protected]>
@littledan
Copy link
Member Author

Is the idea to link to this from the agenda instead of inlining it in each agenda?

Yes, see tc39/agendas#1835

@littledan
Copy link
Member Author

littledan commented Apr 7, 2025

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?

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants