Skip to content

Suggest that other stage advancement requirements can be articulated, specific to a proposal  #17

Description

@littledan

We discussed #15 in TC39, and several committee members (including @wycats @ljharb @zbraniecki and others) had this great suggestion: When moving from one stage to the next, or any time later, the committee and champions may articulate further things that need to be done to move to the following stage. We might want to write this down in the process document, or in a separate guide for how to champion proposals/be a committee member. We've been doing this sometimes, often in earlier stages; it may be useful for advancing from Stage 3 to 4 as well, articulating web compatibility, implementer experience and buy-in requirements specific to the proposal.

Activity

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions