-
Notifications
You must be signed in to change notification settings - Fork 18
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
Proposal repo should be a requirement #24
Comments
Seems like a PR, and an agenda item to get consensus on it, is in order. |
I believe we've been treating this as a requirement in practice already, and have held things back at Stage 0 due to not having a proposal repo. Documenting our practices here makes sense to me. |
That's not been my experience. What have we held back for not having a repo? (note that there are stage 1 proposals lacking a repo that were added in July 2019, July 2017, and September 2016) |
My mistake then! |
I think this is a good idea, as it will make our conversations stronger. Let's document this convention and also add it to the agenda template. |
Got consensus on this today; #26 is merged. |
Continue the discussion in https:/tc39/proposals/issues/236
From @mathiasbynens
From @ljharb
So I create this issue. 😀
The text was updated successfully, but these errors were encountered: